How to Automate Mounting and Saving Image File of a RAM Disk?

[David (PassMark)]

We are also releasing V3.3 today with significant speed improvements to the physical drive emulation option.
Logical emulation will still be faster for most people however.

[PRHL]

OSFmount still holds the crown in speed. A small update with newer versions:
CrystalDiskMark 9.0.2
SSD KINGSTON SKC3000D2048G PCIe 4.0 x4 - NTFS
RAMdrive AIM Toolkit 20260420 - exfat
RAMdrive OSFMount v3.2.1000 - exfat
Batch file:
OSFMount.com -a -t vm -m v: -o format:exfat:"RAM_osf" -s 12G

[Simon (PassMark)]

Looks like the sample command in that post was missing a argument in the format option, it should be this instead:

osfmount.com -a -t vm -m #: -o format:NTFS:"RAM Volume" -s 1G

Original post with the examples has also been updated.

[PRHL]

I just made a copy/paste of
osfmount.com -a -t vm -m #: -o format:"RAM Volume" -s 1G

Nothing happens - besides that the syntax is shown. Here is a screenshot of cmd-admin:
I tried a few changes, e.g. "- s:" and "-s 12G", but no success either. The RAM disk that was used for CrystalDiskMark was created using the app osfmount.exe.

There are a bunch of command line arguments you can use with OSFMount to mount an image from the command line.
They are all documented in the Help file (Which you can get to from the "Help" menu).

Some examples,

Mounting a empty RAM disk and format osfmount.com -a -t vm -m #: -o format:"RAM Volume" -s 1G

Mounting an image file as a virtual drive osfmount.com -a -t file -f C:\passmark\images\vmdk_split.001 -m #:

[Simon (PassMark)]

Now the bad news: osf has no autostart option - neither for the RAM disk itself nor for the temp variables. And that led me to this thread.
Interestingly, the command line arguments did not work. It only showed the help instructions how to use the command line arguments. I tried the arguments mentioned here (copy + paste) and also some variations.
It made no difference whether a batch file was used or Win+R or cmd or PowerShell (admin or not). A pity.

Windows already has built-in options that allow OSFMount to be started automatically. Placing a batch script in the startup folder (C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup) and setting up a task in Task Scheduler worked ok.

What command line arguments were you trying to use? If its showing help instructions, it might mean that the arguments may be incorrect.

[PRHL]

I use the RAM disk of ImDisk Toolkit for some years now. That program has integrated options for both a) autostart and b) temp variables. So my system always starts with the temp folder on the RAM disk. Yesterday, I read an article about a new version of OSFmount and wanted to give it a try.

The good news is: OSFmount is faster than ImDisk. The following grapics show CrystalDiskMark 8.0.4 with the SSD (C), ImDisk (R) and OSFmount (S):

SSD


ImDisk


OSFMount

Actually, I started the three tests with osf and made a fourth test again with osf - with the same reslts. Yes, osf is really faster.

Now the bad news: osf has no autostart option - neither for the RAM disk itself nor for the temp variables. And that led me to this thread.
Interestingly, the command line arguments did not work. It only showed the help instructions how to use the command line arguments. I tried the arguments mentioned here (copy + paste) and also some variations.
It made no difference whether a batch file was used or Win+R or cmd or PowerShell (admin or not). A pity.

[ibay770]

True, I'll have to retry it, sorry for the inconsistancy/

[David (PassMark)]

Thanks for the post ibay770, but there are a bunch of problems with your test method.

1. You switched between different versions of Crystal Disk Mark. Some tests were with V8 and some with V7
2. You picked a different number of test threads. Sometime 5 threads and sometimes 1 thread.
3. You picked different file sizes for the test (8GB, 2GB, 1GB, etc..).
4. The size of the RAM drives you created are different for each product tested.
5. You used different file systems when formatting the RAM drives.
6. There was no information on the test hardware you were using. Was it even the same hardware for each test?

So all this kind of ruins the comparisons. It isn't apples to apples.

[ibay770]

I think all the available options are in the help file.

