Autostart fail and CLI fallback
Ramdisk for Windows and mounting of image files
Brought to you by:
w77
Menu
▾
▴
As noted in RamDisk autostart sometimes fails , this is the exact same problem I run into. It'll work for a few days, and then it won't.
I have a batch startup script that checks to see if the RAM disk was created (just a simple drive check), and if not, produce an error message and open the GUI interface.
Instead of the GUI interface, I want to just fallback to a command line creation of the default configuration with 16 GB. But the command line tests tries aren't working.
As noted in mount commands, I'm trying the command line "aim_ll.exe -a -t vm -s 16G -m R: -p "/fs:ntfs /q /y", I'm not getting any result.
The aim_cli.exe, RamDyn.exe, and aim_ll.exe outputs without commands (to get the "help" information), don't provide a great deal of assistance, and I've searched throughout web for any solution. While it explains the switches in general, there isn't examples using a completed working command line.
Can anyone provide a command line example, using my 16 GB default, of how to mount it?
I also have AutoHotkey available, but the window titles and text can't be grabbed correctly to interact with the GUI interface, otherwise I'd just use that instead.
Last edit: Jack 2025-09-22
Are you using the last version?
The command "aim_ll.exe -a -t vm -s 16G -m R: -p "/fs:ntfs /q /y" is correct ("-t vm" is not mandatory).
Check that you are in the correct folder and you have administrative privileges.
The syntax help can be get by starting aim_ll without argument in a command prompt.
For RamDyn, you can also start it without argument, or even start it from Explorer, because it displays a message box.
aim_cli is for image file mounting only.
Perhaps I should provide a diagnotic tool...
When the ramdisk is not created at startup, could you please run this command file and then attach the file diag.txt to your message?
Yes, the latest. The next time it fails, I'll run the command file.
Documentation would really be helpful. The syntax generated doesn't provide an example, like in that command line string above. If I hadn't found that previous post, I wouldn't have been able to put that together myself.
I'll try this as a fallback.
Thank you so much!
Jack
It did fail on the next start, so I've attached the diagnostic file.
I then started it with the command-line, and it hasn't failed since...but if it does, it'll fall back to the command-line and restart it automatically with my script.
Thanks a lot. I didn't expect that this diagnostic script helps so much...
So here is what I see:
You have 16GB RAM and try to create a static ramdisk of 16GB, that is, a ramdisk that fills all your RAM, and even beyond because of the space used by the system.
This is the first issue. It can still work because you have a pagefile that increases your virtual memory.
In the current case, as the virtual memory in use is about 6GB, I would say that the memory allocation (done by the driver) has failed, and after a quick look, this explains why the service AIMtkRD is still running.
Here, there is something to do for me.
Anyway, with or without a fix from me, you must change your settings.
You have to either reduce the size of your ramdisk, or use a dynamic ramdisk.
With a dynamic ramdisk, you will be able to see the used command line in the Task Manager, but it is unlikely you need it.
Besides, every Windows system requires a certain minimum amount of RAM, without which it won't run. Creating a 16GB RAM disk on 16GB of RAM is crazy, IMO. ;)