I have created a ram disk with the attached configuration, when I start it two windows appear with a formatting request for the “R” disk and an “I” disk.
I reproduced the issue in virtual machines. Yes, it's really not clean at all...
Technically:
Currently, I am using aim_ll to create the disks. It creates the partition and Windows automatically assigns a drive letter. Then, the driver letter is removed and the requested drive letter is then applied.
After that, format.com is called to format the volume.
Perhaps it's not fast enough, but this explains why you get 2 format prompts (with a bug in Windows 11 24H2).
Unless Olof finds a way to fix that, what I can do is to switch to the API of AIM, which allows to create disks without partition.
Then, by creating the partition myself, I will have a better control on what is happening next.
This is a big work but it's interesting...
I am currently rewriting all the mounting procedure. This is really a hell of a work.
A lot of users and developers are annoyed by these format prompts.
Using the AIM API does not fix this issue. These prompts are generated by a service named "Shell Hardware Detection" (ShellHWDetection). It is easy to stop the service while the GUI is open and then restart the service at close, but at system startup, it's another issue.
Yes, at least on Windows 7, I got these prompts even at system startup.
So I will have to play with it, by respecting as much as possible the user's configuration.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
When I activate RAMDisk “R,” the formatting prompt always appears for two disks, “I” and “R.”
What are you doing exactly?
I have created a ram disk with the attached configuration, when I start it two windows appear with a formatting request for the “R” disk and an “I” disk.
Ok thanks. But is R: formatted if you does nothing with the prompts?
Yes.
The same configuration with ImDisk Toolkit has never given me any problems.
Last edit: OA Stubby 2025-02-27
Thanks. I have an idea but... It will require some work.
I reproduced the issue in virtual machines. Yes, it's really not clean at all...
Technically:
Currently, I am using aim_ll to create the disks. It creates the partition and Windows automatically assigns a drive letter. Then, the driver letter is removed and the requested drive letter is then applied.
After that, format.com is called to format the volume.
Perhaps it's not fast enough, but this explains why you get 2 format prompts (with a bug in Windows 11 24H2).
Unless Olof finds a way to fix that, what I can do is to switch to the API of AIM, which allows to create disks without partition.
Then, by creating the partition myself, I will have a better control on what is happening next.
This is a big work but it's interesting...
Last edit: v77 2025-02-28
I am currently rewriting all the mounting procedure. This is really a hell of a work.
A lot of users and developers are annoyed by these format prompts.
Using the AIM API does not fix this issue. These prompts are generated by a service named "Shell Hardware Detection" (ShellHWDetection). It is easy to stop the service while the GUI is open and then restart the service at close, but at system startup, it's another issue.
Yes, at least on Windows 7, I got these prompts even at system startup.
So I will have to play with it, by respecting as much as possible the user's configuration.