When I run your build in one-time setup, it comes up unformatted. Seems to me, you should format it when you generate it. Youir instructions do not mention having to format it.
But this 'one-time' feature does not work. Next boot, there is no ram disk.
I have created a scheduled task which is the same as the 'one time' above except the Author is my username, not SYSTEM and I see no way to change that. The 'History' of that task shows that is has 'Never' run. At boot, I do not get 'anything' from you - consistent w Never having run.
When I open Admin cmd line, I can key in ' imdisk -a -s 12g -m I: -p "/fs:ntfs /q /y" ' and it works: I get 11 GB I: drive - formatted. If I right click on this drive to dismount it, it goes away. If I hit F3 to bring up the previous command, I can execute it again and it works again: I: is back. Repeat. This 'path' just 'works' tho it is the most inconvenient path imaginable.
If I navigate the Admin cmd line window to the cmd file I generated [in _imdisk directory], when I type in the name of the cmd file there, it 'runs' but does not produce a ram disk.
Why won't the one-time [format and] repeat at next boot; why won't the scheduled task work, even tho the command line w same information does work? How can I capture the CMD line procedure in to a desktop icon so I can manually do this w a single click? Running the above imdisk command line as .cmd and as .bat is the same. They both 'run' and [high speed] scroll dozens of B&W operations but neither produces a ram disk.
I have read that it cannot be done as startup task, since that path would allow malware to load and run [Admin], so only the scheculed task is legal/available. It just doesn't work.
I had this working w your software 20 years ago. W2000? 98? 95? Probably single line added to autoexec.bat back then.
I see from the screen prints, attached, that the task in the list is yours, SYSTEM, and not the one I generated. It has run twice w different results [140 & 106].
Attached: total task data & .cmd file
What do you mean by "one-time" feature?
The Imdisk Toolkit does not use scheduled tasks. It can install several user mode services, depending on the used features, and two drivers ("imdisk" and "awealloc"). That's all.
If you have a scheduled task, it is created by something else.
If you attempt to create a ramdisk with a scheduled task "At system startup", the ramdisk should be created, but the drive letter may not appear in Explorer.
Why not simply use the GUI?
Somewhere at the imdisk site or during installation, the s/w brags about the new features and last one mentioned is if you give the parameters now, it will set up your ram disk 'now' and you never have to do it again. That's the 'one time' feature. I did that and did get a ram disk, but also got window saying I'd hav gto format it before I could use it [this is mentioned in my input] so I did that and that worked, too. But on reboot, there was no such ram disk.
It's strange that you say im does not use scheduled tasks since the one that is there and that I showed in pictures below is the one IM instructed me to create. YOu can tell that because I [as adirected] specified 'SYSTEM' somewhere and that produced a special term/phrase/label somkewhere and that is there in the task I showed you. I didn't put that oneo ther - IMDISK did. And it doesn't work.
If there is no drive letter for a disk, how would I ever discover that it is there. Neitehr my partitioning tool nor my HD test ap sees the RAM Drive - see attachments - no drive I: or 12 GB. I had plannd to run th speed test on this drive to compare w SSD in my computer. OK, I can't do that, but that's no biggie.
It is interesting to see that my Processor Gadget does not detect that IM has ised some RAM - see attached. I have 24GB installed [trying to make things faster - less paging] but Windows refused to use moe than 6, leabing 18 unused. So I chose to RAM DISK 12 of that 18 and the gadget still see 18 unused. I can't see that as a problem.
So, looking 3 ways for drive w no drive letter, I would not see/detect it. Fortunately, that does not seem to have occurred on my computer so I dno't have to worry about it. Make that 4 ways: Computer/Manage does not see the ram drive, too.
And then you say 'use the GUI'. What GUI? In looking at my desktop before responding, I find that installation has stuck a coupla icons there [disk driver & configuration]. I ran configuration - twice - to see if it retained my size paramenter, and it did/does. Kudos for that!! I also rebooted and it was there!!!
So I conclude that that icon/shortcut that runs "C:\Program Files\ImDisk\RamDiskUI.exe" is what you meant and am very pleased to report that it is exactly the 'capture the CMD line procedure in to a desktop icon' that I longed for, except that I only need to run it once, as the installation s/w hinted about something else.
But those details don't matter. What matters is that now I have ram disk at boot and at this point, I'll say it's all your fault since you made me look around and experiment.
When I last had/used IMDISK, decades ago, I found that loading & unloading [which involves either rotating HD or SSD (these days)] took up the time I'd saved by using ram disk so I quit doing it. I'm hoping I can find something useful to do w the previously wasted 12GB of installed RAM. I sometimes do a little video processing and have determined that my system is [8-core] processor-bound, so faster storage [SSD vs HD] does not really help/change anything.
What do 'normal' ram disk users us it for?