Problem summary Nuke scripts give an error when following symlinks/junctions from mapped drives in Windows
Customer reported version nuke.12.1v1
Customer reported platform windows10
Steps to reproduce
1) On machine A, create a folder and share it to the network, by right clicking>properties>sharing>Share... then follow the wizard
2) On machine A, create a subfolder in that folder called Test1
3) On machine A, create a symlink/junction to that folder, using mklink /j Test2 Test1 in cmd
4) On machine B, navigate to the shared folder and map it to a drive letter 5) On machine B, Open Nuke, make a checkerboard, and save the script to the mapped drive in the Test1 folder
6) On Machine B, close the script, then try to open it via the Test2 symlink/junction, it should error:
Expected behaviour For the script on the symlinked/junctioned folder to open
Actual behaviour When opening a script through a symlinked/junctioned folder Nuke cannot read the file
Workaround 1) Open File Explorer (Windows Key+E)
2) Right-click on "This PC" and click "Map network drive..."
3) Select a drive letter and enter the path to your junction directory (So that the drive letter opens directly into the directory)
4) Open Nuke
5) Try opening the file through the drive letter instead of the junction
Reproduced by Support in: Nuke 13.2v2 - Windows 10 Nuke 13.1v1 - Windows 10 Nuke 12.1v1 - Windows 10 Nuke 12.0v1 - Windows 10 Nuke 11.0v1 - Windows 10 Nuke 10.0v1 - Windows 10 Nuke 9.0v1 - Windows 10 Nuke 8.0v1 - Windows 10
