Hurray AIMtk! // MBR HDD versus GPT SSD
Ramdisk for Windows and mounting of image files
Brought to you by:
w77
Menu
▾
▴
Hi all!
I was very pleased with ImDiskTk for a long time now and so I immediately switched to AIMtk, of course.
The new approach of the AIM driver instantly solved two issues I had with the good old ImDiskTk:
1. Windows updates could not be integrated to an image on the RamDisk with NTLite
2. Ocenaudio was unable to detect the RamDrive's free space and kept spamming me with alerts
Regarding the topic, it is possibly defined by the driver itself and is more of a formality but I still would like to ask what you and the community think about it.
First, I wonder why it is recognized as HDD instead of SSD on my Windows 10 Pro x64 22H2 which would technically be more like it, I think. In any case, Windows handles and optimizes HDD and SSD differently. For example: Defrag on HDD, useless and adverse on SSD. On the other hand, what if it shows up as SSD and tries TRIM on that RamDisk?
Second, it is partitioned with MBR instead of modern and robust GPT. More compatible, yes, but on today's UEFI systems no problem and I think it's no good to use the old standard.
Regards,
WilleHelm
Last edit: WilleHelm 2025-05-18
Yes, a ramdisk is closer to a SSD than a HDD. Perhaps Olof can do something about that in the driver.
About GPT, I was thinking about that recently. Thanks to a partition property (GPT_BASIC_DATA_ATTRIBUTE_NO_DRIVE_LETTER), we could avoid to play with the service ShellHWDetection, at the cost of 40 KB more for each ramdisk, which seems to me acceptable.
Unless you want to create an image file of the ramdisk and mount it on Windows XP, which seems very unlikely, we can now use GPT.