Page 1 of 1


Posted: Wed Mar 20, 2013 6:41 pm
by Jeff

usbitcmd thinks "No USB mass storage devices found!" when called like this: 'usbitcmd l'

However, there is a device connected and the USB Image Tool exe finds it correctly. I guess this is a bug.

Furthermore, does usbitcmd (if it works) accept drive letters like o:?


Re: usbitcmd

Posted: Fri Mar 22, 2013 7:14 pm
by Alex
I assume, you have to start the command line tool with the /d option, if your device contains no valid file system. For that, the console has to be started with admin rights.