First post, by Retroview
After nearly three weeks of trial and error I finally nailed a issue down I have not found a solution yet anywhere else on the Net. Because I have often used the net and also this forum in the past to find advice I will now take the time to share this information so someone else can maybe find it with google and safes himself the trouble and the money 😀
Ok lets start
I wanted to play Wing Commander again and this time on real Hardware of that time. I used a 486DX33 without Turbo and my MT32 with SOFTMPU. I encountered a strange lockup of the MT32 at random points in every mission(mostly when it was really stressfull with multiple enemies and much much shooting and sounds). The only thing you could do then was to turn the unit off and on again (of course you need to restart WC then too or all sounds wrong)
I first though OK might be some hanging notes buffer overflow bug and used all Softmpu gave me to use but nothing helped.
I then blamed Softmpu for the error and bought a Roland SCC1 and a HardMPU on Ebay. The SCC1 arrived first and I was confident that the issue would be gone and tried it again but BAAAM Crash MT32 . I was like WTF.
I now blamed the Bus Speed of my 486 ISA Port and I used a other 486 Board I still had in storage that had a bios where you can set clock2/X ... Of course that board had a Dallas chip on it so I got myself the right desolder equipment to desolder the Chip and put a socket with a new one on it (The Board survived and I really could now set the clock speed manually to clock2/4 and even down to clock2/6!!! Well you can guess ... Still CRASH MT 32...
Now I blamed the 486 Processor and got myself a 386DX33 from Ebay again and( because I had now read from a lockup bug on Mt32 with OLD Firmware) I also ordered a new Blue Ridge Firmware, too. Lucky for me that I thought, oh well its only 15Euros I will also order a NORMAL 1.07 firmware, too JUST IN CASE ...
Well the 386 and the ROMs arrived today and I first tried the 386DX33 but the Roland Crash was of course still there. I then opened my MT32 and saw that there were already custom ROMs on it with the number 1.08. I did not get what that means and put my new BR 1.07 on the unit ... Well and I was really like WTF WTF when it crashed again! .........
I gave up and wanted to wait till my new MT32 would arrive from Japan ( I had ordered one with a 90000 number, mine is a 83000 one).
and THEN it hit me ... What if the guy who wrote 1.08 on the ROMS inside my MT32 actually meant 1.07 BR ???!!! If so I would have switced a Blue Ridge ROM for a Blue Ridge ROM today !!
I really did not think it would work, I was under the impression BR would be flawless for sure, but I then switched the ROM again and this time I used the NORMAL NON BLUE RIDGE 1.07 and now its FINALLY fixed and no more crashes even after 1 hour running a mission that always crashed again and again and again 😀
Well long text short meaning: Dont use BR1.07 when you want to play Wing Commander 1 or 2 with your MT32 😀
Just to add for clarity I have not encountered any other errors with that MT32 BR1.07 in any other game before not even in games that use the same Origin Sound System like Ultima 6 or World of Ultime Savage Empire. It was really only in WC1 and WC2 and there also ONLY inside missions when the unit was stressed with lots of sounds
RetroCave PlayStation. 286-12 / 386DX33 / 486DX33 / 486DX2-66 / PI-90 / PI-233 / PII-400 / PIII-650 / PIII-700 / PIII-1000 / P4 2,8 / P4 3,06 / P4 3,8 / C2DUO 2,66