[Bug 34558] Alawar launcher fails to start after game has been registered

[wine-bugs at winehq.org]

http://bugs.winehq.org/show_bug.cgi?id=34558

--- Comment #6 from Anastasius Focht <focht at gmx.net> ---
Hello,

--- quote ---
There's a change in application behavior when it is run in a way you requested:
message box with Error 198 is not shown, application just silently (without any
gui messages) exits after couple of seconds.
--- quote ---

that's because of a software protection scheme which doesn't like relay thunks.
I scanned a few executables in install folder:

--- snip ---
-=[ ProtectionID v0.6.4.0 JULY]=-
(c) 2003-2010 CDKiLLER & TippeX
Build 07/08/10-17:57:05
Ready...

Scanning -> Z:\home\focht\.wine\drive_c\Program
Files\Alawar\non-cyrillic-installfolder\MidnightMysteries4.exe
File Type : 32-Bit Exe (Subsystem : Win GUI / 2), Size : 2009024 (01EA7C0h)
Byte(s)
-> File Appears to be Digitally Signed @ Offset 01E8E00h, size : 019C0h / 06592
byte(s)
[File Heuristics] -> Flag : 00000000000001001100000100100110 (0x0004C126)
[!] ASProtect v1.40 Build 11.20 detected !
- Scan Took : 0.557 Second(s)

Scanning -> Z:\home\focht\.wine\drive_c\Program
Files\Alawar\non-cyrillic-installfolder\MidnightMysteries4.wrp.exe
File Type : 32-Bit Exe (Subsystem : Win GUI / 2), Size : 9349632 (08EAA00h)
Byte(s)
[File Heuristics] -> Flag : 00000000000001001100000000000000 (0x0004C000)
[!] Possible CD/DVD-Key or Serial Check -> Unregistered
[CompilerDetect] -> Visual C++ 10.0 (Visual Studio 2010)
[!] File appears to have no protection or is using an unknown protection
- Scan Took : 0.389 Second(s)
--- snip ---

>From your log it seems the app already gathered a certain amount of data to
generate unique license information (NIC mac address, hdd serial which is just
"0" because it's the default for each WINEPREFIX).

Can you generate a log file again without relay but more debugging channels
(use the same recipe as in my previous comment, just different WINEDEBUG
channels):

WINEDEBUG=+tid,+seh,+loaddll,+process,+virtual,+ole,+variant,+msgbox ...

Additionally there should be an application log file named "local.log" in the
same folder.
Check if there is any suspicious error messages and attach the parts that might
be relevant.
To have a fresh log created remove it before the run.

Regards

-- 
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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.winehq.org/pipermail/wine-bugs/attachments/20131211/e0924700/attachment.html>