Windows Mobile 5.0 Now Has a Console!
It is now possible to load and run Microsoft's console as well as Simbolic's PocketConsole. Here are the steps.
1. Get the Pocket Console and install it
Pocket Console
2. Get the Pocket CMD file and install it
Pocket Cmd
3. You can also install Microsoft's cmd program in parallel with the Open Source one. There is a pocket cmd console buried within PowerToys 2003. I tried to install it but it didn't work properly. If you can extract the following three files from the CAB then you can get it working. All you need is the cmd.exe and shell.exe files placed anywhere in one directory. Then use the console.dll that symbolic installs within the Windows directory rather than the Microsoft console.dll and you will be able to run Microsoft's cmd dos utility.
I have a stand alone install for Microsoft's Cmd utility version 4.2 as well as the older one called 3.0 These work quite well. I just don't know where to find them on the web anymore. If you would like to try the stand alone installer, I will post them on a free downloading file site.
4. The most important step! Change the following registry entry.
HKEY_LOCAL_MACHINE\Drivers\Console\OutputTo
set this value to 0
What is beautiful about this set of programs is that I can now launch other apps from a dos console. I am able to launch the pocket ssh port created by Rainer (it supports tunneling) and other apps that have command line arguments and switches. Example. ssh mysite.com -l bandung -L 25:127.0.0.1:25
So to the point. I want to be able to launch python with the command line prompts/arguments. Things such as python.exe my_module.py -i and the like. But these features seemed to have been removed from the python ce port. If they are put back, then we should be able to test our modules by running them within an interactive python session.
http://www.nabble.com/Windows-Mobile-5.0-Now-Has-a-Console!-t2780274.html
True VGA on Windows Mobile 5
True VGA now available with Windows Mobile 5
Some of the WM devices available today come with a VGA screen but don't actually show the same amount on the screen as a "true" VGA device. Rather, the screen is "pixel doubled", which basically means there are more pixels for smoothing out the looks of fonts and objects. The result is that VGA devices are generally easier on the eyes.
A lot of power users actually prefer to run, or occasionally run their VGA device in true VGA mode. Previously, this was done using either SE_VGA or ozVGA but only on WM2003SE devices. I had been using ozVGA with my Axim x50v before upgrading to WM5 and loved it! Everything is quite tiny on the screen but you just hold it a little closer.

When I updated to WM5 I lost the ability to use true VGA on my device as neither SE_VGA nor ozVGA work with WM5. Fortunately, some of the users at XDA Forums and Aximsite were able to get things working! It isn't perfect but it will get your started.
BTW, for those that have not used a VGA app, you will be able to switch from regular VGA and true VGA. You don't have to just run with one or the other. It will require a soft reset to switch.
I decided to host the zip file in case the person that posted it decided to drop it from their site. Here it is:
http://www.smartmobileassets.com/Uploads/VGA.zip
The instructions to get this working are pretty straightforward:
- Copy the stuff in "Windows folder files" to your Windows folder.
- Run the cab file (on your PocketPC)
- Run OzVGA (included in this zip)
Give it a try! It really is nice for surfing to be able to use true VGA. You end up being able to see more of the webpage. You can always increase the size of fonts if they are too small. Just take a look at the documentation for ozVGA.
I am using this on my Axim x50v that is running WM5, but it should work with any VGA WM5 device. If you have a WM2003 device just install and use ozVGA.
This is not a commercial solution, so if you are concerned about this not working you should probably not do it. SMA cannot be responsible for anything that is installed or changed as a result of doing the above.
Another at www.4winmobile.com
http://www.4winmobile.com/4wm-vga-hack-faq-for-windows-mobile-5-devices-vt1800.html?sid=494a2df12b48a1e8fdca8ae0e7bfb752
"VGA demystified ? the definitive guide to OzVGA, SE_VGA and everything VGA-related" - a good discussion about VGA display
http://discussion.brighthand.com/showthread.php?t=216249
Native (high-resolution) VGA on WM5 VGA devices – the long-awaited roundup and tutorial!
It has been a year since I’ve published VGA demystified - the definitive guide to OzVGA, SE_VGA and everything VGA-related (alternatives:MobilitySite, AximSite (the x50/x51 forum; the Tips and Tricks forum), PPC Magazine, FirstLoox, BrightHand), the definite guide to the native VGA mode. As the in the meantime released Windows Mobile 5 requires so-called ‘code signing’ for these kinds of things to work, there has been a lot of confusion about how WM5 devices should be run in native VGA mode. The situation was made even worse by the fact that AKU2 ROMs and ROM upgrades, released earlier this year, also added some new icons to repertoire of Windows Mobile, which resulted in old hacks’ not working flawlessly.
Because of the tremendous (and because I’m one of the guys that know the most about the secrets of the native VGA mode) demand for a new, updated version of the above-linked VGA demystified guide, I’ve allocated some time to elaborate on this subject a bit and to test all the currently available solutions and hacks. This means I’ve tested all the available hacks on all my three VGA WM5 Pocket PC’s (HP iPAQ hx4700 (2.01), HTC Universal and Dell Axim x51v (A12)), taking a LOT of time and effort (because I’ve kept hard resetting these devices between installing other hacks).
First and foremost, now that there are some really nice packages (I'll also refer to them as "OzVGA builds" or "versions" as they're all contain the OzVGA front-end to switch between the two VGA modes and for configuration) to make the installation easy, using the hack on WM5 devices is in no way more complicated than on the previous operating system version WM2003SE.
Note: The tested & linked distributions are only meant for US English devices!
As the vast majority of the Pocket PC’s have an US English ROM (and I, having no WM5 VGA devices with other languages, couldn’t test other versions), I’ve only linked in US English native VGA versions. Do NOT try to install the above-linked versions on anything else (for example, a French or German PDA) because the native VGA mode won’t work!
To get versions meant for Pocket PC’s having ROM’s in other languages, please read AximSite forum member makuu's excellent tutorial. He's already built a French package.
If you have a Dell Axim x51v (including the latest, A12 ROM version),
First, you’ll need to get and install this certification CAB file. Then, get and install this CAB file. You’re set: you can now use OzVGA to switch between the two VGA modes (see its icon in Start Menu/Programs).
If you have a HTC Universal or an HP iPAQ hx4700 updated to WM5,
you’ll need to use this file. As opposed to the x51v version, no separate certification import is needed.
Note that, on the hx4700, it’ll mess up some of the dialogs; for example, the iPAQ Wireless dialog will be displayed two times: once pixel doubled and once in the upper left quarter of the screen. It’s the latter that you’ll need to use. Also, the built-in, simple HP Today plug-in, TodayPanel, will use oversized icons. You will want to disable it and switch to something better (please see this article (alternates: MobilitySite, AximSite, PPC Magazine, FirstLoox) for alternate Today launcher/meter plug-ins). Still, it’s much better than the x51v-specific CAB: using the latter, the HTC Universal won’t display the speaker, the phone and the battery icons and the hx4700 won’t display the speaker and the connectivity icon. Also note that, fortunately, as opposed to the x51v / Universal (screenshot of them here), the Power applet is displayed properly.
If you have another WM5 VGA model,
give a try to the second-linked CAB file first. If you don’t see some icons on the taskbar, give a try to the x51v-specific version.
Please also post your remarks on using these OzVGA builds on your particular VGA device (if it’s not one of the three VGA devices I’ve tested the builds on)!
Always remember to backup!
Much as it’s very rarely that installing these applications can cause any harm to your Pocket PC, remember to backup before installing them. This is of particular importance with non-tested VGA Pocket PC’s, where you may end up having to switch to another OzVGA version. Then, you may need to hard reset and restore your previous backup to get rid of a particular OzVGA version.
To backup your device, I recommend the latest, 3.0 series of SKTools (review here), Spb Backup (current version: 1.5) or Sprite Backup (current version: 5.1) (comparison here).
MSN Messenger and Transcriber compliance
These two apps were rather problematic with earlier versions (Transcriber with WM2003SE and Messenger with earlier WM5 distributions). Now, both work flawlessly.
I’ve tested MSN Messenger on the hx4700 and the x51v; both worked fine.
Transcriber works on all the three devices without problems (Universal screenshot here; it, incidentally, also shows the “incoming, unanswered call” icon is also displayed on the taskbar).
Other links
To understand the differences between the two (native and SE/standard) VGA modes, how OzVGA can be used, how you can swap the on-screen keyboard files etc., you will want to read the first-linked VGA demystified article.
Also see this AximSite thread on the x51v and this XDA-Dev thread on the Universal/hx4700 CAB. Note that the latter thread has a lot of additional, useless information and you will NOT need to read it to be able to use OzVGA. My old VGA demystified article will be sufficient for most people.
UPDATE (09/06/2006): PPCT Frontpage
UPDATE (09/07/2006): added a link to makuu's new foreign-language tutorial.
UPDATE (09/23/2006):: in this thread, there are some additional CAB files you;ll want to install if you have a non-hx4700 device. They will fix the power / brightness / microphone settings applets. (On the HP iPAQ hx4700, you won't need them.)

