Unable to configure CE.NET for more than 3 serial ports.

Hi,

I have a hardware which has six serial ports and I was able to use
this and configure it with the CE 3.0. But in CE.NET I am not able to
use more than 3 serial ports.

I have already disabled the COM1 debug port by modifying the Debug.C
file. It seems the trick is how to use the port base addresses found
at the start of platform.reg file. I am really not sure how do those
addresses work.

My hardware settings are
COM1 - IRQ4 - SysIntr 14 - 0x3F8 ( Works )
COM2 - IRQ3 - SysIntr 13 - 0x2F8 ( Works )
COM3 - IRQ9 - SysIntr 19 - 0x3E8 ( Works )
COM4 - IRQ6 - SysIntr 16 - 0x2E8 ( Fails !! )
COM5 - IRQ7 - SysIntr 17 - 0x280 ( Fails !! )
COM6 - IRQ14 - SysIntr 24 - 0x2C0( Fails !! )

I checled in the driver and it seems to fail when the
InterruptInitialize function in the StartDispatchThread is called for
COM4,COM5 and COM6.

Any help with what could be wrong will be highly appreciated.

Thanks,
Bhavin

Paul
Mon Sep 27 13:03:03 CDT 2004

Build a debug version of the OS and actually trap the debug messages (you
may have to turn the debug serial port back on for this, of course).

Paul T.

"Bhavin Shah" <bhavinmshah@yahoo.com> wrote in message
news:411fd11c.0409270942.30a03125@posting.google.com...
> Hi,
>
> I have a hardware which has six serial ports and I was able to use
> this and configure it with the CE 3.0. But in CE.NET I am not able to
> use more than 3 serial ports.
>
> I have already disabled the COM1 debug port by modifying the Debug.C
> file. It seems the trick is how to use the port base addresses found
> at the start of platform.reg file. I am really not sure how do those
> addresses work.
>
> My hardware settings are
> COM1 - IRQ4 - SysIntr 14 - 0x3F8 ( Works )
> COM2 - IRQ3 - SysIntr 13 - 0x2F8 ( Works )
> COM3 - IRQ9 - SysIntr 19 - 0x3E8 ( Works )
> COM4 - IRQ6 - SysIntr 16 - 0x2E8 ( Fails !! )
> COM5 - IRQ7 - SysIntr 17 - 0x280 ( Fails !! )
> COM6 - IRQ14 - SysIntr 24 - 0x2C0( Fails !! )
>
> I checled in the driver and it seems to fail when the
> InterruptInitialize function in the StartDispatchThread is called for
> COM4,COM5 and COM6.
>
> Any help with what could be wrong will be highly appreciated.
>
> Thanks,
> Bhavin

bhavinmshah
Tue Sep 28 13:10:42 CDT 2004

Hi Paul,

Thanks for your reply. I did enable the Debug serial port back but
nothing seems to come out on the debug serial line. Instead I have a
dump in my ethernet debugger which is as below ....

