It's a Kindle. It shows in Device Mgr as a Portable Device. Manually I can read. write & delete files on it . To all intents & purposes it is a disk drive. It just doesn't have a drive letter.
Sorry, I may not have read your opening post carefully enough and asked the right questions. It now looks like the device is showing in a device tree on your windows box, but the kindle filesystem is not necessarily integrated into the windows filesystem, but exists as an island on its own. There are generally 2 ways of moving files from a connected device to a target device
- Inclusion of the connected device file system or a part of it into the filesystem
- some form of file transfer protocol
On reflection, this appears to be the latter, which is disguising itself as the former. The device is integrated into the target system filesystem, but the device filesystem may not be. You are probably enabled to transfer files by software 'methods' [which may well be proprietary] being exposed to the target system graphical interface ie accessible via right click, but not necessarily exposed to the commands used for scripting.
Even if it is the latter case, it may still be accessible for scripting if you can see the underlying API, but I think you may find that assigning a drive letter may be the least of your problems - and may be irrelevant if you have to go to a scripting environment other than CMD.
Pages in this thread: 
Print Thread
XRaySpeX
