Tom,

You should be able to get rid of this problem by editing C:\BOOT.INI and
add the /NOSERIALMICE parameter to the windows boot string. To edit
BOOT.INI you must do ATTRIB -r -s -h BOOT.INI to reset the readonly,
system and hidden flags.

The problem is caused by your device sending an ASCII string (during
boot) which looks like a serial mouse string. Windows then starts a PNP
serial mouse installation. You get similar problems with serial GPS
devices.

Regards, Peter Moreton


> -----Original Message-----
> From: pic microcontroller discussion list
> [mailto:PICLIST@MITVMA.MIT.EDU] On Behalf Of Tom
> Sent: 19 September 2003 22:16
> To: PICLIST@MITVMA.MIT.EDU
> Subject: [PIC:] USB mouse confusion
>
>
> I'm using the FTDI USB chips interfacing to a PIC to move
> into the "USB
> present" from the "RS232 past".
>
> Everything works correctly - most of the time.  But every
> once in a while
> when plugging in a USB cable, Windows decides it's not a 232 port this
> time; rather, it thinks I've just plugged a serial mouse into
> the port.  My
> PIC program is sending ascii data but Windows interprets it as mouse
> commands and everything on the screen begins taking on a life
> of it's own.
> The real mouse still works but can't keep control.  If the
> system isn't
> stopped quickly, "Very Bad" things will occur. Like icons on
> the desktop
> moved all around, various settings changed and so on.
>
> Does anyone know what causes this to occur and what can be
> done to prevent it?
> TIA,
> Tom
>
> --
> http://www.piclist.com hint: PICList Posts must start with ONE topic:
> [PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads
>

--
http://www.piclist.com hint: The list server can filter out subtopics
(like ads or off topics) for you. See http://www.piclist.com/#topics