4294768161 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458:
DEVICE!ActivateDeviceEx(Drivers\BuiltIn\Serial) entered
4294768170 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458: >>> Loading module
com16550.dll at address 0x03A20000-0x03A34000 (RW data at
0x01FA3000-0x01FA3564)
Loaded symbols for 'D:\WINCE420\PUBLIC\CUSTOMLM\RELDIR\NATIONAL_GEODE_X86DEBUG\COM16550.DLL'
4294768188 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458: SerInit - Devindex 0,
SysIntr 20, IOB 3F8, IOLen 8
4294768188 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458:
Ser_InternalMapRegisterAddresses : HalTranslateBusAddress - OK
4294768189 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458:
Ser_InternalMapRegisterAddresses : IO Space
4294768189 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458: SerInit - SYSINTR 20
4294768189 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458:
SL_InstallSoftwareISR, No Installable ISR
4294768190 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458: PNP interface class
{f8a6ba98-087a-43ac-a9d8-b7f13c5bae31} (COM1:) ATTACH
4294768192 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458:
DEVICE!ActivateDeviceEx(Drivers\BuiltIn\Serial2) entered
4294768195 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458: SerInit - Devindex 1,
SysIntr 19, IOB 2F8, IOLen 8
4294768195 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458:
Ser_InternalMapRegisterAddresses : HalTranslateBusAddress - OK
4294768196 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458:
Ser_InternalMapRegisterAddresses : IO Space
4294768196 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458: SerInit - SYSINTR 19
4294768197 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458:
SL_InstallSoftwareISR, No Installable ISR
4294768198 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458: PNP interface class
{f8a6ba98-087a-43ac-a9d8-b7f13c5bae31} (COM2:) ATTACH
4294768199 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458:
DEVICE!ActivateDeviceEx(Drivers\BuiltIn\Serial3) entered
4294768202 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458: SerInit - Devindex 2,
SysIntr 25, IOB 3E8, IOLen 8
4294768202 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458:
Ser_InternalMapRegisterAddresses : HalTranslateBusAddress - OK
4294768203 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458:
Ser_InternalMapRegisterAddresses : IO Space
4294768203 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458: SerInit - SYSINTR 25
4294768203 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458:
SL_InstallSoftwareISR, No Installable ISR
4294768204 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458: PNP interface class
{f8a6ba98-087a-43ac-a9d8-b7f13c5bae31} (COM3:) ATTACH
4294768205 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458:
DEVICE!ActivateDeviceEx(Drivers\BuiltIn\Serial4) entered
4294768209 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458: SerInit - Devindex 3,
SysIntr 22, IOB 2E8, IOLen 8
4294768209 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458:
Ser_InternalMapRegisterAddresses : HalTranslateBusAddress - OK
4294768209 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458:
Ser_InternalMapRegisterAddresses : IO Space
4294768210 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458: SerInit - SYSINTR 22
4294768210 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458:
SL_InstallSoftwareISR, No Installable ISR
4294768211 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458: PNP interface class
{f8a6ba98-087a-43ac-a9d8-b7f13c5bae31} (COM4:) ATTACH
4294768212 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458:
DEVICE!ActivateDeviceEx(Drivers\BuiltIn\Serial5) entered
4294768216 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458: SerInit - Devindex 4,
SysIntr 23, IOB 280, IOLen 8
4294768216 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458:
Ser_InternalMapRegisterAddresses : HalTranslateBusAddress - OK
4294768216 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458:
Ser_InternalMapRegisterAddresses : IO Space
4294768217 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458: SerInit - SYSINTR 23
4294768217 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458:
SL_InstallSoftwareISR, No Installable ISR
4294768218 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458: PNP interface class
{f8a6ba98-087a-43ac-a9d8-b7f13c5bae31} (COM5:) ATTACH
4294768219 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458:
DEVICE!ActivateDeviceEx(Drivers\BuiltIn\Serial6) entered
4294768223 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458: SerInit - Devindex 5,
SysIntr 36, IOB 2C0, IOLen 8
4294768223 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458:
Ser_InternalMapRegisterAddresses : HalTranslateBusAddress - OK
4294768223 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458:
Ser_InternalMapRegisterAddresses : IO Space
4294768224 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458: SerInit - SYSINTR 36
4294768224 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458:
SL_InstallSoftwareISR, No Installable ISR
4294768225 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458: PNP interface class
{f8a6ba98-087a-43ac-a9d8-b7f13c5bae31} (COM6:) ATTACH

As it can be seen very clearly from the above log, there is a definite
disconnect between the SysIntr values that I am providing in my
registry and the one which the system is seeing. The values are in HEX
as I can see.

My question is, in the registry, do I need to provide the HEX SysIntr
values or the decimal. I think the offset is IRQ + 10. Is this offset
HEX 10 or decimal 10 that I do not know now.

I hope you can help me with this issue.

Thanks in anticipation,

Best Regards,
Bhavin Shah ( CA,USA )

