Hopefully someone has some insight.
I use a USB to serial converter to feed the GPS stream from my Onstar Interface . My Car PC does not have a serial port, so this is what I am stuck with.
Now, If I boot my computer before starting my truck (and sending an NMEA stream through the converter) my CarPC boots fine. If I boot after starting truck, CarPC interprets Stream and converter as a USB mouse. No matter what I do, disabling, etc, it always happens. If I unplug the converter, it again boots fine.
Is there a way to set what the USB device recognizes as in XP Pro? Like I said, if I disable the USB mouse device, it still boots recognizing as a mouse, not a serial port.
Anyone have any tips?
A relay and a delay on timer should solve it. I had a car pc that did the same thing and was hard to fix. I had to disable the mouse driver that the serial usb adapter was using key strokes all the while the mouse pointer is bouncing all over the place.
Oh, that's it! Disable the serial mouse detect with the BOOT.INI switch /NOSERIALMICE=COMx, not USB. It's a virtual serial device so it's getting to it through that.
or all the options...
Did your serial -> usb adapter come with drivers? I have one from Belkin and when I plug it in it recognizes it as the port replicator, not mouse. If what was suggested above doesn't work out for you maybe installing some generic drivers would help.
When dtr is raised, a serial mouse will send an M character to indicate to the OS there is a serial mouse connected to the port. His problem was that when the OS was doing it's serial mouse check by raising dtr, the gps device would start sending nmea data back. This happens to contain several M characters, for example:
... or something to that extent. Glad to see a workaround posted.
I had similar problem; after researching and experimenting I found out that there is a big difference on the usb serial adapters. First I got one of those low-cost adapters from ebay. With that I got several installation errors and when I finally got it installed successfully I got similar problem as yours. I couldn't get it working so I bought a more expensive USB to Serial adapter and it worked flawlessly. The cheap model had drivers from Prolific, the expensive have drivers from a company called FTDI. Apparently it makes a difference.