Posted on May 17, 2011 at 12:47there's no ST driver. USB CDC is a standard and windows (32-bit) supports it. the ''driver'' you mention is only a text file (.inf) saying that for a specific VID/PID device, windows should load the standard driver. if your particular OS supports CDC then you should be able to configure it so that the CDC driver loads.
(the .inf file shouldn't be necessary, the device describes enough of itself so that any OS should be able to load the driver -automatically or at least with manual configuration-, just like windows loads the mouse driver no matter what the make/model of the mouse. this is all part of a repulsive plan by the Microsoft mafia to charge hardware developers for the privilege of allowing windows users to use their hardware. as you may know, in 64-bit versions of windows the .inf file *MUST* be electronically signed by the Redmond mobsters or otherwise the device will be rejected. the user isn't allowed the option of bypassing the signature checking; only the mobsters decide what drivers run on the machines of the unfortunate windows users -if indeed the machines can be considered theirs once they are owned by the windows virus. the hardware manufacturers must pay the mobsters and pass the cost down to their users, while the users don't realize how deep Microsoft is reaching into their pockets because they are busy marveling at the cute translucent little window title bars. I can't understand how the DOJ allows this. plus I guess any 3rd party solution (hack) to this anticompetitive and freedom destroying practice would be swiftly sued out of existence using the obnoxious DMCA, so I don't even expect one to ever appear. let ignorant windows users be scammed.)
(as a hack, of course you can use someone else's VID/PID to bypass signatures, provided that the device you're ''cloning'' has the same CDC interface. btw, you can be sure that the successor of USB will use ID signatures to plug this hole.)
