http://bugs.winehq.org/show_bug.cgi?id=16543
--- Comment #23 from Jeff Zaroyko jeffz@jeffz.name 2009-05-07 20:12:10 --- (In reply to comment #22)
Hello,
--- quote --- '"C:\Program Files\PopCap Games\Bookworm Deluxe\Bookworm.exe" '
In other words, there is a rogue space after the command line. --- quote ---
So this trailing whitespace character (0x20) also applies to all other explorer/shell spawned processes. That "lpCmd" parameter passed to CreateProcess(W) must already contain that whitespace to let the command line show up that way in process explorer.
That leaves the question where it gets added. The most likely candidate is ShellExecute(Ex)(W). Maybe someone can extend "shlexec" part of shell32 test suite and verify this behaviour in Windows. Alternatively you could try native shell32 and friends overrides and do relay log.
Regards
Hello
Then this looks like a duplicate of bug 13617. Applying the linked patch[1] and using wine start /Unix Bookworm.exe makes the program work.
the /Unix flag is supposed to implement the quirks observed when starting processes as they would be through explorer.exe on Windows as some programmers rely on the always quoted commandline that explorer adds and now also the trailing whitespace.
1. http://www.winehq.org/pipermail/wine-patches/2008-June/055520.html