imageUSB and SD drives

[gkclark]

I downloaded imageUSB V1.1 Build 1010 on the recommendation of a co-worker. He uses it to build server images on SD cards for deploying to HP servers. We both have Dell Latitude E6410 laptops and are both running Windows 7 64-bit Service Pack 1. We both have Ricoh SD drives built into the front of the laptop. When I insert an SD card in the slot, Windows AutoPlay pops open and allows me the option of exploring the drive, so I know Windows recognizes the drive. When I open imageUSB, the drive does not appear in my list of available drives. However, on my co-worker's laptop, imageUSB sees the drive and allows him to write-to or create-from the SD drive. I am an administrator on the PC. It doesn't matter if I right-click and run imageUSB as an administrator or not; it does not show the SD drive as available. The SD drive is mounted to Windows as the E:\ drive. I've pasted the log below:

14:27:17:986 - PassMark Software - imageUSB v1.1.1010
14:27:18:002 - Getting list of available removable USB drives...
14:27:18:002 - Inspecting Drive C:\...
14:27:18:002 - Inspecting Drive D:\...
14:27:18:002 - Inspecting Drive E:\...
14:27:18:002 - Inspecting Drive G:\...
14:27:18:002 - Inspecting Drive H:\...
14:27:18:002 - Could not open Drive H:\ Error No: 5
14:27:18:002 - Inspecting Drive S:\...
14:27:18:002 - Could not open Drive S:\ Error No: 5
14:27:18:002 - Inspecting Drive U:\...
14:27:18:002 - Could not open Drive U:\ Error No: 5
14:27:18:002 - Inspecting Drive X:\...
14:27:20:701 - Could not open Drive X:\ Error No: 5
14:27:20:701 - Inspecting Drive Y:\...
14:27:23:041 - Could not open Drive Y:\ Error No: 5
14:27:23:041 - Ready...

The drives with errors are network drives and can be ignored. What is the deal with the E:\ drive and why won't imageUSB allow me to write-to or read-from it?

[David (PassMark)]

We rely on the operating system to tell us what type of drive each drive letter is associated with.

The differences between the machines might be device driver related.


Starting imageUSB with the "-d" command line argument will save a more detailed debug log. The file name for the logfile is "imageUSB.log" and can be found in the same directory as the executable.

If you can send this log in, or post it, we will see if there is any useful information.

[gkclark]

Hi David -

Below is my log:

20-Nov-2012 - 14:17:10:536 - PassMark Software - imageUSB v1.1.1010
20-Nov-2012 - 14:17:10:536 - Getting list of available removable USB drives...
20-Nov-2012 - 14:17:10:536 - Inspecting Drive C:\...
20-Nov-2012 - 14:17:10:536 - Debug: Thread (7944) Drive C:\: Not of USB Type Skipping. DriveType 3
20-Nov-2012 - 14:17:10:536 - Inspecting Drive D:\...
20-Nov-2012 - 14:17:10:552 - Debug: Thread (7944) Drive D:\: Not of USB Type Skipping. DriveType 2
20-Nov-2012 - 14:17:10:552 - Inspecting Drive E:\...
20-Nov-2012 - 14:17:10:552 - Debug: Thread (7944) Drive E:\: Not of USB Type Skipping. DriveType 2
20-Nov-2012 - 14:17:10:552 - Inspecting Drive F:\...
20-Nov-2012 - 14:17:10:552 - Could not open Drive F:\ Error No: 5
20-Nov-2012 - 14:17:10:552 - Inspecting Drive G:\...
20-Nov-2012 - 14:17:10:567 - Debug: Thread (7944) Drive G:\ Size: 259215360 Bytes Volume: Other: FAT

20-Nov-2012 - 14:17:10:567 - Inspecting Drive H:\...
20-Nov-2012 - 14:17:10:583 - Could not open Drive H:\ Error No: 5
20-Nov-2012 - 14:17:10:598 - Inspecting Drive S:\...
20-Nov-2012 - 14:17:10:598 - Could not open Drive S:\ Error No: 5
20-Nov-2012 - 14:17:10:598 - Inspecting Drive U:\...
20-Nov-2012 - 14:17:10:598 - Could not open Drive U:\ Error No: 5
20-Nov-2012 - 14:17:10:598 - Inspecting Drive X:\...
20-Nov-2012 - 14:17:12:970 - Could not open Drive X:\ Error No: 5
20-Nov-2012 - 14:17:12:970 - Inspecting Drive Y:\...
20-Nov-2012 - 14:17:15:325 - Could not open Drive Y:\ Error No: 5
20-Nov-2012 - 14:17:15:325 - Ready...
20-Nov-2012 - 14:17:35:579 - Exiting...

Again, this is my E:\ drive. For whatever reason, imageUSB is not recognizing the SD drive as a valid USB drive type.

Thanks,
Gary

[David (PassMark)]

The drive type numbers returned refer to the Microsoft standards for bus types. See,
http://msdn.microsoft.com/en-us/libr...=vs.85%29.aspx

So a value of 'DriveType 2' means the device is a Atapi device.
ATAPI = AT Attachment Packet Interface. (with AT being the original IBM 'AT' computer)

Atapi is the interface used when a device is connected to a IDE socket on the motherboard and uses the SCSI protocol. Typically only CD/DVD drives and some now rare tape and floppy drives used Atapi.

I did some searching on the web and there does appear to be some card readers that use the USB bus and other that use IDE/Atapi. Strange that the same laptop model should give different results however.

We'll consider adding a check box to also display non USB drives to the app.