[Bug 7065] Get SecuROM copy-protection working

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

--- Comment #38 from Anastasius Focht   2007-10-14 07:20:40 ---
Hello,

thanks for log.

--- quote ---
New log with drive type corrected.
--- quote ---

You only created additional cdrom symlink, right?

--- snip ---
0009:Call KERNEL32.FindFirstFileA(0033b760
"C:\Windows\System32\Drivers\*.sys",0033b620) ret=007f2a60
...
0009:trace:seh:raise_exception code=c0000094 flags=0 addr=0x7f2afa
0009:trace:seh:raise_exception  eax=00003a7c ebx=7ee73888 ecx=00000000
edx=00000000 esi=0000004b edi=00403000
0009:trace:seh:raise_exception  ebp=0033b990 esp=0033b880 cs=0023 ds=002b
es=002b fs=0063 gs=006b flags=00010202
0009:trace:seh:call_stack_handlers calling handler at 0x7790c0 code=c0000094
flags=0
0009:trace:seh:call_stack_handlers handler at 0x7790c0 returned 0
--- snip ---

Division by zero and then crash due to unhandled exception.

Could you try to put in a fake <driver>.sys file into
"C:\Windows\System32\Drivers" ?

Just copy one from windows directory or rename a file.
Maybe they expect at least one entry to be returned from FindFirstFile().

If possible could you try include module load addresses next time when such a
crash happens?
Do it like this: grep the whole log for "Call PE DLL" and redirect output to
extra file.
Now supply the last relevant lines as usual but prepend the lines from extra
file (from "Call PE DLL") to beginning of log.
I just want to see if the crash happens in securom module (SEH address).

Regards