[Bug 4672] Diablo 2, v1.11 corrupts MBR

Wine Bugs wine-bugs at winehq.org
Thu May 31 11:04:46 CDT 2007


http://bugs.winehq.org/show_bug.cgi?id=4672





------- Additional Comments From Speeddymon at gmail.com  2007-31-05 11:04 -------
Does anyone have verifiable proof that it doesn't zero the first four bytes of
the MBR on windows?

I get the feeling that maybe the game is detecting invalid safedisc (or is it
securom?) stuff and that is what is trashing it..  Maybe someone could play
around with windows in a virtual machine and see about breaking whichever copy
protection is used by Diablo 2 so that it asks for the CD, even when the CD is
inserted.  Then reboot the VM and see if it still boots..

I doubt seriously that wine is the cause, as we have cases where the game asks
for the CD and does not trash the MBR without the nocd patch, and the fact that
the mbr does not get trashed when the nocd patch is applied.....

Just because wine is being used and wine is opening the MBR and writing to it,
that means that diablo 2 has to be asking for wine to do that..  Now granted,
there may be problems with wine's SD/SecuROM and that may be causing it, but it
is still a game bug, because games should never cause an os (even an application
compatibility layer) to zero the first 4 bytes of the MBR.....

I'll leave this one open, since everyone else thinks it's a wine bug, but I'm
going to stick to my guns on this one..  If it is a bug in the game, then wine
needs to workaround it, because users should be allowed to be in the disk group
imho.

-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.



More information about the wine-bugs mailing list