"Paul G. Tobey [eMVP]" <ptobey no spam AT no instrument no spam DOT com> wrote in message news:<OCWH6wLpEHA.1272@TK2MSFTNGP09.phx.gbl>...
> Build a debug version of the OS and actually trap the debug messages (you
> may have to turn the debug serial port back on for this, of course).
>
> Paul T.
>
> "Bhavin Shah" <bhavinmshah@yahoo.com> wrote in message
> news:411fd11c.0409270942.30a03125@posting.google.com...
> > Hi,
> >
> > I have a hardware which has six serial ports and I was able to use
> > this and configure it with the CE 3.0. But in CE.NET I am not able to
> > use more than 3 serial ports.
> >
> > I have already disabled the COM1 debug port by modifying the Debug.C
> > file. It seems the trick is how to use the port base addresses found
> > at the start of platform.reg file. I am really not sure how do those
> > addresses work.
> >
> > My hardware settings are
> > COM1 - IRQ4 - SysIntr 14 - 0x3F8 ( Works )
> > COM2 - IRQ3 - SysIntr 13 - 0x2F8 ( Works )
> > COM3 - IRQ9 - SysIntr 19 - 0x3E8 ( Works )
> > COM4 - IRQ6 - SysIntr 16 - 0x2E8 ( Fails !! )
> > COM5 - IRQ7 - SysIntr 17 - 0x280 ( Fails !! )
> > COM6 - IRQ14 - SysIntr 24 - 0x2C0( Fails !! )
> >
> > I checled in the driver and it seems to fail when the
> > InterruptInitialize function in the StartDispatchThread is called for
> > COM4,COM5 and COM6.
> >
> > Any help with what could be wrong will be highly appreciated.
> >
> > Thanks,
> > Bhavin

Paul
Tue Sep 28 13:37:57 CDT 2004

Any and all entries in xyz.reg are in hex. So, if you put

"SysIntr"=DWORD:23

"23" is hex 23 or 0x35. When the value is read by the driver, it doesn't
care about hex or decimal; the value is a DWORD. However, your text must be
hex...

Paul T.

