The volume is recreated each time, therefore sharing informations are lost. There are 2 solutions:
- Create an image file of the volume (right click on the drive letter in Explorer) and load it with the Data tab of the Ramdisk Configuration Tool. This can be slow if your volume is big.
- Make the share at startup through command line with something like: net share R=R:
Use "net share /?" for more informations. Once your command is ready, you can create a scheduled task with it. If you configure it to run at system boot, the ramdisk may be not ready yet, so you may have to delay the task a bit.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It's odd, because (AMD) Radeon ramdisk does keep sharing information at reboot. Isn't it recreated at reboot as well?
But fortunately there is a third way to go around this problem. It's mounting this ramdrive to an empty subfolder to an other drive that is shared well. While assigning it a new drive letter does not work, mounting to a subfolder works as expected.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This seems to work excellent except one issue: Made ramdisk can be shared, but it will not be shared again after a reboot.
Some registry problem? Service load order problem?
The volume is recreated each time, therefore sharing informations are lost. There are 2 solutions:
- Create an image file of the volume (right click on the drive letter in Explorer) and load it with the Data tab of the Ramdisk Configuration Tool. This can be slow if your volume is big.
- Make the share at startup through command line with something like:
net share R=R:
Use "net share /?" for more informations. Once your command is ready, you can create a scheduled task with it. If you configure it to run at system boot, the ramdisk may be not ready yet, so you may have to delay the task a bit.
It's odd, because (AMD) Radeon ramdisk does keep sharing information at reboot. Isn't it recreated at reboot as well?
But fortunately there is a third way to go around this problem. It's mounting this ramdrive to an empty subfolder to an other drive that is shared well. While assigning it a new drive letter does not work, mounting to a subfolder works as expected.