
I, like many, have to work under different operating systems.
For data storage, I chose the ext3 file system. Under Windows, access to partitions was performed using the
Ext2IFS driver. With such a configuration, I existed remarkably and did not know any problems under WindowsXP. But here on my hard settled Windows 7 (x64) ...
Ext2IFS (v. 1.11a) works, but after each reboot you have to go into the control panel, run the utility and re-mount partitions. No matter how I fought, “ordinary” methods could not make automounting work. I wanted to switch to
Ext2FSD ., But he hung up the system when trying to shut down.
The problem was solved when I remembered the mountvol utility.
The principle is simple:
After installing Ext2IFS and scattering the letters on the necessary partitions, run mountvol in the console without parameters:
\\?\Volume{501e4a5f-f269-11de-b252-0018f3440074}\
U:\
\\?\Volume{501e4a65-f269-11de-b252-0018f3440074}\
K:\
\\?\Volume{501e4a5e-f269-11de-b252-0018f3440074}\
X:\
\\?\Volume{501e4a64-f269-11de-b252-0018f3440074}\
D:\
\\?\Volume{501e4a62-f269-11de-b252-0018f3440074}\
P:\
\\?\Volume{501e4a61-f269-11de-b252-0018f3440074}\
M:\
\\?\Volume{501e4a63-f269-11de-b252-0018f3440074}\
E:\
Based on the information received, we write the bat-nick of the automatic mount:
')
mountvol U:\ \\?\Volume{501e4a5f-f269-11de-b252-0018f3440074}
mountvol K:\ \\?\Volume{501e4a65-f269-11de-b252-0018f3440074}
mountvol X:\ \\?\Volume{501e4a5e-f269-11de-b252-0018f3440074}
mountvol D:\ \\?\Volume{501e4a64-f269-11de-b252-0018f3440074}
mountvol P:\ \\?\Volume{501e4a62-f269-11de-b252-0018f3440074}
mountvol M:\ \\?\Volume{501e4a61-f269-11de-b252-0018f3440074}
mountvol E:\ \\?\Volume{501e4a63-f269-11de-b252-0018f3440074}
It remains only to shove it into autoload.
I would be grateful if someone tells you the windows-way with creating keys in some tricky registry branches or installing the necessary tick somewhere in the wilds of administrative snap-ins ...