Target Location is not Valid on NAS Drives

[Etz]

OK basically I`m Latest Ketarin build and using naming scheme:

{path}\{category}\{appname} v.{version}.{url:ext}

 

"path" is global variable and Now comes the problem:

 

If I define it: W:\Repository , it works,

but if I define it as full network path:

\\192.168.1.2\install\Repository\ , it doesnt...

(It works it windows explorer though, so it must be somekind of issu related to Ketarin )

 

If I use root folder on that share in global variable, for example: \\192.168.1.2\install

It also works...

 

Digging in the logs show interesting thing, ketarin puts "pipe" symbol, after share name, so it searches for location:

\\192.168.1.2\install|\Repository\ , which ofcourse doesnt exist...hence here comes the error.

 

Why I dont want to define it as mapped drive with letter?

Because I have mutliple computers at home, and sometimes mapped drive letters differ after clean install...

 

Maybe someone can explain this behaviour for me, is it a Bug of Ketarin, or a bug of my understanding?

[floele]

Couldn't reproduce this behaviour in any way. You should, however, try not to have double \\ in your path. If pth the {path} as well as the string itself contains a "\" it will lead to an unnecessary character.