u3 detected as 'card reader'

Post Reply
mysteryman
Posts: 17
Joined: Dec 31st, 2007, 8:33 am

u3 detected as 'card reader'

Post by mysteryman »

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.
User avatar
Igor
Developer
Posts: 602
Joined: Nov 1st, 2007, 12:44 pm
Location: Saint Petersburg
Contact:

Re: u3 detected as 'card reader'

Post by Igor »

1. Which version do you use? beta 6 or beta 7?
2. In any case you can ask program to detect this device as a normal device. Just go to device properties -> Common tab and set up "Is this device a card reader" option to "No, it's another device" value
mysteryman
Posts: 17
Joined: Dec 31st, 2007, 8:33 am

Post by mysteryman »

Looks like that option will probably work (don't have time to test right now), but would be nice for it to detect it is U3 automatically. U3 is quite common on new flash drives, specifically sandisk/lexar.
User avatar
Igor
Developer
Posts: 602
Joined: Nov 1st, 2007, 12:44 pm
Location: Saint Petersburg
Contact:

Post by Igor »

mysteryman wrote:Looks like that option will probably work (don't have time to test right now), but would be nice for it to detect it is U3 automatically. U3 is quite common on new flash drives, specifically sandisk/lexar.
Yes, we know about this problem and we have (probably) fixed it in the beta 7 (were released yesterday). Which version of the program do you use?
Post Reply