On 19 Sep 2003, at 14:16, Tom wrote:

> 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?

Stupid, stupid windows - it  /knows/ a working mouse is present but looks for another
one as well - DUH!
Try reporting the bug to microsoft...

George Smith

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