Windows 7 and Automounting with Ext2IFS
I, like many, have to work under different operating systems.
For data storage, I chose the ext3 file system. Under Windows, partitions were accessed using the Ext2IFS driver . With this configuration, I existed wonderfully and did not know any problems under WindowsXP. But here Windows 7 (x64) settled on my hard ...
Ext2IFS (v. 1.11a) works, but after each reboot you have to climb into the control panel, run the utility and re-mount the partitions. No matter how I struggled, the “usual” ways to make auto-mount work could not. I wanted to switch to using Ext2FSD ., But it hung the system when trying to shut down.
The problem was resolved when I remembered the mountvol utility.
The principle is simple:
After installing Ext2IFS and scattering the letters on the desired partitions, run mountvol in the console without parameters: Based on the information received, we write a bat-nickname for automatic mounting: It remains only to put it into startup. I would be grateful if someone would tell me the windows-way with creating keys in some tricky registry branches or setting the necessary checkmark somewhere in the wilds of administrative snap-ins ...
For data storage, I chose the ext3 file system. Under Windows, partitions were accessed using the Ext2IFS driver . With this configuration, I existed wonderfully and did not know any problems under WindowsXP. But here Windows 7 (x64) settled on my hard ...
Ext2IFS (v. 1.11a) works, but after each reboot you have to climb into the control panel, run the utility and re-mount the partitions. No matter how I struggled, the “usual” ways to make auto-mount work could not. I wanted to switch to using Ext2FSD ., But it hung the system when trying to shut down.
The problem was resolved when I remembered the mountvol utility.
The principle is simple:
After installing Ext2IFS and scattering the letters on the desired partitions, run mountvol in the console without parameters: Based on the information received, we write a bat-nickname for automatic mounting: It remains only to put it into startup. I would be grateful if someone would tell me the windows-way with creating keys in some tricky registry branches or setting the necessary checkmark somewhere in the wilds of administrative snap-ins ...
\\?\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:\
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}