6 replies to this topic

[gandalfmeister]

I've been using this great tool (imdisk ramdrive) for a couple of years now on Window 7.

I just upgraded to Windows 10, and installed 2.0.5.. sadly although it seems to work perfectly, the drive doesn't persist.

After every reboot I have to re-run the config UI. (didn't have to do this on Win 7!)

 

I understand there is a way to manually setup the event scheduler to invoke imdisk on startup - but when I run this command line I get the following error

 

C:\Users\Dad>imdisk -a -s 1024M -m R: -p "/fs:ntfs /q /y"

Creating device...

Created device 4: R: -> Image in memory

Error defining drive letter: Access is denied.

 

I've set it up as a task running as the administrators group and I still get an error (lts not logged )

 

Help?

Thx

[Olof Lagerkvist]

In Task Scheduler, have you ticked the box "run task with highest privileges"? If not, I would think that's probably what you need to do.

[gandalfmeister]

No I haven't - I'll reinstall and re-try. However - why did I not need to do any of this under Win7? I just installed it - check the run at startup and it all worked? Never had to look at the Task Scheduler before - ever!

[v77]

The drive is not supposed to persist across reboots, unless you are using Windows 8 and the hybrid sleep is activated.

The driver has a feature that allows you to mount a volume automatically, but it won't be formatted (see -P switch in command line).

If you have never used neither the -P switch nor the task scheduler, it means there was something else that was doing the job, such as ImDisk Toolkit.

[gandalfmeister]

Ah - OK - I see I'm confused. Yes - I've only ever used imDisk Toolkit. I haven't ever used the driver on its own. What I mean by "persist" is NOT that the contents remain - but that the drive is recreated every startup. With Windows 10 - this is  NOT the case, whereas it always has under  Windows 7. Is this a Windows 10 issue (or possibly the result of the Win7->Win10 upgrade process?)

[v77]

My guess would be that the drive is built (and that's why you get an access denied error), but is not visible in Explorer.

I noticed with Windows 10 that VirtualBox takes sometimes up to several minutes to show the shared drive mounted by the "guest additions" (each time I open a window of Explorer before they are loaded). And these ones are started with the same registry key than ImDisk Toolkit uses for notifying applications of the new drives (HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run).
I didn't yet reproduce the bug, but I assume that ImDisk Toolkit can suffer from the same issue that I saw with the "guest additions".

I used that to fix the same issue on Windows 7 and Vista, but these systems don't have as many bugs as Windows 10...
Windows 10 is definitely the most bugged system that Microsoft has made since Millenium.

Anyway, your ramdisk is built, but not (yet?) displayed by Explorer. By typing R: in the bar of Explorer, you should be able to use the drive though.

And therefore, I think you can remove your scheduled task.

[gandalfmeister]

Thanks for the suggestion. As an FYI I upgraded my daughters machine to Win10 today - it was also configured with a ramdrive via the toolkit. I did a minimal upgrade for her (retain apps & settings) and drive R:\ continues to work perfectly for her! (ironically doing a new Win10 install caused me the problem!!) I therefore agree that the driver is perfectly OK - its just an issue with the toolkit I assume. I'll re-install and retry your suggestion later. Thx