Comment 4 for bug 741632

Yes, I fully appreciate this - but calibre should still not be doing anything with my floppy disk drive as part of the polling process. I appreciate that it may affect so few users that it's not worth your time to address (I guess not that many people have floppy disk drives any more), but I don't think it's correct to imply this isn't a bug in calibre. Under C/C++, one could use DeviceIoControl with the IOCTL_DISK_GET_MEDIA_TYPES to avoid erroneously polling floppy disks - unfortunately, I don't know python otherwise I'd gladly try to submit a patch to address this.

For info, there is a fairly high likelihood of android devices being 'partially detected' in this way because, when the device is connected via USB it asks the user whether they want to "charge only" or mount the SD card as a disk. I select "charge only" because that's what I want to do, and if I instead elect to mount the SD card as a disk in Windows, it's immediately *unmounted* on the phone which stops a whole bunch of apps working (any apps that are installed on the SD card, plus any apps that use the SD card to cache or store data such as the web browser, dropbox, etc).

Like I say, I do fully appreciate that I may be in a tiny minority of users who are affected by this (and as it happens my ebook reader is a kindle, so disabling the android plug-in works around the issue for me), but neverless it is a bug, I think.