"Bhavin Shah" <bhavinmshah@yahoo.com> wrote in message
news:411fd11c.0409281010.d576aea@posting.google.com...
> Hi Paul,
>
> Thanks for your reply. I did enable the Debug serial port back but
> nothing seems to come out on the debug serial line. Instead I have a
> dump in my ethernet debugger which is as below ....
>
> 4294768161 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458:
> DEVICE!ActivateDeviceEx(Drivers\BuiltIn\Serial) entered
> 4294768170 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458: >>> Loading module
> com16550.dll at address 0x03A20000-0x03A34000 (RW data at
> 0x01FA3000-0x01FA3564)
> Loaded symbols for
> 'D:\WINCE420\PUBLIC\CUSTOMLM\RELDIR\NATIONAL_GEODE_X86DEBUG\COM16550.DLL'
> 4294768188 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458: SerInit - Devindex 0,
> SysIntr 20, IOB 3F8, IOLen 8
> 4294768188 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458:
> Ser_InternalMapRegisterAddresses : HalTranslateBusAddress - OK
> 4294768189 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458:
> Ser_InternalMapRegisterAddresses : IO Space
> 4294768189 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458: SerInit - SYSINTR 20
> 4294768189 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458:
> SL_InstallSoftwareISR, No Installable ISR
> 4294768190 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458: PNP interface class
> {f8a6ba98-087a-43ac-a9d8-b7f13c5bae31} (COM1:) ATTACH
> 4294768192 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458:
> DEVICE!ActivateDeviceEx(Drivers\BuiltIn\Serial2) entered
> 4294768195 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458: SerInit - Devindex 1,
> SysIntr 19, IOB 2F8, IOLen 8
> 4294768195 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458:
> Ser_InternalMapRegisterAddresses : HalTranslateBusAddress - OK
> 4294768196 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458:
> Ser_InternalMapRegisterAddresses : IO Space
> 4294768196 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458: SerInit - SYSINTR 19
> 4294768197 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458:
> SL_InstallSoftwareISR, No Installable ISR
> 4294768198 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458: PNP interface class
> {f8a6ba98-087a-43ac-a9d8-b7f13c5bae31} (COM2:) ATTACH
> 4294768199 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458:
> DEVICE!ActivateDeviceEx(Drivers\BuiltIn\Serial3) entered
> 4294768202 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458: SerInit - Devindex 2,
> SysIntr 25, IOB 3E8, IOLen 8
> 4294768202 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458:
> Ser_InternalMapRegisterAddresses : HalTranslateBusAddress - OK
> 4294768203 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458:
> Ser_InternalMapRegisterAddresses : IO Space
> 4294768203 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458: SerInit - SYSINTR 25
> 4294768203 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458:
> SL_InstallSoftwareISR, No Installable ISR
> 4294768204 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458: PNP interface class
> {f8a6ba98-087a-43ac-a9d8-b7f13c5bae31} (COM3:) ATTACH
> 4294768205 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458:
> DEVICE!ActivateDeviceEx(Drivers\BuiltIn\Serial4) entered
> 4294768209 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458: SerInit - Devindex 3,
> SysIntr 22, IOB 2E8, IOLen 8
> 4294768209 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458:
> Ser_InternalMapRegisterAddresses : HalTranslateBusAddress - OK
> 4294768209 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458:
> Ser_InternalMapRegisterAddresses : IO Space
> 4294768210 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458: SerInit - SYSINTR 22
> 4294768210 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458:
> SL_InstallSoftwareISR, No Installable ISR
> 4294768211 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458: PNP interface class
> {f8a6ba98-087a-43ac-a9d8-b7f13c5bae31} (COM4:) ATTACH
> 4294768212 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458:
> DEVICE!ActivateDeviceEx(Drivers\BuiltIn\Serial5) entered
> 4294768216 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458: SerInit - Devindex 4,
> SysIntr 23, IOB 280, IOLen 8
> 4294768216 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458:
> Ser_InternalMapRegisterAddresses : HalTranslateBusAddress - OK
> 4294768216 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458:
> Ser_InternalMapRegisterAddresses : IO Space
> 4294768217 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458: SerInit - SYSINTR 23
> 4294768217 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458:
> SL_InstallSoftwareISR, No Installable ISR
> 4294768218 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458: PNP interface class
> {f8a6ba98-087a-43ac-a9d8-b7f13c5bae31} (COM5:) ATTACH
> 4294768219 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458:
> DEVICE!ActivateDeviceEx(Drivers\BuiltIn\Serial6) entered
> 4294768223 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458: SerInit - Devindex 5,
> SysIntr 36, IOB 2C0, IOLen 8
> 4294768223 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458:
> Ser_InternalMapRegisterAddresses : HalTranslateBusAddress - OK
> 4294768223 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458:
> Ser_InternalMapRegisterAddresses : IO Space
> 4294768224 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458: SerInit - SYSINTR 36
> 4294768224 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458:
> SL_InstallSoftwareISR, No Installable ISR
> 4294768225 PID:a1bd47d2 TID:a1bdc1e2 0x81bd4458: PNP interface class
> {f8a6ba98-087a-43ac-a9d8-b7f13c5bae31} (COM6:) ATTACH
>
> As it can be seen very clearly from the above log, there is a definite
> disconnect between the SysIntr values that I am providing in my
> registry and the one which the system is seeing. The values are in HEX
> as I can see.
>
> My question is, in the registry, do I need to provide the HEX SysIntr
> values or the decimal. I think the offset is IRQ + 10. Is this offset
> HEX 10 or decimal 10 that I do not know now.
>
> I hope you can help me with this issue.
>
> Thanks in anticipation,
>
> Best Regards,
> Bhavin Shah ( CA,USA )
>
> "Paul G. Tobey [eMVP]" <ptobey no spam AT no instrument no spam DOT com>
> wrote in message news:<OCWH6wLpEHA.1272@TK2MSFTNGP09.phx.gbl>...
>> Build a debug version of the OS and actually trap the debug messages (you
>> may have to turn the debug serial port back on for this, of course).
>>
>> Paul T.
>>
>> "Bhavin Shah" <bhavinmshah@yahoo.com> wrote in message
>> news:411fd11c.0409270942.30a03125@posting.google.com...
>> > Hi,
>> >
>> > I have a hardware which has six serial ports and I was able to use
>> > this and configure it with the CE 3.0. But in CE.NET I am not able to
>> > use more than 3 serial ports.
>> >
>> > I have already disabled the COM1 debug port by modifying the Debug.C
>> > file. It seems the trick is how to use the port base addresses found
>> > at the start of platform.reg file. I am really not sure how do those
>> > addresses work.
>> >
>> > My hardware settings are
>> > COM1 - IRQ4 - SysIntr 14 - 0x3F8 ( Works )
>> > COM2 - IRQ3 - SysIntr 13 - 0x2F8 ( Works )
>> > COM3 - IRQ9 - SysIntr 19 - 0x3E8 ( Works )
>> > COM4 - IRQ6 - SysIntr 16 - 0x2E8 ( Fails !! )
>> > COM5 - IRQ7 - SysIntr 17 - 0x280 ( Fails !! )
>> > COM6 - IRQ14 - SysIntr 24 - 0x2C0( Fails !! )
>> >
>> > I checled in the driver and it seems to fail when the
>> > InterruptInitialize function in the StartDispatchThread is called for
>> > COM4,COM5 and COM6.
>> >
>> > Any help with what could be wrong will be highly appreciated.
>> >
>> > Thanks,
>> > Bhavin

