| Author |
Topic |
|
|
MLong
19 Posts |
 Posted - 22 Apr 2003 : 09:50:40
|
I've been trying to alter the default configs for serial #1 on the Bitsy by editing the reginit.ini file and changing the following:
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Serial]
"Dll"="Serial.Dll"
"Order"=dword:2
"Index"=dword:1
"SerialPortIndex"=dword:1
"DeviceArrayIndex"=dword:0
"Prefix"="COM"
"FriendlyName"="Serial on COM1:"
"SerialEventGenerationPeriod"=dword:7D0
"IRSerialPort"=dword:0
"RS485"=dword:0
"INT_Disable"=dword:0
"Tsp"="Unimodem.dll"
"DeviceType"=dword:0
"DevConfig"=hex: 10,00, 00,00, 05,00,00,00, 10,01,00,00, 00,96,00,00, 00,00, 08, 00, 00, 00,00,00,00
The 96 (38400) used to be 4B (19200). I also changed:
[HKEY_CURRENT_USER\Comm\RasBook\38400@com1]
"DevCfg"=hex:\
10,00,00,00,5a,00,00,00,10,00,00,00,00,96,00,00,00,00,08,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
00,00,00,00
Where 38400@com1 used to be 19200@com1 and the 96 (38400) used to be 4B (19200).
However, after reburning flash and booting the changes haven't taken place. We need the default rate for com1 to be 38400 after boot, not 19200. What am I missing? I don't see an entry in the adsload.reg file that can be altered to obtain the desired result so it was assumed that editing the reginit.ini file would do the trick. Nada. Anyone know/see what we're missing to make this happen?
|
|
|
akidder
1519 Posts |
Posted - 22 Apr 2003 : 17:28:09
|
It looks like you've done your homework on this one! The issue may be that the build of CE you're using doesn't support hex strings. GC Plus CE builds 3.46 and later support reading the hex strings.
You can try one of the latest releases of CE for the GC Plus, use the ADSReg.exe application to parse an adsload.reg-like file or you can create this key programmatically. The choice is yours!
p.s. Please forgive that I'm moving your post from the Hardware forum to CE. |
 |
|
|
MLong
19 Posts |
Posted - 23 Apr 2003 : 08:06:17
|
We're using CE.NET 4.12 image on a 32meg Bitsy board. I gather from your reply that I did it correctly and it should have worked? That's what I was afraid of! Doing things correctly then discovering it still doesn't work is the worst kind of scenario ; ]
"...The issue may be that the build of CE you're using doesn't support hex strings."
CE.NET 4.12?
I assume the ADSReg.exe file you mention is some kind of program used to pre-validate reg files for potential errors prior to going through the burn process and wasting time with a bad file? I'll give that a shot and see if it complains about my edits, though I seriously doubt it because I was careful about the alterations, to the point of replacing existing data without "adding" anything including crlf etc. May have been overkill but I didn't want to risk it.
p.s. np about moving it. I put it there because there were many serial-port related questions in there. |
|
|
|
ctacke
877 Posts |
Posted - 23 Apr 2003 : 09:15:47
|
A few things I notice:
1. Modifying reginit.ini has no effect. The file is only included for informational purposes. To make registry modifications you must use ADSLOAD.REG.
2. At boot, ADSLOAD.REG entries are applied to the system, however the parser in most of our images just doesn't support binary data. It won't complain - it just won't apply them. We've written an updated parser called ADSReg, which Drew alluded to in his post, which does support binary keys. We are including the engine from this parser in our newer builds, but not all have been replaced yet. |
|
|
| |
Topic |
|
|
|
All Forums
Microsoft Windows CE
Modifying Bitsy default serial config
Forum Locked
Send Topic to a Friend
Printer Friendly