http://bugs.winehq.org/show_bug.cgi?id=34095
--- Comment #4 from alexei.svitkine@gmail.com 2013-07-21 10:09:13 CDT --- It looks like dlls/dplayx/dplayx_global.c tries to map some data at 0x50000000 in memory.
My guess is that using the mac driver changes what's loaded in the address space such that by the time that code runs, that memory loc is taken by something else.
I guess the question is whether the data needs to be at 0x50000000 (i.e. is that what happens under Windows and do programs use hardcoded offsets into that data), or can we change that address to pick a location that's free?
If it does need to be at 0x50000000, then during the wine init sequence, it should probably reserve that space early on so that other stuff can't be loaded there and then use the reserved space by the time dxplay needs to be loaded.