Hardware Wizard, SIO behavior

[David]

Archived from groups: microsoft.public.windowsxp.hardware (More info?)

Enough is enough. Why is it that XP always treats an unexpected bitstream
on the SERIAL port at boot time as a mouse and loads the MS serial mouse
driver which locks the port?
Other than making sure the the serial device is unplugged/off at boot time,
does anyone know of a way to make the AddNewHardware Wizard ignore the port?
Dave

 

[Guest]

Archived from groups: microsoft.public.windowsxp.hardware (More info?)

Available switch options for the Windows XP and the Windows Server 2003
Boot.ini files
http://support.microsoft.com/default.aspx?scid=kb;en-us;833721&Product=winxp

/fastdetect:comnumber
This switch turns off serial and bus mouse detection in the Ntdetect.com
file for the specified port. Use this switch if you have a component
other than a mouse that is attached to a serial port during the startup
process. For example, type /fastdetect:comnumber, where number is the
number of the serial port. Ports may be separated with commas to turn
off more than one port. If you use /fastdetect, and you do not specify a
communications port, serial mouse detection is turned off on all
communications ports.



David wrote:

> Enough is enough. Why is it that XP always treats an unexpected bitstream
> on the SERIAL port at boot time as a mouse and loads the MS serial mouse
> driver which locks the port?
> Other than making sure the the serial device is unplugged/off at boot time,
> does anyone know of a way to make the AddNewHardware Wizard ignore the port?
> Dave
>
>
>

 

[David]

Archived from groups: microsoft.public.windowsxp.hardware (More info?)

Well schucky darn. It defaults to /fastdetect without argument. The
problem is that the OS itself scans for changes.
I found a KB on the subject and it is a bit convoluted adjustment.
Especially when the com port is on a USB adaptor.

"Bob I" <birelan@yahoo.com> wrote in message
news:4154912A.9040807@yahoo.com...
>
> Available switch options for the Windows XP and the Windows Server 2003
> Boot.ini files
> http://support.microsoft.com/default.aspx?scid=kb;en-us;833721&Product=winxp
>
> /fastdetect:comnumber
> This switch turns off serial and bus mouse detection in the Ntdetect.com
> file for the specified port. Use this switch if you have a component other
> than a mouse that is attached to a serial port during the startup process.
> For example, type /fastdetect:comnumber, where number is the number of the
> serial port. Ports may be separated with commas to turn off more than one
> port. If you use /fastdetect, and you do not specify a communications
> port, serial mouse detection is turned off on all communications ports.
>
>
>
> David wrote:
>
>> Enough is enough. Why is it that XP always treats an unexpected
>> bitstream on the SERIAL port at boot time as a mouse and loads the MS
>> serial mouse driver which locks the port?
>> Other than making sure the the serial device is unplugged/off at boot
>> time, does anyone know of a way to make the AddNewHardware Wizard ignore
>> the port?
>> Dave
>