From: Arnold H. <a.h...@b-...> - 2010-05-31 14:25:56
|
On 31-5-2010 15:48, Greg Chicares wrote: >> 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. >> >> > I ran this in a CMD prompt: > > C:\temp>\\?\C:\msys\1.0\bin\sh.exe > The system cannot find the path specified. > > Same symptoms for solitaire: > > C:\temp>\\?\C:\WINDOWS\SYSTEM32\SOL.EXE > Try C:\temp>start \\?\C:\WINDOWS\SYSTEM32\SOL.EXE Or use "Run" in the Windows start menu. > A little googling suggests it might have something to do with: > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Command Processor\DisableUNCCheck > My problem isn't with cmd.exe. Apparently cmd.exe is a bit buggy when it comes to converting its parameters to CreateProcess or whatever it uses, but that shouldn't affect Run in the Windows start menu, or the START command itself. Both seem to run other applications fine when invoked using a UNC path, but sh.exe doesn't (and rxvt.exe doesn't, and I presume a lot of the rest of msys, but most of those other commands don't wait for input, so they're hard to test with) |