do you have the /FASTDETECT switch present?
It should be but some remove it. It is there because it replaces the Windows NT 4 switch /NOSERIALMICE. The switch exists so NTDETECT can support booting Windows NT 4 in a dual boot configuration. Windows Plug and Play device drivers perform detection of parallel and serial devices, but Windows NT 4 expects NTDETECT to perform the detection. Specifying the /FASTDETECT switch causes NTDETECT to skip parallel and serial device enumeration while omitting the switch causes NTDETECT to perform this enumeration (which is required for booting Windows NT 4).
Here is a list of the boot.ini switches with explanations.
I have a PABX system that runs on the serial port - com port (Win XP) which when plugged in is detected by PNP as a microsoft serial mouse. When detected it sends the mouse pointer crazy and I can't use the computer nor the pabx. It shows in the device manager as the microsoft serial mouse. I can unplug the pabx but it disappears from the device list so I can't disable it (even if that is the correct solution) as a mouse and when it's replugged in the pointer is too uncontrolable click on the device. If I start the computer then plug in the pabx on the com port it works fine but when rebooted with PABX plugged in the pointer goes crazy again. In this part of South Africa the electricity goes off sometimes for so long that the UPS dies. I despirately need a solution that is better than teach the operator to only plug the pabx in when the computer has booted.
Does anyone have a solution. Thanks, Jivan