https://bugs.winehq.org/show_bug.cgi?id=34095
--- Comment #14 from Ken Thomases ken@codeweavers.com --- The problem is not really specific to the Mac driver. It does seem that loading the Mac driver makes it much more likely that the particular address range is used for something before dplay tries to use it, there's no guarantee either way.
It's possible that one could use the Mac driver and it would happen to not use that address range.
It's also possible that one could use the X11 driver and it would happen to use that address range, resulting in the same problem. This could happen on Linux as well as OS X.
It's somewhat random. Any given build of Wine or the system libraries and frameworks could change it.
The only real fix would be to change dplay to not require a specific address range.