u3 detected as 'card reader'
Posted: Oct 12th, 2008, 12:34 am
The detection routines for card readers should learn to detect U3 devices (often containing u3 in their device name).
U3 devices are flash drives which contain a standard fat/fat32 partition, as well as a virtual cd rom interface. Because the flash drive has two 'devices' according to windows, usbsr detects it as a card reader.
It would be best to tell u3 launchpad to eject which will turn off some running applications which will possibly allow you to eject without lock errors. (not sure if launchpad allows this remote ejection... maybe a WM_MESSAGE?)
However, if a person knows that there are no launched programs, the launchpad will close itself when the drive is removed manually. So, if the first way is not possible, it should simply not complain about the 'you should eject the drive not the device' error.
U3 devices are flash drives which contain a standard fat/fat32 partition, as well as a virtual cd rom interface. Because the flash drive has two 'devices' according to windows, usbsr detects it as a card reader.
It would be best to tell u3 launchpad to eject which will turn off some running applications which will possibly allow you to eject without lock errors. (not sure if launchpad allows this remote ejection... maybe a WM_MESSAGE?)
However, if a person knows that there are no launched programs, the launchpad will close itself when the drive is removed manually. So, if the first way is not possible, it should simply not complain about the 'you should eject the drive not the device' error.