2008-07-20, 10:04
Some usb mass storage devices cannot recover from the mount method of the CFatXDevice (that tries to mount the device in the first place) . When the mount of the CFatXDevice is disabled then the CFat32Device mount works better. I Assume there are people that use FatX and Fat32 devices so both of the mounting options should stay in the code. So some sort of mounting priority of the usb device (FatX / Fat32) or some configuration parameter that disable FatX mount would be nice. To temporarily test this solution modify the CMemoryUnitManager::MountDevice and comment out the CFatXDevice instance creation and mounting.
The second modification (that is compulsory for increased compatibility) is the addition of the delay between the device powering-up and device accessing. Some devices apparently need this delay to function properly. Modify CFat32Device::Mount() and add Sleep(1000); at the very beginning of the method (as the first command of the method).
This solution enabled 2 of my USB mass devices (Verbatim Store & GO, iPod Nano) while preserved functionality of my old memory stick (Seitec - worked without this modification).
Hope this helps...
I could'n use tracker to report this because the tracker (I used provided link) throws this: ERROR: Artifact: Only Artifact Admins Can Modify Private ArtifactTypes
The second modification (that is compulsory for increased compatibility) is the addition of the delay between the device powering-up and device accessing. Some devices apparently need this delay to function properly. Modify CFat32Device::Mount() and add Sleep(1000); at the very beginning of the method (as the first command of the method).
This solution enabled 2 of my USB mass devices (Verbatim Store & GO, iPod Nano) while preserved functionality of my old memory stick (Seitec - worked without this modification).
Hope this helps...
I could'n use tracker to report this because the tracker (I used provided link) throws this: ERROR: Artifact: Only Artifact Admins Can Modify Private ArtifactTypes