So, I would like to create a RAMdisk with ImDisk TK. I've been looking at the the TK's RAMdisk creation GUI, but am not sure about some of the options. I'll go straight to the questions:
1. Is the "Launch at Windows startup" option equivalent to using the -P parameter in the command line options? I ask because I plan to *INSTALL* some apps into the RAMdisk, and I need them to be available at every boot, exactly as I left them.
2. When I try to use the "-a" or "imdisk -a" parameter in the command line options, I get an "Error: the volume cannot be mounted" error. This happens even if no other parameters are used.
3. When using the "-t type" parameter, for using a file backingstore for the RAMdisk, what is the correct syntax? Am I supposed to specify it simply as "-t <location of backingstore file here> (i.e. "-t C:\RAMDisk.img") Or just as "-t type"? Or "-t type <location of backingstore file here>"? I need the contents of an *.img to be stored on the root of a fast SSD volume (for immediate availability at startup), but have the contents loaded into RAM during startup. So I'm looking for a true RAMdisk that is filebacked for persistence, rather than a *.img that is simply mounted but not loaded into RAM. I have tried using a RAMDisk before with software such as Opera, but they didn't seem any faster, I guess they were just loaded from a mounted *.img rather than being located in RAM. Not sure.
4. Is the "vm" parameter specified in conjunction with -f the equivalent to using the "Load content from image file or folder" in the Data tab of the RAMDisk creation GUI (and therefore not necessary)?
5. Is the "-P" parameter effective when used alone, or does it need to be explicitly specified along with -a?
6. I would also like to create a RAMDisk for temp directories, both for C:\Windows\Temp, as well as the temp directories for each of my user accounts. Should I also change the user/system environment variables myself (instead of trusting the GUI to do it and possibly screwing it up)? I think I should create the directories myself beforehand, save them into a *.img, then let the TK load that *.img. Should I also create NTFS junction points redirecting the user/system temp folders into the appropriate RAMDisk locations? Or is this not advised? I know that the RAMDisk is available while the system is running, and there should be no issues if the temp directories are seamlessly redirected. But my concern is that, somehow, if Windows or the user accounts tries to access the temp folders during startup or shutdown, then they may not be available if the ImDisk driver hasn't loaded yet. At what point in the bootup process does the driver load? Very early, or only after other critical system services are started first? And the shutdown process, it would seem that Windows is in a mad rush to kill all services ASAP, including ImDisk's services. How does the TK handle this during shutdown? I'm also worried that something like Windows Update may try to make use of the temp folders during startup or shutdown, and they may not be available if the ImDisk service(s) are not running, thus causing updates to fail.
7. Is hibernation compatible with the RAMDisk created by the TK? I'm aware that the TK syncs all data in the RAMDisk to the backing file during shutdown/reboot. But if I hibernate, will this cause issues? I currently have hibernate/hybrid sleep disabled, and if the RAMDisk will have issues with it then I will leave it as such. So for me, a shutdown is a true poweroff event, and a reboot is a "regular" reboot, with nothing saved to C:\hiberfil.sys either way. I don't really feel that hibernation is necessary on an SSD, but if I need to use it for say, emergency shutdown while doing something important (i.e. updates, working on my online schooling/Internet marketing projects, etc) then I won't hesitate to enable and use it in a one-off scenario.
8. Are the -hd, -fix, and -rw parameters the TK's defaults when creating a RAMDisk, or should I explicitly specify them. In the case of -hd, I'm not sure if it's necessary to create a dedicated partition within a *.img (to be loaded into RAM).