Wizard

For me, if you set the options for the Temp folder on the RamDisk, at startup, some processes start writing there already before the ramdisk is created, and since I set the ramdisk on a mount-folder instead of a driveletter, this means the folder gets written to, then ramdisk startup comes along and finds the specified mount-folder is not empty and aborts the mount. Mind you, the ramdisk gets created, but it's the mount part that fails. Solution: Either don't use the options for Temp-folder, or figure...

To be honest with ya, I didn't think about it/notice it (Foldername). That's already good enough... No need to have a switch from running install.bat as I'm not running that anyways. I was asking to just have a set version=20250818 in it (or even a rem 20250818 or something like that would suffice, so my script would just read install.bat and interprete that, but then, indeed, I might aswell just read the foldername for that... Thanks for pointing that out...

It would suffice if you add a DOS-variable like set version=2025.08.18.0 to the install.bat. I can simply extract that and use it as the versionnumber... Or better, but don't know if possible, add file-version to the .cab ?

You put fileversion in ImDiskTk-x64.exe on my request in the past. I was using that to determine update-status through my scripts and auto-update if newer... Since AIMtk is just a zip/7z I can't do that 'trick' anymore... Don't know if, perhaps, you could add the fileversion to the zip/7z ?

Could you embed a version ID somewhere. Even if just declaring as a variable in the install.bat script would suffice. I'm trying to auto-convert all my imdisk installations with AIMtk. For imDisk I asked you before to embed a version ID which you did and it enabled me to write a "auto-update" script. Would like to do the same/re-use parts of that code for AIMtk after a one-time-only conversion... Thanx...

Alright. Never mind any longer. Got it working finally, after a day of trial and error. With all due respect, you're messing around alot with those services (I understand why !), but made this very difficult for me. GPO script runs as SYSTEM, but you should see it as a "stripped" SYSTEM, it does not hold all privileges, and therefor I had trouble trying anything manually from that script. I now leave it alone and let you do your magic in a sense, just only setting service to manual at shutdown and...

Everything works as it should. If I use RamDiskUI myself to create one on mountpoint, it works. If I set launch at startup, then reboot, it works. It's just that I need to somehow be able to intervene at startup to detect memory-size, then start the ramdisk with changed size setting (if VM-memsize changed). At shutdown-GPO script, I used to set the RamDisk Starter service to manual, so it wouldn't start at startup (to delay it). Then at GPO-startup script, I detect memory size, set the registry entries...

Also, I know figured out, it somehow can't use the Mountpoint, as it does start the RamDisk, you just don't see it. DiskMgmt.msc shows the created RamDisk, it's just not associated with the set MountPoint. If you then start RamDiskUI it doesn't "find" the ramdisk, showing you like there is none (unmount-button greyed out). If you then click Okay again to create one, it hangs (and later on, the whole system hangs at shutdown) at "Mounting ramdisk"... If, after booting, I goto DiskMgmt.msc first, add...