XP serial port behaviour

  • Thread starter Thread starter Andres2c
  • Start date Start date
A

Andres2c

Briefly:

We have a device that continuously sends data to the computer via a
serial cable. When XP starts, the mouse behaves erratically and it's
almost impossible to operate the computer. As if XP thought we had a
serial mouse on that port and began 'reading' the mouse movements and
clicks. And the result is a mix from the data and the real mouse
movements. But there is no trace of this 'serial mouse' on the
hardware list, and we couldn't find a way to tell XP not mix COM1
incoming data with the real PS/2 mouse. And we don't have a USB mouse
to test with.

We have found that if we attach the cable *after* Windows finishes
starting, the mouse works ok and the data from the device keeps coming
ok on COM1.

We know that only USB devices -and not serial/parallel/PS/2- should be
plugged after the machine is started, but we couldn't find any other
solution.

Any ideas, anyone?

Thank you
 
Check in the Bios to see what IRQ you are using for the Serial Port. If
the other serial port is unused then disable it to
free up a IRQ. Or even switch to the other serial port. But still disable
the one that is unused.
 
Thank you for the tip.
Sadly, the serial device is not working anymore so our problem is gone
for the time being (but not really solved). We'll try it when it's
repaired and then report the results.
 
Briefly:

We have a device that continuously sends data to the computer via a
serial cable. When XP starts, the mouse behaves erratically and it's
almost impossible to operate the computer. As if XP thought we had a
serial mouse on that port and began 'reading' the mouse movements and
clicks. And the result is a mix from the data and the real mouse
movements. But there is no trace of this 'serial mouse' on the
hardware list, and we couldn't find a way to tell XP not mix COM1
incoming data with the real PS/2 mouse. And we don't have a USB mouse
to test with.

We have found that if we attach the cable *after* Windows finishes
starting, the mouse works ok and the data from the device keeps coming
ok on COM1.

We know that only USB devices -and not serial/parallel/PS/2- should be
plugged after the machine is started, but we couldn't find any other
solution.

Any ideas, anyone?

Thank you
Click to expand...

Micrsoft knowledge base #283063 or add /noserialmouse to
boot.ini

/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.

http://www.winguides.com/registry/display.php/1268/
 
this boot.ini setting only affects nt4, it will not fix the problem on win2k
and beyond. to fix open up device manager, view by connection. find the
serial port and the mouse underneath it. *disable* the mouse device, do not
uninstall it. disabling will stop the driver from loading. uninstalling
will only reinstall the device the next time it is "discovered"

d

--
This posting is provided "AS IS" with no warranties, and confers no rights.
Please reply to newsgroups only.

Si Ballenger said:
Briefly:

We have a device that continuously sends data to the computer via a
serial cable. When XP starts, the mouse behaves erratically and it's
almost impossible to operate the computer. As if XP thought we had a
serial mouse on that port and began 'reading' the mouse movements and
clicks. And the result is a mix from the data and the real mouse
movements. But there is no trace of this 'serial mouse' on the
hardware list, and we couldn't find a way to tell XP not mix COM1
incoming data with the real PS/2 mouse. And we don't have a USB mouse
to test with.

We have found that if we attach the cable *after* Windows finishes
starting, the mouse works ok and the data from the device keeps coming
ok on COM1.

We know that only USB devices -and not serial/parallel/PS/2- should be
plugged after the machine is started, but we couldn't find any other
solution.

Any ideas, anyone?

Thank you
Click to expand...

Micrsoft knowledge base #283063 or add /noserialmouse to
boot.ini

/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.

http://www.winguides.com/registry/display.php/1268/
Click to expand...
 
There is an easier way (someone in the GPS group found it
a while ago). Boot your computer with the device plugged in
to the com port so it goes nuts. Now unplug the device so you
have control with the mouse. In device manager, select the
pointing device windows *thinks* it knows about and select
"do not use" (or something close to that). This will leave the
com port active, but windows now knows not to use the
"pointing device" on that port. Works great.

--
Mike "mikey" Fields
http://home.comcast.net/~mike.fields/
outgoing email scanned by Norton Antivirus ... is that good ?

Linux users brag on how long their system stays up,
Window users assume it's a temporary condition ...
 
NoSerialMouse: Simple Fix Utility

Hello,

For several times I was (and my customers, too) a vitim of 'crazy mouse jumper', but I tired to try disable the false mouse device at Control Panel at Vista. So, I develop a small and simple utility to help fix it: NoSerialMouse. It's free and works with all Windows versions, including Windows 2000, Windows XP and Vista 64 and 32.
More detail (sorry, portuguese only) at:
http://www.marciowb.net/blog/2008/10/rapidinha-dispositivo-serial-windows

I hope that it helps someone.

Regards,
Marcio Wesley Borges
 
Back
Top