https://bugs.winehq.org/show_bug.cgi?id=34730
winetest@luukku.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |winetest@luukku.com
--- Comment #31 from winetest@luukku.com --- (In reply to Alexandre Julliard from comment #26)
You have to use cmd (or some other Windows application) to launch Unix binaries, yes. That's what the FAQ is about.
The wine loader only supports loading Windows binaries, and there doesn't seem to be any need to change that. If you are running Unix binaries from Unix, there's no reason to go through the wine loader at all.
(In reply to Rosanne DiMesio from comment #30)
(In reply to Emmanuel Charpentier from comment #27)
So the FAQ § 7.4 should be rewritten to explain the exact procedure to use. The example given does *NOT* work currently.
If the documentation issue is the only reason this bug is still being kept open, that's been fixed. The relevant section of the FAQ is now 5.8, and it was rewritten some time ago to explicitly state the need to add a dot character to the end of the list of extensions in HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Environment\PATHEXT (per comment 21).
I don't see that this is going to be changed. Suggesting closing this bug.