We did some benchmarks back in 2019 with Arsenal image mounter (as I don't think there is another other solution that supports the same range of disk image formats).
Example below.




We also did a benchmark comparison with Softperfect as they were the other fastest solution at the time.




We haven't redone them in 2020.
But it is pretty trivial to run a comparison. So we would encourage people to do their own. Results will probably vary depending on your hardware.

I can verify that. I tried it with a bunch of ramdisks,and it was neck in neck with Asus ROG Ramdisk,, but OSFMount offers a few more options. I posted my results here, although I tried it on different amounts of memory, so the results may seem skewed.

I've been trying to create a ramdisk with the commands above, but it isn't working for me, what command do I run to create a 15GB ramdrive,formatted as FAT32, with a logical partition, with the letter A? Thanks in advance,and thanks again for making this awesome software.

[janszpilewski]

This is a problem because when you put a bach script into startup directory then the Windows 10 will display a popup and ask for administrator promt every time I start my computer.
It would be better to make the app automount/autostart like it is done in ImDisk .

Use Windows Task Scheduler to create a task with a trigger at boot or logon and action like:
"osfmount.com -a -t file -f C:\passmark\images\vmdk_split.001 -m #"
It should ask for the password only when you create the task.

However, an option to save the ramdisk to a file from command line seems to be missing.

[hhprfmxdeifhtxywva_avxrja]

1) Yes. There are lot of ways to auto-run programs at boot time in Windows.

One way is,
1. Press windows key + r
2. Copy the run command Shell:startup
3. It will reach C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup
4. Create the shortcut of the program you want to run in startup. (this might be a batch file for example that runs OSFMount)
5. Drag and drop shortcut into the folder.
6. Restart the computer.

2) No, at least nothing built into OSFMount

This is a problem because when you put a bach script into startup directory then the Windows 10 will display a popup and ask for administrator promt every time I start my computer.
It would be better to make the app automount/autostart like it is done in ImDisk .

[David (PassMark)]

I think all the available options are in the help file.

We did some benchmarks back in 2019 with Arsenal image mounter (as I don't think there is another other solution that supports the same range of disk image formats).
Example below.




We also did a benchmark comparison with Softperfect as they were the other fastest solution at the time.




We haven't redone them in 2020.
But it is pretty trivial to run a comparison. So we would encourage people to do their own. Results will probably vary depending on your hardware.

[reimburseplating]

Hi, David,

I looked at the Help file that you referred to. Are there perhaps some additional CLI arguments besides the ones listed in the Help file?

For example, I notice that there are no CLI arguments to save the contents of the RAM drive to the image file. That would be really helpful.

Also, I think there was a claim somewhere that OSFMount is the fastest RAM disk program. Is there a source for this claim?

Thank you.

There are a bunch of command line arguments you can use with OSFMount to mount an image from the command line.
They are all documented in the Help file (Which you can get to from the "Help" menu).

Some examples,

Mounting a empty RAM disk and format osfmount.com -a -t vm -m #: -o format:NTFS:"RAM Volume" -s 1G

Mounting an image file as a virtual drive osfmount.com -a -t file -f C:\passmark\images\vmdk_split.001 -m #:

[DanD]

Thank you David (PassMark), very useful information!

[David (PassMark)]

Using the virtual memory "-t vm" option on the command line creates a RAM drive. So the content of the drive is stored in virtual memory. If you have enough free physical RAM, this will be a very fast drive. If you don't have enough free physical RAM, performance will drop off a cliff as the operating system will start swapping to disk. Adding the -f option, pre-loads a disk image into the RAM drive. Once this happens there is no mirroring or backups back into the on disk .img file. So changes to the RAM drive are lost (unless you manually save it). Manually saving a RAM drive back to disk will be slow, as typically disks are pretty slow.

Using the -t file option means all reads and writes go back into the .img file (the new volume is backed by a file and not by virtual memory). So this is not a RAM drive. But some caching in RAM can still happen. It will generally be a lot slower than a RAM drive. But contents are not lost on demounting.

There is also a 3rd option which is "-t file+wc". With this option the virtual disk is backed by the '-f' image file and an existing write cache file (.osfdelta). This means the orginal disk image is never modified and all changes get added to a separate delta file. LIMITATIONS: The disk must be mounted using physical emulation option.