Windows boot, fastdetect and COM port question

[Guest]

We have a system here that will be a call accounting system. It will have
data from a PBX sent to a COM port even when the system is booting up. This
creates a problem under normal circumstances as Windows will try to install a
serial pointing device.
I have /fastdetect in the boot.ini file but the system is still trying to
install pointing devices. I have added the COM1,2,3 etc after fast detect and
still the same problem.
Basically I have done exactly what Microsoft said to do to prevent the
problems I am seeing.
So what is the real solution to this problem?

 

[Yves Leclerc]

We have a system here that will be a call accounting system. It will have
data from a PBX sent to a COM port even when the system is booting up. This
creates a problem under normal circumstances as Windows will try to install a
serial pointing device.
I have /fastdetect in the boot.ini file but the system is still trying to
install pointing devices. I have added the COM1,2,3 etc after fast detect and
still the same problem.
Basically I have done exactly what Microsoft said to do to prevent the
problems I am seeing.
So what is the real solution to this problem?

Use the BOOT.INI /noserialmice

/NOSERIALMICE=[COMx | COMx,y,z...] - Disables serial mouse detection of the
specified COM port(s). Use this switch if you have a component other than a
mouse attached to a serial port during the startup sequence. If you use
/NOSERIALMICE without specifying a COM port, serial mouse detection is
disabled on all COM ports.

 

[Guest]

Isn't that switch for NT4.0 and prior OS' only?

We have a system here that will be a call accounting system. It will have
data from a PBX sent to a COM port even when the system is booting up. This
creates a problem under normal circumstances as Windows will try to install a
serial pointing device.
I have /fastdetect in the boot.ini file but the system is still trying to
install pointing devices. I have added the COM1,2,3 etc after fast detect and
still the same problem.
Basically I have done exactly what Microsoft said to do to prevent the
problems I am seeing.
So what is the real solution to this problem?

Use the BOOT.INI /noserialmice

/NOSERIALMICE=[COMx | COMx,y,z...] - Disables serial mouse detection of the
specified COM port(s). Use this switch if you have a component other than a
mouse attached to a serial port during the startup sequence. If you use
/NOSERIALMICE without specifying a COM port, serial mouse detection is
disabled on all COM ports.

 

[Guest]

Here is the key line from my boot.ini file.
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP
Professional" /FASTDETECT /NoExecute=OptIn

Now, fastdetect was in lower case but I just changed it to upper case just
because. I do not think it is case sensitive but you never know.
Any other thoughts on this problem?

We have a system here that will be a call accounting system. It will have
data from a PBX sent to a COM port even when the system is booting up. This
creates a problem under normal circumstances as Windows will try to install a
serial pointing device.
I have /fastdetect in the boot.ini file but the system is still trying to
install pointing devices. I have added the COM1,2,3 etc after fast detect and
still the same problem.
Basically I have done exactly what Microsoft said to do to prevent the
problems I am seeing.
So what is the real solution to this problem?

Use the BOOT.INI /noserialmice

/NOSERIALMICE=[COMx | COMx,y,z...] - Disables serial mouse detection of the
specified COM port(s). Use this switch if you have a component other than a
mouse attached to a serial port during the startup sequence. If you use
/NOSERIALMICE without specifying a COM port, serial mouse detection is
disabled on all COM ports.

 

[Infosink]

Isn't that switch for NT4.0 and prior OS' only?

We have a system here that will be a call accounting system. It
will have data from a PBX sent to a COM port even when the system
is booting up. This creates a problem under normal circumstances
as Windows will try to install a serial pointing device.
I have /fastdetect in the boot.ini file but the system is still
trying to install pointing devices. I have added the COM1,2,3 etc
after fast detect and still the same problem.
Basically I have done exactly what Microsoft said to do to prevent
the problems I am seeing.
So what is the real solution to this problem?

Use the BOOT.INI /noserialmice

/NOSERIALMICE=[COMx | COMx,y,z...] - Disables serial mouse
detection of the specified COM port(s). Use this switch if you have
a component other than a mouse attached to a serial port during the
startup sequence. If you use /NOSERIALMICE without specifying a COM
port, serial mouse detection is disabled on all COM ports.

Here's a link if it helps anyone:

[Boot INI Options Reference]
http://www.sysinternals.com/Information/bootini.html

 

[Guest]

The problem with the switches listed are that the /fastdetect one just flat
out does not work.

Isn't that switch for NT4.0 and prior OS' only?

:

We have a system here that will be a call accounting system. It
will have data from a PBX sent to a COM port even when the system
is booting up. This creates a problem under normal circumstances
as Windows will try to install a serial pointing device.
I have /fastdetect in the boot.ini file but the system is still
trying to install pointing devices. I have added the COM1,2,3 etc
after fast detect and still the same problem.
Basically I have done exactly what Microsoft said to do to prevent
the problems I am seeing.
So what is the real solution to this problem?

Use the BOOT.INI /noserialmice

/NOSERIALMICE=[COMx | COMx,y,z...] - Disables serial mouse
detection of the specified COM port(s). Use this switch if you have
a component other than a mouse attached to a serial port during the
startup sequence. If you use /NOSERIALMICE without specifying a COM
port, serial mouse detection is disabled on all COM ports.

Here's a link if it helps anyone:

[Boot INI Options Reference]
http://www.sysinternals.com/Information/bootini.html