UNC Paths are an issue about rcwm HOT 5 CLOSED

I was able to reproduce, this should be fixed when the scripts move to powershell. Since batch script can't "cd" into the UNC path, it can't get the name of the source folder - it mistakenly takes the destination folder's name instead.

from rcwm.

Hey, thanks for opening this issue and your feedback!

If I understand correctly, my script copies the folder to your local C:\Windows instead of the actual UNC path?
I'll have to test it, it could be the backslashes that are causing the problem. Are you using single or multiple mode? Which windows (or powershell) version? Which RCWM version?

I'm in the process of moving everything to powershell and using registry for storing filepaths, so single mode and multiple mode will both use the same script. Should be a bit easier to debug and maintain.

from rcwm.

Correct, C:\Windows[folder].
The above script I shared with you appears to effectively run it the same way and it works when I run it. PS would be a nice move as well. Thanks for looking into it.

from rcwm.

This should be resolved for copying/moving and removing directories in v2.0.0 (making links will still fail). Try it out:
https://github.com/GChuf/RCWM/releases/tag/v2.0.0

from rcwm.

from rcwm.