Hello, I have AIM Toolkit (version 20250521) used to mount a 3GB ramdrive formatted as NTFS with temp files on it. The options are: Cluster size: default; Quick format; Enable NTFS Compression and Use AWE physical memory.
The OS is Windows 11 24H2 freshly installed.
Files on ramdrive seems to take the double of the space without any reason I can think of.
Deleting a 161MB file has freed 322MB, 189MB freed 379MB.
Like any developer, I would first say: please use the last version before any report. Several bugs have been fixed.
That said, what you are describing here has nothing to do with the ramdisk. This is the result of the NTFS compression.
Besides, using NTFS compression in a static ramdisk does not change the amount of RAM used.
In most cases, using the dynamic memory allocation feature is more interesting if you don't have a lot of RAM.
Please don't use both NTFS compression and dynamic memory, it does not work properly.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello, I have AIM Toolkit (version 20250521) used to mount a 3GB ramdrive formatted as NTFS with temp files on it. The options are: Cluster size: default; Quick format; Enable NTFS Compression and Use AWE physical memory.
The OS is Windows 11 24H2 freshly installed.
Files on ramdrive seems to take the double of the space without any reason I can think of.
Deleting a 161MB file has freed 322MB, 189MB freed 379MB.
What's wrong with my ramdrive?
Thank you
Like any developer, I would first say: please use the last version before any report. Several bugs have been fixed.
That said, what you are describing here has nothing to do with the ramdisk. This is the result of the NTFS compression.
Besides, using NTFS compression in a static ramdisk does not change the amount of RAM used.
In most cases, using the dynamic memory allocation feature is more interesting if you don't have a lot of RAM.
Please don't use both NTFS compression and dynamic memory, it does not work properly.
Thank you, without compression, now the space is calculated correctly.
Now I have another issue, but I start a separate thread,