ConEmu build: 171109 x64
OS version: Windows 10 LTSB v.1607 x64
Far Manager: version 3.0 (build 5095) x64 (latest nightly as of 2017-11-15)
When I execute a *.BAT file from FAR when active panel is a network path:
\\Server\Shared\Music > play_audio.bat song.mp3
...then *.BAT executed well but I get this annoying error message:
'\\Server\Shared\Music'
CMD.EXE was started with the above path as the current directory.
UNC paths are not supported. Defaulting to Windows directory.
To dismiss this message I already set HKEY_CURRENT_USER\Software\Microsoft\Command Processor\DisableUNCCheck=1 (see attachment "CMD.EXE's UNC Check - disable.reg")
This registry setting works in plain FAR, but it not works when FAR started from ConEmu :(
That's the problem =)
The text was updated successfully, but these errors were encountered:
CMD.EXE's UNC Check .reg files.zip
ConEmu build: 171109 x64
OS version: Windows 10 LTSB v.1607 x64
Far Manager: version 3.0 (build 5095) x64 (latest nightly as of 2017-11-15)
When I execute a *.BAT file from FAR when active panel is a network path:
\\Server\Shared\Music > play_audio.bat song.mp3
...then *.BAT executed well but I get this annoying error message:
To dismiss this message I already set HKEY_CURRENT_USER\Software\Microsoft\Command Processor\DisableUNCCheck=1 (see attachment "CMD.EXE's UNC Check - disable.reg")
This registry setting works in plain FAR, but it not works when FAR started from ConEmu :(
That's the problem =)
The text was updated successfully, but these errors were encountered: