Unfortunately the post with me Mars and another user (turned out to be the user hard drive crashing)...
Is lost on the forum
Here is proof that hfs can and or was able to handle shared network path.
http://rejetto.com/forum/index.php?topic=10803.msg1056943#msg1056943On NAS/PC with a shared folder, you will require a shared folder with full control over files to a single user.
On server PC that permission folder will be mapped as a network shared drive
https://support.microsoft.com/en-us/help/4026635/windows-map-a-network-driveOn the servers, on hfs and drag the drive letter to the house/root of the hfs window. And add it as a real folder.
_------
https://www.computerhope.com/jargon/h/hiddshar.htmMore info on hidden share/admin/ read-only shares. And windows share has another secret share of the path that also ends o. A $ ....
These share are usually system related and don't/are not usueable for true network sharing.
O don't recommend using a hidden share to map, if you want then 'c' drive shared then you will have to go to the PC and share that drive.
On regards to 3 com and other wol tools.
https://sourceforge.net/projects/wake-on-lan/3 com was an example, as they are a nice / network hardware manufacturer and often have third party tools such as pxe boot
....
Sorry, usually. Use a PC, but with current work, the phone is what I have, and auto correct and predicted text mess with the typing sometomes.
Again, your server PC must have a network shared folder to a disk drive.
Then you add that drive like any other folder to hfs