Re: [Mingw-users] msys and \\?\ UNC paths

[Earnie <ea...@us...>]

Arnold Hendriks wrote:
> I'm having trouble starting MSYS sh.exe from a process, and I think I've
> narrowed it down to our use of UNC paths (we use UNC paths to avoid
> dealing with the 255-path length limit on Windows)
>

I doubt that overriding path limits greater than 255 will happen with 
MSYS executables.  So you may not gain much if you have a path greater 
than 255 characters and executing an MSYS executable.

>    I seem unable to start the msys tools using \\?\ UNC paths (on WinXP
> SP3). I have installed the shell into C:\blexdev\msys\bin
>
> Start>  Run>  C:\blexdev\msys\bin\sh.exe works fine, and so does typing
> "start C:\blexdev\msys\bin\sh.exe" in a cmd.exe window.
>
> However, if I try to invoke the shell with
>
> Start>  Run>  \\?\C:\blexdev\msys\bin\sh.exe
> or
> "start \\?\C:\blexdev\msys\bin\sh.exe"
>
> I see a quick screen flashing by, which immediately disappears.
>

I don't know about starting MSYS with UNC paths but once started you can 
use them.

ls -l //?/C:/blexdev/msys/bin

I'm guessing that it may be an issue with the way the DLL needs to find 
itself.  I also get a security warning about an unknown publisher by 
starting it with the UNC path.

-- 
Earnie
-- http://www.for-my-kids.com