serial port does not appear in device manager.

[Yu-ning Feng]

Hello,

I have a thinkpad T21 installing WS2003 trial edition. T21 has a serial port
but it does not appear in device manager. Have tried to add it in manually,
but system complains resources are used by ACPI. ACPI driver (power
management driver) is installed, so are other hardware drivers. Any idea?

[Dave Patrick]

Check that it is enabled in cmos setup


--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"Yu-ning Feng" wrote:
> Hello,
>
> I have a thinkpad T21 installing WS2003 trial edition. T21 has a serial
> port
> but it does not appear in device manager. Have tried to add it in
> manually,
> but system complains resources are used by ACPI. ACPI driver (power
> management driver) is installed, so are other hardware drivers. Any idea?

[Yu-ning Feng]

"Dave Patrick" wrote:

> Check that it is enabled in cmos setup
>

Thanks for your fast response.

I suspected that at first and checked. Serial port did enabled (0x3f8, 4). I
disabled it, rebooted. Enabled it again, rebooted. No magic.

I added a comm port manually, again. It was given the name of com4, and
still had resource conflict.
However, I kept it this time (I uninstalled it immediately in previous
trials). Rebooted. com1 appeared. Strange (at least from my view).

Either BIOS or system should be responsible.

[Dave Patrick]

Yes, that is strange. Glad to hear it's working now.



--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"Yu-ning Feng" wrote:
> Thanks for your fast response.
>
> I suspected that at first and checked. Serial port did enabled (0x3f8, 4).
> I
> disabled it, rebooted. Enabled it again, rebooted. No magic.
>
> I added a comm port manually, again. It was given the name of com4, and
> still had resource conflict.
> However, I kept it this time (I uninstalled it immediately in previous
> trials). Rebooted. com1 appeared. Strange (at least from my view).
>
> Either BIOS or system should be responsible.

[Yu-ning Feng]

"Yu-ning Feng" wrote:

> "Dave Patrick" wrote:
>
> > Check that it is enabled in cmos setup
> >
>
> Thanks for your fast response.
>
> I suspected that at first and checked. Serial port did enabled (0x3f8, 4). I
> disabled it, rebooted. Enabled it again, rebooted. No magic.
>
> I added a comm port manually, again. It was given the name of com4, and
> still had resource conflict.
> However, I kept it this time (I uninstalled it immediately in previous
> trials). Rebooted. com1 appeared. Strange (at least from my view).
>
> Either BIOS or system should be responsible.

Forgot to mention, I was doing kernel debugging, so
.... /debugport=com1 in boot.ini
Don't know if that mattered.

Rebooted once more, com1 disappeared.

[Dave Patrick]

Can you remove or comment out to test?



--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"Yu-ning Feng" wrote:
> Forgot to mention, I was doing kernel debugging, so
> ... /debugport=com1 in boot.ini
> Don't know if that mattered.
>
> Rebooted once more, com1 disappeared.

[Yu-ning Feng]

"Dave Patrick" wrote:

> Can you remove or comment out to test?
>
>

Yes. I have two items in my boot menu, one for normal, the other for debug.

Using normal makes com1 appear, while using debug has the opposite effect.
For the first time com1 appeared, I did change boot.ini to /debugport=com4.
So, at least I could see a pattern now.

[Dave Patrick]

Ok, good. Sounds like you have it sorted out.


--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"Yu-ning Feng" wrote:
> Yes. I have two items in my boot menu, one for normal, the other for
> debug.
>
> Using normal makes com1 appear, while using debug has the opposite effect.
> For the first time com1 appeared, I did change boot.ini to
> /debugport=com4.
> So, at least I could see a pattern now.