debugging longman dictionary

[Rizsanyi Zsolt]

Hi!

I'm trying to debug what goes wrong with the Longman Dictionary of 
Contemporary English.

I have succeeded installing it under wine on a fake windows installation. (I 
had some problems, and posted them on wine-user, but I have succeded)

Now I get an unhandled exception (page fault on read access). But I cant find 
the cause of the problem.
Maybe somebody could hint me how to proceed.

I'm attaching the output of 
wine --debugmsg +relay LDOCE32.EXE

Also I have set up a breakpoint, and stepped through the last 10 instructions 
before the page fault, but I dont understand what that code is trying to do 
(it is somewhat strange).

Also it may be usefull if you could put in a faq or some other documentation 
that the next output (which is very frequent), is just a check running 
debugger. This check is usually done in sharewares to check whether the 
program is debugged.
This is the characteristic output:
fixme:win32:DEVICE_Open Unknown/unsupported VxD SICE. Try --winver nt40 or 
win31 !
fixme:win32:DEVICE_Open Unknown/unsupported VxD SIWVID. Try --winver nt40 or 
win31 !
fixme:win32:DEVICE_Open Unknown/unsupported VxD NTICE. Try --winver nt40 or 
win31 !

At first I tried to define these VxD-s, but when I did so the program 
instracted me to stop the debugger and restart.

Thanks for your attention, and I hope you can help me :)

Zsolt Rizsanyi

[Laurent Pinchart]

> I'm trying to debug what goes wrong with the Longman Dictionary of
> Contemporary English.

[...]
> fixme:win32:DEVICE_Open Unknown/unsupported VxD SICE. Try --winver nt40 or
> win31 !
> fixme:win32:DEVICE_Open Unknown/unsupported VxD SIWVID. Try --winver nt40
> or win31 !
> fixme:win32:DEVICE_Open Unknown/unsupported VxD NTICE. Try --winver nt40 or
> win31 !

Seems like a copy protection to me. Windows programs usually use non portable 
ways to detect if a debugger is running, ... usually by trying to read or 
write from/to kernel space or from/to the interrupt vector, which results in 
a crash when running the program in wine.

The easiest way to solve the problem would be to crack your program (and 
after that people still don't believe that a crack can be used in a legal way 
? :-)

If you can't, then you'll have to figure out what the copy protection tries 
to do, and then implement an exception handler to support it in wine.

Laurent Pinchart