SymLinks aren't supported within the source folder hierarchy

[CodeRedPaul]

I thought this solved all my problems and fulfilled all my requirements.... I was so close.

I have a symlinked folder as part of the startup folder hierarchy, but when in the RAMDISK the folder has been changed to a physical one.

I basically wanted a RAMDISK that was completely volatile, but would pass through data to a physical disk for one folder only.

I guess it's harder to find a solution than I thought. Thanks for this project anyway.

[tmcdos]

I suspect the problem is in my code - it does not check whether subfolders in the startup folder are actually symlinks and simply traverses all the way down. I will take a look and handle such an edge case.
Thank you for using my tool and for taking the effort to report this problem. Stay tuned.

[CodeRedPaul]

I suspect the problem is in my code - it does not check whether subfolders in the startup folder are actually symlinks and simply traverses all the way down. I will take a look and handle such an edge case. Thank you for using my tool and for taking the effort to report this problem. Stay tuned.

What I love about the tool is that it's so easy to change the RAMDISK as requirements and needs evolve. Easy to simply add a new file or folder rather than having to create a new template disk, and again, if you need to change the size of the RAMDISK you don't need to create a new disk image (like in a number of other products I've evaluated - one of which, even though my template was only 2MB, required a whole 1GB image file on disk in order to back the 1GB RAMDISK 🤦).

Thanks for being so responsive. I implemented a workaround by making a change to my workflow, but it would be good to have the flexibility again in the future.

[tmcdos]

Sure, I will definitely try to fix this issue.
By the way, a few other users complained about the lack of image support - they expected RAM usage to dynamically decrease when they delete files from the RAM-disk which (with the current version of the Arsenal driver) is only supported with sparse disk images (through the TRIM logical interface).

[tmcdos]

So, I made an experiment and it turns out the code does support junction points - https://github.com/tmcdos/ramdisk/blob/master/RamSync.pas#L57
If your folder is a junction point then this tool will not convert it (dereference) into its target while initializing the RAM-disk.

[CodeRedPaul]

Arh! Ok!

Mine was an actual symlink as opposed to a junction. I've just tested with a junction instead and it's working no problems! Fantastic!

Thanks for clearing that up. 😍