• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Windows symbolic link problem.

hexden

n00b
Joined
Nov 18, 2012
Messages
41
I have a PC running Windows 7 Home Premium x64 set up as a media server where I store my DVD rips. I play them with my Patriot Box Office (PBO) media player. I have the movie Alien ripped as files in the directory named Alien which is in turn stored in a directory named SciFi. I also want to have the movie Alien appear in the Horror directory so I created the following symbolic link to do so: mklink /D "F:\Movies\Horror\Alien" "F:\Movies\SciFi\Alien". After creating the link I could see the files in the FMovies\Horror\Alien directory from Windows Explorer with no problem. But my Patriot Box Office saw the directory FMovies\Horror\Alien as empty. I tried using NTFS junction points instead and they worked but neither Flexraid nor SnapRaid, the programs that I want to use to protect my file rips support NTFS junctions. Any ideas as to the problem and how to fix it?
 
Two things to try, I don't use Patriot Box Office so I can't test:
1. Try making a regular directory of F:\movies\horror\aliens, and then make symbolic links to the files themselves. Never know, it might work.
2. Do the same as above, but use hardlinks instead of symbolic links. Hardlinks, in my estimation, should definitely work, the only limitation is that they are tricky to manage. A file is not deleted until *all* hardlinks to it are deleted, it's basically just duplicating the file's info into another directory. Also hardlinks must point to files on the same volume, just so you know. And it could be tricky with backup software, as they may tend to backup the file twice or more (once for each hardlink on the source drive) so you'd probably have to configure an exclusion on one of them.
 
Last edited:
Back
Top