On 11/10/2014 10:57 AM, Andrey Repin wrote: > Greetings, Nellis, Kenneth! >>> (CMD.EXE doesn't like UNC paths.) I hadn't realized that I could >> pipe a script into bash. >> reg ADD "HKEY_CURRENT_USER\Software\Microsoft\Command Processor" /f /v "DisableUNCCheck" /t REG_DWORD /d 1 >> And speaking of "doesn't like", it only don't like it's own CWD to be UNC path. > You can still start programs by full UNC path from CMD. > Though, with correct settings (see above), the point is moot. >>> -- > WBR, > Andrey Repin (anrdaemon@yandex.ru) 10.11.2014, <21:56> >> Sorry for my terrible english... >> I always thought it odd that MS invents UNC's then fails to support them properly in their own tools. Try pushd on a UNC path... -- Andrew DeFaria http://defaria.com -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple