[Touch Pro2, Tilt 2 Windows Mobile General] mail_e36:
Hello friends,

After some work I have finally gotten the command line interface (Dos Prompt CLI) to work on the Tmobile Rhodium with the stock ROM and Windows Mobile 6.1.

Here's what you need: Microsoft Windows Mobile Developer Power Tools available for free here:

http://www.microsoft.com/downloads/...d6-1dcc-47aa-ab28-6a2b006edfe9&displaylang=en

Within the Microsoft Windows Mobile Developer Power Tools package extract the folder called "PPC Command Shell - Command shell for the Pocket PC 2003 device." Do not worry that it says "Pocket PC 2003", we will make it work on Windows Mobile 5/6! (for background information read http://dalelane.co.uk/blog/?p=122&cpage=1#comment-102893). You will see three files: shell.exe, cmd.exe, and console.dll. Place the console.dll file in your Windows directory on your device (in our case, on the Rhodium Touch Pro 2 the Windows directory takes a long time to populate, but it will, add the console.dll to it). Then move the shell.exe and cmd.exe file to another folder on your device. After you are done with the below instructions you will be able to link directly to the cmd.exe file and run the command line terminal.

For the command line to work you would normally need to toggle the following registry key between "0" and "1" HKEY_LOCAL_MACHINE\Drivers\Console\OutputTo

By default it is set to "1" which disallows the command prompt to run, we need to set it to "0" to enable the command prompt. But, the caveat is that upon reboot it's best to have this key set to "1" otherwise your boot process is extended by about two minutes and you will get two open command prompt windows upon booting which you will need to manually close to go back to your home screen (annoying, but not a huge issue). In order to avoid all that, I have created a two simple Cab files which toggle the above registry key between "0" and "1". Before running the command prompt I run Command_Line_VISIBLE.cab (which turns the registry key to a "0" and when I'm done with the command prompt I run Command_Line_INVISIBLE.cab (which turns the registry key back to '1').

If you forget to run Command_Line_INVISIBLE.cab when done with the command prompt it's no big deal, just run it whenever you get a chance (even after a reboot, which would take two minutes longer and open the command prompt by default, which is no biggie since you can just close it once the device fully boots). Leaving the registry key set to "0" should not damage anything.

I have attached the cab files on the forum.

The goal of installing a command line interface on a Windows Mobile device is 'hackability'... you get yet much better (granular) access to your device. I have always been fond of the way Linux-based devices (Android, Iphone, Nokia N900) give you access to the command line, and always wanted something similar on Windows Mobile. Now this is possible, albeit with less options than the linux-based phones.

For example, with the command line you can now run NetCat. Netcat is known as the Swiss Army Knife of Networking. (http://en.wikipedia.org/wiki/Netcat) on your Windows Mobile phone...

You can download and install NetCat for Windows Mobile at http://prt.fernuni-hagen.de/~bischoff/wince/

I have tested a few basic NetCat commands and they seem to be working as expected, but more testing is needed.

Any feedback is appreciated

Usual disclaimer: This has worked great for me, but obviously I am not responsible if you damage your device.