The test results you have selected are very old and may not represent the current state of Wine.
Selected Test Results (selected in 'Test Results' table below)
What works
Installation and first chapter
What does not
Other chapters than first
What was not tested
Gameplay on other chapters
Additional Comments
I tried to import previous savegames from other chapters - some of them works, but game crashes just after playing a bit, some crashes game when loading.
---fixme:ddraw:IDirectDrawImpl_SetCooperativeLevel (0x16c0e8)->((nil),00000008)
fixme:d3d:IWineD3DStateBlockImpl_Release Releasing primary stateblock
fixme:d3d:IWineD3DDeviceImpl_Release (0x16ca60) Device released with resources still bound, acceptable but unexpected
fixme:d3d:dumpResources Leftover resource 0x1e4bc5a8 with type 1,WINED3DRTYPE_SURFACE
fixme:winmm:MMDRV_Exit Closing while ll-driver open
---
2 errors appears after crash, which are not visible (they are smudged), titlebar says:
1. a terminal error has occured
2. microsoft visual c++ library...
The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.
RE: Crash
by Lorenzo on Saturday August 2nd 2008, 11:14
The issue was apparently not solved at all with 1.0, since I just tried and I got the same problem. As far as I remember from digging out the problem at the time, the DIB section failure was caused by some more internal WIN calls that ostensibly exhausted the available memory, thus returning a NULL to the caller or something like that. Of course it can't possibly be a ram related error, since Sanitarium was conceived to work on much older machines. I also remember other 2D games were affected by the same issue: I read this was to be added to the 1.0 milestones, which I now guess wasn't.
Are the two opened bugs really to remain there forever? I'm sure they're not impossible to solve. If there's anything I can do to help just let me know: I'm just not familiar with the Wine development and debugging tools, so I'll need some guidance on that.
