@WilleHelm Hello! Thank you for the answer! How can i do this with a cli interface? I can't find appropriate option....
@WilleHelm Hello! Thank you for the answer! How can i do this with a cli interface?
Fix uploaded.
OK, thanks for the report. I missed that you mounted an iso, and therefore you had a CDROM drive type. Yes, there is an issue. The GUI does not recognize the drive when it's a CDROM. Don't know how I could have missed that. I will fix that as soon as possible.
OK, thanks for the report. I missed that you mounted an iso, and therefore you had a CDROM drive type. Yes, there is an issue. The GUI does not recognize the drive. Don't know how I could have missed that. I will fix that as soon as possible.
Actually i tried in a VM with a clean Windows 10 22H2 IOT LTSC and i get the same error. https://imgur.com/a/pw36gCO
Actually i tried in a VM with a clea Windows 10 22H2 IOT LTSC and i get the same error. https://imgur.com/a/pw36gCO
Actually i tried in a VM with a clea Windows 10 22H2 IOT LTSC and i get the same error.
I regularly unmount AIM disks without any issue, no matter it's a ramdisk or an image file. Could it be specific to Windows 11 25H2? For now I have no machine with this version, so could someone confirm the issue?
Hi there. I'm trying this version under Windows 11 25H2 and when i try to unmount an iso from the right click context --> unmount virtual disk, i got an error which says that the drive is not an AIM virtual disk (incorrect function). I can unmount successfully from an elevated command line with the command: aim_cli --dismount=devicenumber
Hi! This may be more of a formal error. I have noticed in all of my Event Viewers this weekly error because Defrag fails to optimise it (although it's unnecessary of course). It is set to dynamic allocation in AWE mode with Release Method Automatic. I didn't investigate further yet and just wanted to let you know.
By activating the option Allocate Memory Dynamically before creating the drive it uses memory only if needed.
Who knows? Disabling the Swap File is neither recommended nor does it lead to any performance gains. Windows uses your disk anyway if needed to keep the system stable in extreme situations. It is easy to fill up all your RAM with a single application if configured to do so by accident or intentionally. Modern Windows can handle everything optimal the way it is on automatic; the times when it used disk space 1,5x of your RAM it long past. With your Swap File at default AIM's Memory Type option works...
Who knows? Disabling the Swap File is neither recommended nor does it lead to any performance gains. Windows uses your disk anyway if needed to keep the system stable in extreme situations. It is easy to fill up all your RAM with a single application if configured to do so by accident or intentionally. Modern Windows can handle everything optimal the way it is on automatic; the times when it used disk space 1,5x of your RAM it long past. With your Swap File at default these three options do exactly...
RamDyn should now reduce the risk of data loss in critical situations: Detection of low system memory no longer cancels the request but only generates a warning. Request is paused until the user clicks on a button. A "retry" button is now available in case of memory allocation error. Request is also paused in this case. ⠀ For now, messages are only in english. I should have done that sooner but better late than never. ⠀ ⠀
RamDyn should now reduce the risk of data loss in critical situations: Detection of low system memory no longer cancels the request but only generates a warning. Request is paused until the user clicks on a button. A "retry" button is now available in case of memory allocation error. Request is also paused in this case. ⠀ For now, messages are only in english. ⠀ ⠀
RamDyn should now reduce the risk of data loss in critical situations: Detection of low system memory no longer cancels the request but only generates a warning. Request is paused until the user clicks on a button. A "retry" button is now available in case of memory allocation error. Request is also paused in this case. ⠀ For now, messages are only in english. ⠀
RamDyn should now reduce the risk of data loss in critical situations: Detection of low system memory no longer cancels the request but only generates a warning. Request is paused until the user clicks on a button. A "retry" button is now available in case of memory allocation error. Request is also paused in this case. For now, messages are only in english.
RamDyn should now reduce the risk of data loss in critical situations: Detection of low system memory no longer cancels the request but only generates a warning. Request is paused until the user clicks on a button. A "retry" button is now available in case of memory allocation error. Request is also paused in this case. For now, messages are only in english.
RamDyn should now reduce the risk of data loss in critical situations: Detection of low system memory no longer cancels the request but only generates a warning. Request is paused until the user clicks on a button. A "retry" button is now available in case of memory allocation error. Request is also paused in this case. For now, messages are only in english.
RamDyn should now reduce the risk of data loss in critical situations: Detection of low system memory no longer cancels the request but only generates a warning. Request is paused until the user clicks on a button. A "retry" button is now available in case of memory allocation error. Request is also paused in this case. For now, messages are only in english.
RamDyn should now reduce the risk of data loss in critical situations: Detection of low system memory no longer cancels the request but only generates a warning. Request is paused until the user clicks on a button. A "retry" button is now available in case of memory allocation error. Request is also paused in this case. For now, messages are only in english.
RamDyn should now reduce the risk of data loss in critical situations: Detection of low system memory no longer cancels the request but only generates a warning. Request is paused until the user clicks on a button. A "retry" button is now available in case of memory allocation error. Request is also paused in this case. For now, messages are only in english.
RamDyn should now reduce the risk of data loss in critical situations: Detection of low system memory no longer cancels the request but only generates a warning. Request is paused until the user clicks on a button. A "retry" button is now available in case of memory allocation error. Request is also paused in this case. For now, messages are only in english.
I come back to this matter. Why checking the available memory? After all, I could just rely to the error generated by the allocation function. In fact, I don't check the available memory for the ramdisk, but to protect the whole system from becoming totally unusable. And the system needs virtual memory. That's why I think checking ullAvailPageFile even for physical allocation is the right thing. Perhaps I miss something, but I think the only issue of the large-page allocation method is that we cannot...
@w77 - I would assume that you have no plans on expanding to add support for ARM64, but I would certainly love to see it. Having used a mid-level Qualcomm Snapdragon X Plus laptop (32GB RAM), I think it is far superior in some respects (especially heat and quietness) to my far more expensive and beefier June 2025 Lenovo ThinkPad Intel/Nvidia laptop.
@w77 - I would assume that you have no plans on expanding to add support for ARM64, but I would certainly love to see it. Having used a mid-level Qualcomm Snapdragon X Plus laptop (32GB RAM), I think it is far superior in some respects (especially heat and quietness) to my far more expensive and beefier June 2025 Intel/Nvidia laptop.
Hi All ! Please tell me what the AWE option is for. My PC has 96 GB of RAM, and of course I don't use a swap file. Do I need this option to create a RAM drive or not?
Hi All! I can create a fixed-size RAM drive, and it works perfectly. But I don't understand how to create a dynamic RAM drive.
Hi v77, the fix works! Thank you so much! Best regards, J
For one of the two command line tools (aim_cli.exe), a flag was not explicitly specified for disks that are not read-only. It still worked well... except for removable disks. Thanks for pointing that. I have uploaded a quick fix. Please try.
Dear Forum, I'm using a program called Rekordbox that can write only to removable disks. As I don't have a USB key at hand, I thought I'd emulate one, by mounting an image using AIM Toolkit, ticking the "removable" checkbox, so that Rekordbox can then write to that image. I can successfully mount the image and the contained FAT32 volume shows up as removable in Rekordbox just like I need. However, the entire disk is read-only, i.e. I can not alter or write to the volume. In diskpart, the disk shows...
OK, thanks, I'll try that then.
Why not use the GUI? In the Advanced tab, there is a field "Run after mounting" that allows you to run anything just after the drive is ready. You could use swapadd in this field. With what you use in your previous topic, it would come to: "C:\Windows\System32\swapadd.exe" P:\pagefile.sys 256M 5G Just ensure that the correct full path to swapadd is present.
Hi everyone, I'm thinking about regrouping my Temp/Tmp folders and pagefile under the same roof instead of having two separate RAM disks. Since I'm running a .bat file that creates the RAM disk where the pagefile resides (the other is set via GUI), I'd like to know what commands I must add to it so that the disk is initiated, set to the proper size and file system, then points both user and system temp folders to it.
OK, I'm not sure I understood everything in your last post so here's what I did: I copy-pasted swapadd.exe onto the C:\Programmes\AIM Toolkit folder, then edited my .bat file with the complete path of both aim_ll and swapadd and now it's working. Thanks for your help! I'm still not sure what difference placing a pagefile in the RAM disk is going to make, but I wanted to try anyway.
Unlike ImDisk, AIM Toolkit copies no file in Windows\System32. As I said, you have to go in the installation folder (or write the full path to aim_ll). "ll" means "low level".
Unlike ImDisk, AIM Toolkit copies no file in Windows\System32. As I said, you have to go in the installation folder (or write the full path to aim_ll).
EDIT: it doesn't work. "aim_ll" isn't recognized as a command. Do I have to manually add AIM to the Path? I also tried "aim_cli" just in case, same result.
EDIT: it doesn't work. "aim_ll" isn't recognized as a command. Do I have to manually add AIM to the Path?
OK thanks, I'll try. Is that "ll" or "II" (two lower case L's or two upper case i's)? I'll copy-paste from your post, but just in case I need to type further down the road, you know...
You can just replace imdisk by aim_ll (in the installation folder). Most options are compatible. aim_ll -a -s 6G -m P: -p "/fs:ntfs /q /y" Never tried swapadd but it should work the same way.
Hi everyone, I finally adopted AIM Toolkit since ImDisk is now defunct (RIP 😢), but I don't know if I can create a pagefile in a RAM disk the way I used to with ImDisk. The syntax I used looked like this (just an example): imdisk -a -s 6G -m P: -p "/fs:ntfs /q /y" swapadd P:\pagefile.sys 256M 5G Swapadd is located in my Windows\System32 folder and ready to go, but I don't know: a) If AIM Toolkit supports it; and b) How to edit the command line above to make it work. 😐
OK, got it. I've uninstalled ImDisk and installed AIM instead. So far, so good. Thx!
Both can run simultaneously. But if you uninstall one of them, you should reinstall the other one. The main difference is that volumes are in fact emulated full disks that you can see in the Windows Disk Manager.
Hi everyone, I discovered the existence of AIM Toolkit completely by chance and came here. I've read several entries in the discussion board, including one where v77 says that "ImDisk is dead". As a long time ImDisk user, I'm wondering what are the advantages and drawbacks of switching to AIM Toolkit. I'm not worried about speed or that kind of thing, because those things are almost imperceptible and highly subjective, but overall stability is important for me. My main PC runs Windows 10 Iot LTSC...
also one extra annoying , when create 2 or more ramdisk , it som times not remember volume name and can mix names example i have 2 volumes Cache and Data, and after reboot Data can mount as Local Drive or Cache Cache
Latest exist nvidia driver. Not tested with dynamic ramdisk . The video itself works, but that "scroll" is annoying. especially when the video has black bars on the sides, it flashes on the left black bar. I'll try to make a video of this or screenshots to explain it more clearly.
There seems to be an incompatibility between the AIM driver and the graphic driver. Is the graphic driver updated? And does this occur with dynamic ramdisks? I cannot explain the second issue but I keep that in mind.
I created RAMdisk 1 for the Google Chrome cache and pointed it to empty Cache and Code Cache folders to clear them every system restart. Then I placed them using a symbolic link and added them to my Google Chrome profile. 2 for data I copy from a prepared folder with "deletion control" Local Extension Settings IndexedDB and also placed a symbolic link back into the profile. The file system is NTFS, the RAMdisk is fixed. so in result i have 2 disks Cache and Data - with autosaved when shutdown / reboot...
This means that the system does not even try to unfragment the memory in order to get a 2MB contiguous block. Hmm.. I think the system was under high memory pressure at the time and perhaps it was unable to do so. There are 32 GB of RAM, but there was an opened browser window with a lot of tabs opened, a VM with 8 GiB allocated to it was running, and I was also decompressing an archive, which was using %Temp%; that's when the message was displayed. If the system does not try to move anything, this...
With what you had as free pageable memory, testing ullAvailPageFile should not have generated an error. So we can indeed assume that the system could not allocate a 2MB contiguous block. This means that the system does not even try to unfragment the memory in order to get a 2MB contiguous block. And if the system does not try to move anything, this also means that I should test ullAvailPhys, as you suggested. However, a lot of users use this feature because they want their data to be kept in physical...
Possible mistake when large pages are used, ullAvailPageFile?
Sorry, there was a mistake on the website so it had not shown up separately as it should have done. Fixed that now!
If a user wants to lose control of his machine by letting a software decide what file can exist or not, it's his choice and he have to assume.* I like it! :)
By the way, I will never do that for any other vendor. If a user wants to lose control of his machine by letting a software decide what file can exist or not, it's his choice and he have to assume. I like it! :)
AIMtk-svc.exe and RamDyn.exe had these alerts. I made a false positive report. According to VirusTotal, it is now fixed for both files. I hope not to have to do that each time. By the way, I will never do that for any other vendor. If a user wants to lose control of his machine by letting a software decide what file can exist or not, it's his choice and he have to assume.
Solved itself. For completeness I attached a screenshot of the block log from yesterday. But today this did not happen anymore.
No no, thank you! You identified the problem and corrected it in no time at all!
It detects Trojan:Script/Wacatac.B!ml. Best regards, Micha
I am trying to use this feature to assit with downloading stuff to RAM directly. But HWMonitor and Task Manager show SSD activity and temperature increase. I've tried this https://steamcommunity.com/discussions/forum/1/458606877310501802/ mklink /d "C:\Program Files (x86)\Steam\steamapps\workshop\content\<app-id>" "R:\<game> Mods\" I've tried creating junction, I've tried the empty folder feature in program. Nothing works. </game></app-id> It shows SSD writes, then at one time it copies whole file...
Thanks again. It is now fixed and should work like before. aim_cli now uses by default the driver deviodrv instead of the shared memory method previously used, hence the bug. For command line users, you have to either add --io=shm to aim_cli, or ensure that the driver deviodrv is started.
Thank you both for your responses. “accrights” is a great tool too. I'd been struggling with secedit.exe's behavior, but it solved the problem in one go.
How much time did you spend to make all these measures? Did you really notice these differences by yourself? Are you making huge static ramdisks the whole day? But thanks. You perfectly illustrate what I was saying.
FYI: Speed test on a Intel Core Ultra 7 265K with 192GB of RAM which runs at 6400Mhz 32,39,39,102 AIM Toolkit 2025-10-22 Creating 170GB drive default settings 63 Seconds. Creating 170GB drive Quick Format enabled 0.5 Seconds. Creating 50GB drive default settings 22 Seconds. Creating 50GB drive Quick Format enabled 0.5 Seconds. Copying 50GB data from SSD to Ram drive 22 seconds Copying 50GB data from one memory drive to an other 50Gbyte memory drive takes 17 seconds. ImDisk 2025-02-06 Creating 170GB...
I cannot find it. Edit: It is in the archive files just below the line (not obvious): "Big ZIP files with compiled stand-alone exe-files for most of the utilities listed here and some more:"
I cannot find it.
I have a tool I call "accrights" that can do this if you like. To show assigned rights to Administrators group: accrights Administrators To remove “SeLockMemoryPrivilege”: accrights /remove Administrators SeLockMemoryPrivilege It is on my website https://ltr-data.se/opencode.html
For now, I changed the default download to the version 20250818. I asked Olof about this issue, as I cannot find a quick fix. I could also try to remove the use of aim_ll, but it would require more time.
The permission is granted to the administrators group. Without the group policy editor, it is indeed difficult to revert the change, but not impossible, with secedit.exe, or a PowerShell script such as that. I could add something to remove the permission, but if another software needs it, this can break it. And even you are not necessarily aware of that. For instance, 7-Zip does not ask you before changing this permission... So I would say, you should not worry too much about that.
Hi. I have a question. I understand that the Toolkit automatically adds the “SeLockMemoryPrivilege” permission as needed, but specifically, to which account is the “SeLockMemoryPrivilege” permission granted? I want to know how to revert to the original state after trying “large-page”. Also, if using the Home Edition, how can I check and restore this? As you know, the Home Edition does not include the Group Policy Editor.
Hi. This is a question. I understand that the Toolkit automatically adds the “SeLockMemoryPrivilege” permission as needed, but specifically, to which account is the “SeLockMemoryPrivilege” permission granted? I want to know how to revert to the original state after trying “large-page”. Also, if using the Home Edition, how can I check and restore this? As you know, the Home Edition does not include the Group Policy Editor.
Yes thanks, there is an issue. I will dig into that. It should be the update of aim_cli done in the version 20251015.
AIMtk installed cleanly as far as I could see, with all components selected and RAM disks work as expected, I have one running, but I am unable to mount a VMDK image using MountImg. From what I could see, because it spawns quickly, MountImg calls aim_cli and aim_ll with command lines similar to these: "C:\Program Files\AIM Toolkit\aim_cli.exe" --name=AIM99c4766dcc7 --filename="C:\Virtual Machines\Storage\Shared.vmdk" "C:\Program Files\AIM Toolkit\aim_ll.exe" -a -t proxy -o shm,hd,rw,fix -f AIM99c4766dcc7...
Wikipedia
Thanks. I will wait a few days, in case other translators also publish something. And also in case there is a bug, which is not impossible for this kind of release. ;)
Updated to AIM Toolkit 20251015.
When I start up, I automatically create a 32GB RAM disk and also redirect the paths %SystemRoot%\TEMP to (Ramdisk)X:"\Temp. My problem now is that when I boot into Windows 11 Safe Mode, I can't download any files using either Firefox or Edge. For some reason, both programs don't download the data to my desired folder, but first download it to %SystemRoot%\TEMP\xyz and then move it to my desired location. Why Firefox does this is a mystery to me, as I have disabled the HDD cache there myself. Since...
This release brings the support of large-page memory allocations for dynamic ramdisks. This means that Windows uses 2MB memory blocks instead of the usual 4KB blocks. The main advantage is that these blocks cannot be written to the pagefile, like AWE, but with a speed close to the virtual memory. 2 warnings though: - Like a hard drive, RAM can be fragmented. Therefore, finding a new 2MB block can be difficult and may require memory moves from the system, which can lead to a general slowdown. However,...