Subject: | |
From: | |
Reply To: | |
Date: | Thu, 5 Feb 1998 20:17:55 -0500 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
>Good Folk,
>
>I've been running my new socket-7 PC for about 6 weeks now. The
>serial mouse and modem seem to work OK, but the comm ports are not
>configured properly.
>When my NT boots, I look in the Event Log and find:
> Event 3:
> User configuration data for parameter COM2 overriding firmware
> configuration data.
>
> Event 22:
> A conflict has been detected between two drivers which claimed two
> overlapping Io port regions. Driver Serial, with device
> <\Device\Serial10000.Translated>, claimed an IO port range with
> starting address in data address 0x28 and 0x2c, and length in data
> address 0x30.
>
> Event 22:
> A conflict has been detected between two drivers which claimed two
> overlapping Io port regions. Driver Sermouse, with device
> <\Device\PointerPort0.Translated>, claimed an IO port range with
> starting address in data address 0x28 and 0x2c, and length in data
> address 0x30.
>
> Event 11:
> The hardware resources for COM1 are already in use by another
> device.
>
>If I could get my comm ports configured the way NT "needs" them, I
>would be happy as a clam ...
NT is initializing the mouse on Com 1 as a serial device, then attempting
to initialize Com 1 using the same resources. Since it cannot do this,
there are no system conflicts, just those annoying "Event Failed " entries
in the Event Log. Even though it is counter-intuitive, deleting the COM 1
entry from Control Panel/Ports and rebooting should put you in the blue.
Ron Browne
Marlton Computer Associates
[log in to unmask]
Need help with PCBUILD:
[log in to unmask] or http://nospin.com
|
|
|