First of all, thank you for developing and maintaining AIM Toolkit.
I would like to report a usability issue with the RAM Disk GUI when managing multiple RAM disks mounted as NTFS folders rather than drive letters.
Current behavior:
I have several RAM disks configured to mount automatically into different folders.
When creating these disks sequentially through the GUI, everything works correctly. All disks are created and mounted as expected.
However, when I open the GUI later to modify or remove an existing disk configuration, I encounter a problem:
The GUI always displays the settings of the last configured RAM disk.
There is no way to select another previously configured RAM disk mounted as a folder.
As a result, I cannot edit or remove the configuration of a specific disk through the GUI.
The configurations are stored separately in the Windows Registry, and I can see and manually delete individual entries there. However, managing RAM disks directly through the Registry is inconvenient.
If I delete all configurations and recreate the disks from scratch, everything works correctly again. But this is not a practical solution when I only need to modify one disk.
Suggested improvement:
Would it be possible to add a dropdown list or another selection mechanism to the GUI that displays all configured RAM disks, including those mounted as NTFS folders?
Selecting a disk could load its stored configuration into the existing GUI, allowing the user to edit or remove that specific configuration.
Since the configurations are already stored individually in the Registry, I hope this could be implemented without major changes to the underlying RAM disk functionality.
Thank you for considering this suggestion.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The dropdown list already exists, and the "Unmount" button just above the list allows to remove the ramdisk from the registry (as said in the tooltip).
However, yes, selecting a previous ramdisk does not update the options of the GUI. I will put that on my list.
Hello,
First of all, thank you for developing and maintaining AIM Toolkit.
I would like to report a usability issue with the RAM Disk GUI when managing multiple RAM disks mounted as NTFS folders rather than drive letters.
Current behavior:
I have several RAM disks configured to mount automatically into different folders.
When creating these disks sequentially through the GUI, everything works correctly. All disks are created and mounted as expected.
However, when I open the GUI later to modify or remove an existing disk configuration, I encounter a problem:
The GUI always displays the settings of the last configured RAM disk.
There is no way to select another previously configured RAM disk mounted as a folder.
As a result, I cannot edit or remove the configuration of a specific disk through the GUI.
The configurations are stored separately in the Windows Registry, and I can see and manually delete individual entries there. However, managing RAM disks directly through the Registry is inconvenient.
If I delete all configurations and recreate the disks from scratch, everything works correctly again. But this is not a practical solution when I only need to modify one disk.
Suggested improvement:
Would it be possible to add a dropdown list or another selection mechanism to the GUI that displays all configured RAM disks, including those mounted as NTFS folders?
Selecting a disk could load its stored configuration into the existing GUI, allowing the user to edit or remove that specific configuration.
Since the configurations are already stored individually in the Registry, I hope this could be implemented without major changes to the underlying RAM disk functionality.
Thank you for considering this suggestion.
The dropdown list already exists, and the "Unmount" button just above the list allows to remove the ramdisk from the registry (as said in the tooltip).
However, yes, selecting a previous ramdisk does not update the options of the GUI. I will put that on my list.
Last edit: v77 3 days ago