Bruce
Tue Sep 28 14:25:46 CDT 2004

Also look up "reg files" in PB Help, the fact that these are HEX and other
fun facts are there.

--
Bruce Eitman (eMVP)
Senior Engineer
beitman AT applieddata DOT net

Applied Data Systems
www.applieddata.net
An ISO 9001:2000 Registered Company
Microsoft WEP Gold-level Member

Do have an opinion on the effectiveness of Microsoft Windows Mobile and
Embedded newsgroups? Let us know!
https://www.windowsembeddedeval.com/community/newsgroups

bhavinmshah
Wed Sep 29 13:21:06 CDT 2004

Thanks for all the help. I have been using CE 3.0 for quite some time
and have not had any issues with the serial port. The difference was
in CE 3.0 , I had to modify the serial driver in order to achieve the
six ports.

I have been able to get COM5 working now but still COM4 and COM6 do
not work. I believe in my OS settings, IRQ6 ( COM4 ) and IRQ14 ( COM6
) are assigned to something else.

Here are my settings for all the 6 pors in platform.reg
********************************************************************
IF BSP_NOSERIAL !
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Serial]
"SysIntr"=dword:14
"IoBase"=dword:03F8
"IoLen"=dword:8
"DeviceArrayIndex"=dword:0
"Prefix"="COM"
"Dll"="Com16550.Dll"
"Order"=dword:0
"Priority"=dword:0

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Serial\Unimodem]
"Tsp"="Unimodem.dll"
"DeviceType"=dword:0
"FriendlyName"=LOC_FRIENDLYNAME_SERIAL
"DevConfig"=hex: 10,00, 00,00, 05,00,00,00, 10,01,00,00,
00,4B,00,00, 00,00, 08, 00, 00, 00,00,00,00

IF BSP_SERIAL2
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Serial2]
"SysIntr"=dword:13
"IoBase"=dword:02F8
"IoLen"=dword:8
"DeviceArrayIndex"=dword:1
"Prefix"="COM"
"Dll"="Com16550.Dll"
"Order"=dword:0

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Serial2\Unimodem]
"Tsp"="Unimodem.dll"
"DeviceType"=dword:0
"FriendlyName"=LOC_FRIENDLYNAME_SERIAL2
"DevConfig"=hex: 10,00, 00,00, 05,00,00,00, 10,01,00,00,
00,4B,00,00, 00,00, 08, 00, 00, 00,00,00,00
ENDIF BSP_SERIAL2

