Executables are run from FC directory instead of current
Posted: 03.12.2007, 16:26
Hi !
When running a batch file by double- clicking in FreeCommander I would expect that it runs in the current directory, like in cmd or explorer. FC runs it from its own FC installation directory, which leads to "file not found" errors in my start.bat on my USB pen drive (which contains relative paths, for obvious reasons).
Could not test if the behaviour is the same for .exe files, but I suppose it is. This could lead to problems when running .exe / .bat files directly in FC, which is very common in a pen drive scenario ...
This is easy to work around, of course (start a DOS prompt) and low priority, but think it's a bug, anyway.
Best regards, A.
When running a batch file by double- clicking in FreeCommander I would expect that it runs in the current directory, like in cmd or explorer. FC runs it from its own FC installation directory, which leads to "file not found" errors in my start.bat on my USB pen drive (which contains relative paths, for obvious reasons).
Could not test if the behaviour is the same for .exe files, but I suppose it is. This could lead to problems when running .exe / .bat files directly in FC, which is very common in a pen drive scenario ...
This is easy to work around, of course (start a DOS prompt) and low priority, but think it's a bug, anyway.
Best regards, A.