https://bugs.winehq.org/show_bug.cgi?id=47967
--- Comment #13 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- Hello,
(In reply to russ.herman from comment #11)
@ Olivier F. R. Dierick
Unsatisfactory response. May be documented as requirement, but worked unti 3.18. Much breakage has resulted.
I'm simply saying that the issue doesn't prevent the applications from running at all (they run fine when started as described in the manual). That's why the bug severity should not be 'major' or 'critical'.
I make no statement about the undocumented behavior that worked for you until 4.18. I'm following the manual since years and change the directory before starting applications in all my wrapper scripts. In this case, following the manual did prevent 'much breakage' for me.
(In reply to Artem S. Tashkinov from comment #12)
I'm deeply sorry, guys, but Windows DLLs loader (ntdll?) works even when an app is run from the _wrong_ working path.
If we're talking about Windows conformance, Wine 4.18 has stopped being conformant. Please revert the old behavior.
--- quote from the linked forum topic --- (...) Windows uses different conventions: - the loader starts by setting the current working directory to the directory that contains the program and starts it running. (...) --- end quote ---
The difference in behavior is well known and that's why there is a specific entry in the wine user's guide explaining how to achieve that with Wine.
--- quote from wine user's guide --- You need to use wine start if you specify a full path to the .exe, because that allows Wine to set the working directory for the program if it needs it. --- end quote ---
You get Windows loader conformance by using "wine start C:\fullpath\to.exe" instead of simply "wine C:\fullpath\to.exe".
Regards.