IF BSP_SERIAL3
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Serial3]
"SysIntr"=dword:19
"IoBase"=dword:03E8
"IoLen"=dword:8
"DeviceArrayIndex"=dword:2
"Prefix"="COM"
"Dll"="Com16550.Dll"
"Order"=dword:0

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Serial3\Unimodem]
"Tsp"="Unimodem.dll"
"DeviceType"=dword:0
"FriendlyName"=LOC_FRIENDLYNAME_SERIAL3
"DevConfig"=hex: 10,00, 00,00, 05,00,00,00, 10,01,00,00,
00,4B,00,00, 00,00, 08, 00, 00, 00,00,00,00
ENDIF BSP_SERIAL3

IF BSP_SERIAL4
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Serial4]
"SysIntr"=dword:16
"IoBase"=dword:02E8
"IoLen"=dword:8
"DeviceArrayIndex"=dword:3
"Prefix"="COM"
"Dll"="COM16550.Dll"
"Order"=dword:0

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Serial4\Unimodem]
"Tsp"="Unimodem.dll"
"DeviceType"=dword:0
"FriendlyName"="Serial Cable on COM4:"
"DevConfig"=hex: 10,00, 00,00, 05,00,00,00, 10,01,00,00,
00,4B,00,00,00,00, 08, 00, 00, 00,00,00,00
ENDIF BSP_SERIAL4

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Serial5]
"SysIntr"=dword:17
"IoBase"=dword:0280
"IoLen"=dword:8
"DeviceArrayIndex"=dword:4
"Prefix"="COM"
"Dll"="Com16550.Dll"
"Order"=dword:0
"Priority"=dword:0

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Serial5\Unimodem]
"Tsp"="Unimodem.dll"
"DeviceType"=dword:0
"FriendlyName"="Serial Cable on COM5:"
"DevConfig"=hex: 10,00, 00,00, 05,00,00,00, 10,01,00,00,
00,4B,00,00, 00,00, 08, 00, 00, 00,00,00,00


[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Serial6]
"SysIntr"=dword:24
"IoBase"=dword:02C0
"IoLen"=dword:8
"DeviceArrayIndex"=dword:5
"Prefix"="COM"
"Dll"="Com16550.Dll"
"Order"=dword:0
"Priority"=dword:0

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Serial6\Unimodem]
"Tsp"="Unimodem.dll"
"DeviceType"=dword:0
"FriendlyName"="Serial Cable on COM6:"
"DevConfig"=hex: 10,00, 00,00, 05,00,00,00, 10,01,00,00,
00,4B,00,00, 00,00, 08, 00, 00, 00,00,00,00

ENDIF BSP_NOSERIAL !
**********************************************************************

Is there any known device which uses IRQ6 and IRQ 14. My BIOS is fine
and I have tested all the 6 serial ports using a DOS utility.

Please advise,

Thanks,
Bhavin Shah
Sr. Software Enginner ( Fremont , CA , USA )


"Bruce Eitman \(eMVP\)" <beitmannospam@NOSPAM_applieddata.NOSPAM_net> wrote in message news:<uJMz1DZpEHA.3300@TK2MSFTNGP12.phx.gbl>...
> Also look up "reg files" in PB Help, the fact that these are HEX and other
> fun facts are there.
>
> --
> Bruce Eitman (eMVP)
> Senior Engineer
> beitman AT applieddata DOT net
>
> Applied Data Systems
> www.applieddata.net
> An ISO 9001:2000 Registered Company
> Microsoft WEP Gold-level Member
>
> Do have an opinion on the effectiveness of Microsoft Windows Mobile and
> Embedded newsgroups? Let us know!
> https://www.windowsembeddedeval.com/community/newsgroups