http://bugs.winehq.org/show_bug.cgi?id=5272
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |focht@gmx.net
--- Comment #5 from Anastasius Focht focht@gmx.net 2007-11-22 12:13:12 --- Hello,
--- quote --- I don't see anything referring to .net when trying to start the demo. However it ends immediately like: err:seh:raise_exception Exception frame is not in stack limits => unable to dispatch exception.
That's all :( --- quote ---
Yes, the game has nothing to do with .NET technology. Maybe the initial reporter wanted to express "network based application" and didn't know that the term ".net application" has a complete different meaning? Summary should be changed to disambiguate.
Anyway that game uses a custom PE protector, the retail version additionally includes SecuRom 5.x Although the section names indicate "xprot" -> x-treme protector it doesn't seem to resemble the "real" Xprot. Thats a common technique to look like other copy protection by using same section names and entry signatures. Probably to scare crackers away ;-)
From looking frankly at the trace, the protector seems to mess up the exception
registration head (teb->NtTib.ExceptionList, fs:[0]) while executing code in its virtual machine. It points to nowhere, hence the "err:seh:raise_exception Exception frame is not in stack limits" error.
From reading some game forums, it seems the protection caused many issues on
windows itself, early versions seemed pretty unstable (a mess). The demos are a bit old and are not updated anymore, maybe the retail stuff runs better with newer patches.
Regards