http://bugs.winehq.org/show_bug.cgi?id=21061
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |focht@gmx.net
--- Comment #1 from Anastasius Focht focht@gmx.net 2009-12-20 07:19:05 --- Hello,
the first crash in "saskutil.sys" helper kernel driver is something Wine can't fix in near future. The driver assumes there is a valid service descriptor table (SDT) that points to a valid system service dispatch table (SSDT). The mapped ntdll is used to get SSDT service number index of hooked Zw functions by searching entry of the function in ntdll export table. One could setup a "fake" SSDT that is seen by driver only (by design) - just to keep it happy but more serious action might not work out.
If the crash annoys you, remove the service key in registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\SASKUTIL
Service start type = disable/manual won't work as the app wants to start it.
---
The second (application) crash is due to Wine OLE compound storage insufficiency (processing of "SASREPAIRS.STG"). AFAIK this part of ole32 is currently heavily worked on so your chances might not be bad at all to get a fix in a decent timeframe. Work around by using native ole32.dll and set override "native-then-builtin".
There exist some tools for OLE compound files that might help to track Wine insufficiencies/bugs down. Example: http://www.coco.co.uk/developers/CFX.html (CFX - The Compound File Explorer). You might find it useful for exploring/manipulating the contents of OLE compound files and for verifying if Wine's implementation actually works ;-)
Regards