Thank you for the feedback - the two things you noticed are connected, so let me explain how it works and what we'd suggest.
Why the chosen source folder itself doesn't appear on the RAM FS drive
When you create a volume with a source folder, e.g. C:\Test, that folder itself
becomes the volume. Your C:\Test is set aside and is replaced with a link pointing at the RAM FS drive. So C:\Test\report.doc and R:\report.doc are the same file, and every application that used the old path keeps working unchanged. There's no R:\Test because the root of the drive already is the Test folder. This is intentional rather than an oversight.
Saving only part of a drive
Persistence in RAM FS is a property of the volume, not of individual folders: a volume is either saved or it isn't. That's the current design, and it's what keeps the behaviour predictable - you never have to remember which folder on a drive is the one that survives a reboot.
If you need both, simply use two volumes, for example:
- R: folder-backed on C:\Test, saved as usual.
- S: an ordinary volatile RAM FS volume for scratch files.
Both can be set to mount automatically at boot, so it's a one-off setup, and you get a clean separation: everything on R: is kept, everything on S: is temporary, with no ambiguity about which is which.