[time-nuts] USB and Mouse conflict persists

[Joop]

 quote: [On the tab "Port Settings" click "Advanced" and in that window 
 uncheck the
 box next to "Serial Enumerator"]
 This is a feature of the FTDI driver. Not something generic.

 What worked for me was to disable (postpone actually) the Windows PnP 
 device enumerator for a serial device. It works for hardware serial 
 ports as well as the USBtoRS232 converters.
 This can be done with a registry patch which adds the 
 "Skipenumerations" registry entry. Setting this to a big value skips the 
 possible detection of any device (such as a serial mouse) on a COM port.
 Search the net for details. E.g. here : 
 http://support.microsoft.com/default.aspx?scid=kb;en-us;283063

 Lots of the USBtoRS232 converters do not contain EEPROM to store a 
 unique serial number. Without it Windows cannot be sure you unplugged 
 the same device as you re-plugged in another USB port. Its behaviour is 
 to assign it a new COM port number. Re-plugging the converter in the 
 original USB port should bring back the same COM port number.
 You will need to patch the registry again if a new COM port number is 
 assigned. If you want to avoid this, look for USBtoRS232 converters that 
 have the option to program a USB serial number (like the FTDI FT232R 
 based ones)

 Joop - pe1cqp