One of the reasons I was fiddling with linux was an outrageously annoying problem with XP: if I have a serial device plugged into a serial->USB converter, and there's dataflow on that device during boot-up, windows automatically tries to figure out what the device is so it can configure it for you. It's a "feature", I guess.
So, with my new USB-only set-up in the new airplane if I boot up with the GPS on XP think's it's an "HID device" (fancy name for a mouse but it isn't loading it as a mouse). The screen goes nuts like the touchpad has been possessed by demons (uh, no comment), things get "clicked", and the operator goes crazy.
It's a common problem with an easy fix when it detects a mouse, but the easy fix doesn't seem to work with this "HID device". I'll get the problem "fixed" for awhile, then either it comes back or the dataflow from the GPS fails.
Seems like you should be able to tell the OS "hey stupid, stop worrying about trying to figure out what might be connected - take my word for it that it's a simple serial port and relax".
I bet Doc's laughing by now.
Since you kind of have to hardwire the drivers in fedora/ubuntu/etc I figured that wouldn't be a big problem. I'm hoping Win7 will be a little less prone to "the computer user is a moron so I have to take things into my own hands" like XP was.
There's good news though; my
camera interface has successfully removed any requirement for parallel ports in my airplane setup, and except for the little "hid device" weirdness I have all my camera interfacing (triggering and data-comm), video, and GPS all going through a single USB connection! :laugh: