FAQ
Q1: Why can't the MTPdrive recognize my device?
A1: The MTPdrive can work with any device operating MTP mode. It can be any make or brand, as long as the device is visible in the Windows Explorer.
If you can access the files in the device only using proprietary software bundled with your device, not by Windows Explorer, then the MTPdrive cannot work with it.
Q2: Why does Windows Explorer start downloading the files immediately after the drive letter is mapped?
A2: This is a "feature" of Windows Explorer. When you use Windows Explorer to explore a local drive, it looks for additional information about the files - metadata. In case of pictures it typically reads EXIF information embedded inside of the picture files. To obtain the metadata, just a portion of a file needs to be read.
Because an MTPdrive mapped drive looks the same as any other local drive letter, the Windows Explorer attempts to read the picture metadata as usually. Here the same request for a partial read must be accomplished by full picture transfer, as the MTP protocol does not support partial file reads. Sometimes this "feature" can cause the trial limit quota in the MTPdrive to be used up just for these automatic Windows Explorer downloads.
If you can access the files in the device only using proprietary software bundled with your device, not by Windows Explorer, then the MTPdrive cannot work with it.
Q3: Where can I find the registration number of my registered MTPdrive copy?
A3: Assuming you have already purchased and entered a registration key into the 'MTPdrive Settings' application. If you have not, please follow Q4. The registration number is displayed in the 'Registered by' section of any MTPdrive window:
E.g. in the screenshot above the registration number is '00000-00000-00000-00000-00000'.
Q4: I have purchased a registration key, how can I enter it to the MTPdrive?
A4: To enter a registration key to the MTPdrive, use the 'MTPdrive Settings' application. It can be launched several ways:
Once the 'MTPdrive Settings' application is running, click at the 'About' tab and there click at the 'Enter registration key...' button. Then follow the instruction displayed in the 'Enter registration key' window.
Q5: Is there a way upon log-on to the Windows to automatically map a device that is already connected?
A5: The already connected device get disconnected when you log off from your computer. If you log in back the device does not get mapped back as there is no "Device Connected" hardware event which could restore it.
To overcome this issue there is a command line option /startup which allows to restore this mapping again.
In order to have the mapping restored for a particular device you need to satisfy all these conditions:
Note: If some of the conditions are not met the mapping is not restored and there is no info/warning/error message showed.
Q6: Automatic mapping does work not in full (registered) version.
A6: In order to have the auto-mapping working completely automatically, the "Device Connected" events need to be delivered by Microsoft Windows to the MTPdrive first (which is not the case by default). The easiest way to do it is to enable this MTPdrive Setting:
"Always route 'Device Connected' events for all devices (existing or newly installed) to the MTPdrive. Un-check if you want to configure it yourself in Windows AutoPlay/Device Stage."
Click here to see the Settings dialogOnce enabled/checked, close the MTPdrive Setting application and re-connect your device/camera to make it working.
If automapping still doesn't work:
Q7: Is it possible to initiate a drive letter mapping programmatically from the command-line?
A7: The MTPdrive supports command-line mapping since version 4.0.
