On Thu, Jan 15, 2015, Greg Jung wrote:
> Thanks all, let me summarize the situation:
>
>cygwin has its own trick to make a symlnk where the native OS doesn't
> cooperate, which is a simple file beginning with the char[11]='!'
> then 0xFF,0xFE, then wide-char name of where the link points.
> In
Thanks all, let me summarize the situation:
cygwin has its own trick to make a symlnk where the native OS doesn't
cooperate, which is a simple file beginning with the char[11]='!'
then 0xFF,0xFE, then wide-char name of where the link points.
In windows a symlink creator needs elevated privilege
On 15. 1. 2015 4:11, Greg Jung wrote:
> Yes I've seen that, if my second post appeared, the symlinks created with
> cygwin are the ones giving me trouble. These links are invisible to CMD.exe,
> by someone's
> design:
>
> CYGWIN- created links in
> Directory of e:\cygwin64\lib\nox
>
> 03/31/
