For those that don’t know, windows has a virtual device filesystem much like /dev on linux, however you are not able to query it directly. Part of this filesystem includes UUID like volume identifying. Windows actually uses these to assign the right drive letters to the right partitions.
Anyway, why am I droning on about all this? Well I wanted to setup VirtualBox (xVM) to directly access a flash drive a couple of months ago, now while in the documentation it told how to do it. They never mentioned how to find the volume name to do it with in the documentation. Anyway after a while trying to find out on google and not succeeding I gave up.
A couple of weeks ago I had a slight problem with some ntfs corruption, so I wiped the windows XP partition and installed Windows 7 RC x64. Next I tried to get EXT2IFS to read the linux filesystems, and while this worked fine in Vista compatibility mode (to bypass an OS check in the installer) Windows would not remember the drive letter assignments on reboot. So reading the EXT2IFS FAQ mentioned mountvol for manually getting volume UUID names and manually mounting volumes.
As this is exactly what I needed for VirtualBox and to put it in black and white for google and such.
To get Windows Volume Device Names of detectected partitions (mounted or not) one can use mountvol in cmd.
I wrote a little powershell script to mount each ext volume and put it in wondows task schedular to run automatically each system startup as the system account (only way to run something at startup with admin rights without UAC popups) and have reported the problem to the EXT2IFS developer.
Entries (RSS)