11 May
2007
11 May
'07
8:22 a.m.
On 11/05/07, Gordon JC Pearce <gordon at gjcp.net> wrote:
What drivers? It's a USB-to-Serial adaptor - it
should be a
class-compliant device. I have never come across one that actually
needed additional drivers to work in MacOS X or Linux. I haven't tried
one in Windows, but past experience suggests that it needs drivers for
*everything*.
From my experience, the "driver" for
class-compliant devices tends to
be just a file saying "Manufacturer ID XXXX
product ID YYYY is a
device using driver C:\WINDOWS\system32\genericclassdevice.dll" It
then ties the IDs and the location on the USB tree (!) to that driver.
Dumb.
(!) Yes, the location on the tree. We set up a lab here at McGill
with 2 USB devices standard for each workstation: TI DSP eval board,
and a USB oscilloscope. We then imaged the main station (with the
CodeComposer software which takes about 3hrs to install: WTF? lazy
programming I guess...) with the drivers (custom, from the mfg. CD's)
for the two USB devices... Once the images were copied onto the
student workstations and they got powered up, both USB devices
demanded drivers to be installed because the devices were plugged into
different USB ports than they were on the main station! Argh! (More
frustrating than it sounds because we didn't know that this was the
problem, of course. We had to go around 12 workstations and
sequentially install the driver 1, reboot, install driver 2, reboot...
ugh.)
That is beyond dumb. That is broken by design.
Joe.