http://bugs.winehq.org/show_bug.cgi?id=16543
--- Comment #15 from Anastasius Focht <focht at gmx.net> 2009-04-13 13:19:57 ---
Hello,
why did you add obfuscation keyword here? There is nothing related here.
Just to catch attention is bad manners ...
There are working and broken versions of the game - they have even the same
version 1.13 but are built at different dates.
You can compare both 1.13 install directories for differences (Bookworm.exe).
working ->
http://downloads.popcap.com/www/popcap_downloads/BookwormSetup-en.exe
Build Date: April 24, 2008
broken -> http://downloads.popcap.com/www/popcap_downloads/BookwormSetup.exe
Build Date: September 25, 2008
Whoever wrote the broken versions was most likely on drugs.
When the wrapper "bookworm.exe" is started, it parses the initial command line
and prepares the process create parameters for the child.
When started with *full* path *and* a whitespace (or alternatively "" as param)
the parent (wrapper) will not pass any parameters to child (popcapgame1.exe) ->
child will succeed.
In all other cases the father will copy its own complete command line and pass
it to child leading to this error (because the child does not expect any
non-empty params)
This should also fail with Windows.
You might test it by opening a console window, cd to program directory and
manually call the wrapper with:
1. short path ("bookworm.exe")
2. long path (quotes)
3. long path (quotes) + additional whitespace or "" as single parameter
Only 3. should succeed.
For Wine you might use empty quote param because trailing whitespace will get
stripped, e.g.:
--- snip ---
$ wine "C:\Program Files\PopCap Games\Bookworm Deluxe\Bookworm.exe" ""
--- snip ---
Anyway .. there is nothing to fix for Wine here. It's just horribly broken
software.
Regards
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.