http://bugs.winehq.org/show_bug.cgi?id=22146
--- Comment #7 from Jörg Höhle hoehle@users.sourceforge.net 2010-03-29 03:41:22 --- Eric wrote:
check if the content of the MCI table in winmm.dll has been changed on 64bit platforms
I'd be very pleased if somebody would supply that data. Because a new MCI_INTEGER64 type would make the parser more regular and simplify my patch.
Wylda wrote:
If you would melt that into wine test exe
Go to WTB job 1156 before it gets deleted, you can download both patch and exe. https://winetestbot.geldorp.nl/JobDetails.pl?Key=1156
actually my experience is a bit different.
Your results are crazy indeed. Perhaps MS auto-detects a 32bit driver and sends plain old DWORD-sized objects instead?!? That also hints in the direction of additional MCI_INTEGER64 types. Austin English machine's shows exactly the crash that one expects from a 32/64bit pointer mismatch: http://test.winehq.org/data/f7cc8f695b954bf98bd34bb7adccc09378349a1a/wine_ae...