Regarding the Control Panel applet, I simply missed the "Create Virtual disk in physical memory" radio button. So my suggestion does not apply to the GUI. My mistake, sorry.
Regarding the command line I do think my comment/suggestion is valid.
Thanks for you suggestion and I understand that it is currently counter-intuitive in many ways. There are technical reasons for this though from the driver's point of view. There are two separate drivers involved with separate system requirements and the command line tool is meant to be a very low-level tool that should pretty much only send commands directly to the driver. There are other user interfaces of various kinds that are more end-user oriented that could present oddities like this to a user in a lot more intuitive way.
First, I suggest to amend FAQ #5 if it is meant to address the question how to create a RAM disk in physical memory using the command line. The question reads "I want a RAM disk that uses memory above 4 GB in 32 bit Windows. Can ImDisk do that?" and the answer starts by saying "If your 32 bit Windows version supports memory access above 4 GB through address window extension (AWE) and with physical address extension (PAE) turned on, it could be done ..". I run 64-bit Windows, and my concern is that the RAM disk be in physical memory and not in virtual memory (virtual memory may be swapped to the HD).
You are absolutely right. The FAQ is a little "dated" in many ways I really should try to update many things in it. I have changed #5 to something that also mentions physical memory now. Thanks a lot for this suggestion! (The edit seems to have messed up the FAQ quite badly though, I'll see what I can do about it shortly.)
Second, the syntax I suggest is more intuitive and consistent with the existing syntax for virtual memory RAM disks. If virtual memory is a type ("vm"), why isn't physical memory?
I agree, but there are technical reasons for the difference because of the separate driver that is used for physical memory allocation. For a very low-level tool like imdisk.exe I think it makes at least some sense to reflect how the driver works. At least as long as there are far better alternatives for new users.
One final point: I did not see the recommendation that first-time users should install the ImDisk Toolkit (nor did I find a link to the Toolkit on the download page http://www.ltr-data.se/opencode.html/). Maybe this recommendation can be made more prominent?
Could be. What do you think, could it be useful to move up the paragraph about ImDisk Toolkit (with the link) a bit and make it appear closer to the "basic" ImDisk driver links? Or should I have some small note close to the driver download link where I could recommend new users to scroll down to the ImDisk Toolkit paragraph? I am sure this could be bettered somehow, just not sure really how to do it!
(I haven’t tried the toolkit after reading Olof's reply, since right now my chrome browser for some reason blocks the download as possibly harmful …)
That is sadly a common problem. There was a false positive malware detection for that software a while ago and even though that seems to have been corrected Chrome still decides to block that website.
Thanks again. I hope you don't find that my suggestion is a trivial complaint. I just want to make a small contribution to this great project by trying to make life easier for first-time users, and save them some valuable time.
No problems! Suggestions are always welcome! (Hope you don't find my answers to "grumpy" either, that would in no way be my point with anything I write here!)
(*) I did not find this mentioned in the syntax, which makes it appear that –t is always required: "imdisk -a -t type -m mountpoint [-n] [-o opt1[,opt2 ...]] [-f|-F file] …. "
Very well spotted! This is obviously a very old mistake that nobody seem to have actually seen before. At least not myself and I have also never heard anything about it before. But it sometimes happens that almost 13 year-old mistakes get discovered too.