RamDrive stopped loading Image into RAM
Ramdisk for Windows and mounting of image files
Brought to you by:
w77
Menu
▾
▴
Been workin' fine for months, I load a 34GB image upon startup from the SSD into RAM. And today I turn it on and the Ramdrive/image is there, but it's not loaded into RAM, it's just working off the SSD. (where the image is stored).
In Mount Image File, I've tried checking the box "mount at windows startup" Loads it up right fine, but not into ram.
The only way I can get it to load is to go into the "Switch to Driver Interface" & Copy the image into physical memory. but that still won't load it up upon startup.
W10, I'm all GUI, no command line.
Dynamic ramdisk or not? In case of dynamic ramdisk, it would not even be created in case of image file loading error, so I assume the ramdisk is static.
In this case, the image file is loaded by the driver, like when you use the driver control panel.
Anyway, the strangest part is that it worked before and not now, and I see nothing that could interfer.
I've been trying so many things, from ever angle, I just must be confused. I'm sure I've just messed it up. Will you tell me the proper, step by step way to load my Ramdrive.img into Ram upon startup?
MY 34GB Ramdrive.img is in the root of C.
Right now, this is how it's set up:
&
&
Given the first screenshot, you are currently working directly on the image file. It's not a ramdisk.
That means all changes are directly written in the image file.
I would suggest to uninstall ImDisk Toolkit (remove all the parameters), reinstall it, and then use the RamDisk Configuration Tool.
Just go the the Data tab, select your image file in the first field, and click OK.
Reboot the system, and check whether the ramdisk is still here with its content.
So, if I unmount all drives, and try to uninstall the program, it uninstalls BUT with the error of "Installation Failed."
Humm. check the Event Viewer:
The system failed to flush data to the transaction log. Corruption may occur in VolumeId: RamDrive, DeviceName: \Device\ImDisk2.
(The device has been removed.)
It IS gone from computer's program list.
BUT "ImDisk Virtual Disk Driver" is still in Control Panel. Reboot, and I get my 34GB SDD based Image mounted to "E". Weird. I go into Computer Management > Services and Applications > Services > ImDisk Virtual Disk Driver Helper and I stop that service from running.
Reboot. Same, 34GB image is back loaded from SSD.
I try to umount and delete the image. It comes back (albeit unformatted and no data on it)
So whatever, I give up trying to remove that, so I install the software again (20191126) check all the boxes, or no driver, or no startup automatically, I try everything. Nothing changes after any reboot.
So whatever, I'll umount "E" that keeps coming back, go into RamDisk Configuration Tool and 3rd DATA tab load the Ramdrive image into Ram. Works perfect.
Reboot, The image isn't in RAM. I try to go into RamDisk Configuration Tool and mount my image into RAM to "R:\" now. Works. Reboot, works, but "E" keeps coming back, mounted on the SSD.
How can I remove "E" from keeps coming back and overriding anything I want to put on E?
I can't override it and I can't delete it, and I can't stop it from coming back after any reboot.
"Installation Failed." comes from the install/uninstall of the driver. The driver is installed through an .inf file and there is an issue with that. This is the first report I see about that.
Even if a volume cannot be unmounted, the uninstall of the driver does not produce this error.
Even with this error, the uninstall program of the Toolkit continues and deletes everything it can. So even if you used "Mount Image File" to mount an image file at startup, everything about that should be removed.
About your E: drive, if an image file is registered to be mounted at startup with "Mount Image File", you can unregister it by selecting the image file (it should be in the drop-down list) and then click on "Unmount" (it's said in the tooltips).
Nevertheless, the uninstaller also does it, so I am not sure this will work...
There is definitely something that interfers. Perhaps an antivirus?
What does that mean? If (in "Mount Image File") I go in and select the RamDrive.img that's loaded into "E" and click "Unmount":
While it unmounts just fine, it loads right back up when I reboot.
If I go into "ImDisk Virtual Disk Driver" and click remove, it removed it, but loads it back upon reboot. And I don't see anything in "RamDisk Configuration" in which I can umount E. (It's greyed out if I drop down to drive letter "E".
Sorry, I'm usually not so useless.
It now seems your language file is missing... You really have to find what is creating all this mess.
In case of a .img file, the file is directly mounted by the driver. The removal of the parameters by the GUI requires imdisk.cpl, located in %windir%\System32. You can try to remove them yourself, with regedit. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ImDisk\Parameters, and remove all the values.
Then, go to HKEY_LOCAL_MACHINE\SOFTWARE\ImDisk, and remove all the values starting by "Im0".
Reboot. Your E: drive should have disapeared. Reinstall the Toolkit, and force the reinstall of the driver (check the first option).
If it's not enough, well... I'll be out of ideas.
Welp, I deleted all the entries in the registry (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ImDisk\Parameters) rebooted, and it deleted the SSD mounted image that it sent to "E" and replaced it with my RAM mounted Image that I used to have on "R".
Exactly what I wanted to start off with! Perfect! Thanks for your help.