Danish Bronco

Hi everyone, It's been a few months since the last version of the ImDisk Toolkit has been released. I wonder when we'll have a new version, and what it'll bring.

Hi everyone, In my last post I alluded to the fact that when you create multiple RAM Disks with ImDisk Toolkit, settings from one RAM Disk tend to be also used for the other. For example, if I set two RAM Disks, both sharing the same size, file system and general settings, and I want one of them to host a Temp folder the old-fashioned way, and the other via a junction to ProgramData, I can't. I can have one or the other, but not both. Am I missing something? Is there a command line argument I can...

Thanks for the tip(s)! Problem is, when you have multiple RAM disks, the GUI tends to snowball the settings of one disk onto the others (file system, size, for example). Using a .bat file solved that for me. I'm gonna try to run my script from inside the GUI, though. I've set up my RAM disk .bat file to start when I open my session, because I've got Throttlestop launching on startup (scheduled task) and it tends to reside in my Temp folder. Maybe I'll try to launch the .bat file on Windows startup...

Hi everyone, I've used ImDisk Toolkit for a good number of years now, and oh boy, the things we take for granted! For example, I've written .bat files to create a RAM Disk on startup and install a pagefile in it. In fact, I've created two of those, and I've written the .bat file by following an example I found on a website somewhere (can't remember where, don't ask!). The thing is, I'm curious. I know what curiosity did to the cat, but I really want to know more about the syntax I use in that .bat...

Hi everyone, I've used ImDisk Toolkit for a good number of years now, and oh boy, the things we take for granted! For example, I've created .bat files to create a RAM Disk on startup and install a pagefile in it. In fact, I've created two of those, and I've written the .bat file by following an example I found on a website somewhere (can't remember where, don't ask!). The thing is, I'm curious. I know what curiosity did to the cat, but I really want to know more about the syntax I use in that .bat...

Also, is it safe to use the letter A, knowing that it used to be allocated to floppy drives? Even Windows 10 still has a little of MS-DOS lurking in the basement... :-)

UPDATE: I tried that, and lo and behold, it doesn't work. If I set one RAM disk with a ProgramData junction and the other with user and system temp folders, the latter's temp folder remains empty as everything is routed through ProgramData. In other words, the settings you use on one of the RAM disk will also be used on the other, regardless of what they are. Is this normal behavior?

Although... On reflection... Hear me out: What if I created 2 RAM disks, one with a junction with ProgramData and one where the user and system Temp folders are? Would they work independantly?