Build 744: Sets wrong current directory for executed files
Posted: 19.04.2017, 09:12
A new bug that was introduced in FreeCommander since build 742 x64 (on Win7 SP1 x64):
When starting any executable from inside FreeCommander the executable should be normally provided with the current directory, from where the executable was actually called. In build 744 (or maybe already 743) FreeCommander sets the "current path" for calling the executable always to the folder where FreeCommander.exe is located, not the executable being called.
Repro:
Create a batch file test.bat to display the current directory:
Now place it in C:\Temp and navigate with FreeCommander to C:\Temp.
Open test.bat either by double click or Enter key from FreeCommander.
When doing this from build 742 you will get:
Whereas calling test.bat from 744 will produce:
This applies to all kinds of executables and yields different errors, especially when the executables (called with wrong "current directory") try to access files located in "current directory" instead of the directory where the executables are actually located.
When starting any executable from inside FreeCommander the executable should be normally provided with the current directory, from where the executable was actually called. In build 744 (or maybe already 743) FreeCommander sets the "current path" for calling the executable always to the folder where FreeCommander.exe is located, not the executable being called.
Repro:
Create a batch file test.bat to display the current directory:
Code: Select all
@echo off
echo %cd%
pause
Open test.bat either by double click or Enter key from FreeCommander.
When doing this from build 742 you will get:
Code: Select all
C:\Temp
Code: Select all
C:\Program Files\FreeCommander XE