cmd.exe over serial

I am working on porting wince to our custom platform. It is a
headless device and due to memory constraint we are using tiny kernel
configuration. Thus the entire explorer, shell etc are not available.
However when the device boots up we need to have "cmd.exe" executed
and the prompt available on the serial port.



Found that it is possible by the following registry settings

[HKEY_LOCAL_MACHINE\Drivers\Console]
OutputTo = REG_DWORD:1 // Redirects CMD to COM1
COMSpeed = REG_DWORD:19200 // Speed of serial
connection
And have cmd.exe executed at startup by a separate application. Since
putting cmd.exe in the init registry does execute it but terminates
with message "unrecognized option". The application just does a create
process and executes cmd.exe.



But using platform builder I found that the registry settings set in
platform.reg for COMSpeed, does not match with the actual settings on
the target. I checked the final reginit.ini which infact had the
settings same as platform.reg but the target registry had totally
different settings.



For ex: A setting of 9600 in platform.reg/reginit.ini would result in
target setting of 38400


Any inputs or guidance on this problem

sloh
Thu Apr 21 16:06:58 CDT 2005

Hi Arun, I started asking around for someone who knows cmd.exe, when
someone pointed out that your problem is probably something simpler.

Did you know the .reg file format uses hexadecimal DWORD values? 0x9600 in
hex is 38400 in decimal. To get a speed of 9600 (decimal) try 0x2580 hex.

Sue
sloh@microsoft.com (remove "online" from reply-to address)
http://blogs.msdn.com/sloh/
_____________________________________________________________
This posting is provided "AS IS" with no warranties, and confers no rights.
_____________________________________________________________

Have an opinion on the effectiveness of Microsoft Embedded newsgroups? Let
us know!
https://www.windowsembeddedeval.com/community/newsgroups

Frank
Sun Apr 24 05:27:36 CDT 2005

You could also use telnet.
For this you have to add the telnet component into your image.
Have tested this under .NET 4.2, works great.

Frank
www.WinCESoft.de

"Arun" <arun_kalmanje@yahoo.com> schrieb im Newsbeitrag
news:889bc7a7.0504211054.7b479da6@posting.google.com...
| I am working on porting wince to our custom platform. It is a
| headless device and due to memory constraint we are using tiny kernel
| configuration. Thus the entire explorer, shell etc are not available.
| However when the device boots up we need to have "cmd.exe" executed
| and the prompt available on the serial port.
|
|
|
| Found that it is possible by the following registry settings
|
| [HKEY_LOCAL_MACHINE\Drivers\Console]
| OutputTo = REG_DWORD:1 // Redirects CMD to COM1
| COMSpeed = REG_DWORD:19200 // Speed of serial
| connection
| And have cmd.exe executed at startup by a separate application. Since
| putting cmd.exe in the init registry does execute it but terminates
| with message "unrecognized option". The application just does a create
| process and executes cmd.exe.
|
|
|
| But using platform builder I found that the registry settings set in
| platform.reg for COMSpeed, does not match with the actual settings on
| the target. I checked the final reginit.ini which infact had the
| settings same as platform.reg but the target registry had totally
| different settings.
|
|
|
| For ex: A setting of 9600 in platform.reg/reginit.ini would result in
| target setting of 38400
|
|
| Any inputs or guidance on this problem