[Bug 39878] Diablo II does not start on 64bit system with more than 2GB VRAM cards

wine-bugs at winehq.org wine-bugs at winehq.org
Mon Jan 4 07:09:29 CST 2016


https://bugs.winehq.org/show_bug.cgi?id=39878

Józef Kucia <joseph.kucia at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |patch

--- Comment #16 from Józef Kucia <joseph.kucia at gmail.com> ---
(In reply to Wylda from comment #11)
> I still got the same message box pop-up saying "UNHANDLED EXCEPTION:
> ACCESS_VIOLATION (c0000005)". The same message box pops up on Wine-1.9.0. So
> compatibility has been reached ;-))

>From the logs you provided one can see that IDirectDraw2_GetAvailableVidMem()
returns 0xc0000000 on your "Win8.1 64bit 16GB RAM, GTX970 4GB VRAM ver361.43"
for DDSCAPS_TEXTURE | DDSCAPS_VIDEOMEMORY | DDSCAPS_LOCALVIDMEM. So it seems
that this is the same crash as on Wine.

> The only way to run it on Win8.1 is through second workaround, i.e. run in
> windowed mode: "C:\DiabloII\Diablo II.exe" -w  (not tested on Wine).

This workaround works on Wine as well.

The amount of video memory returned by GetAvailableVidMem() could be
potentially limited to INT_MAX. However, this is not how native ddraw works so
I doubt such change would be accepted in Wine.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.


More information about the wine-bugs mailing list