One question. Will Munt work in Win98, Win98SE or WinME? I know canadacow's MT-32 driver would not and I haven't gotten Munt to work either.

Munt uses a WDM driver so it should, in theory, work in 98SE and Me.

When I go to install it, it says the MT32_CONTROL.ROM cannot be found. It is there in the directory. I built mine using Alkarion's method. Am I using the correct file? Perhaps the size is wrong?

The one I just built (which works fine with ScummVM 0.7.0) is exactly 65,536 bytes. If you're suspicious your file might be different, attach it and I'll do a FC.

uhm do a md5sum or so.
please don't attach it.

Mine is also that size and seems to work just fine in scummvm. Scummvm's readme seems to expect a 32K file. Here is the md5 checksum: 9513FEC4F09A7D327748340CE3A2A59B

This is indeed the correct checksum. Did you manually point the hardware installation to the location of your MT32_CONTROL.ROM? I had to do it when I installed Munt myself, even if the correct file was placed in the same directory as the .inf file.

OK, I tried the emulator and noticed the following:

+With DosBOX the emulator seems to handle the games with "Exc. buffer overflow" problems (Utopia and Race Drivin') like a charm, something my MT-32 can't do even with a retro computer and Roland MPU-IPC-T.
+While it uses considerable amount of CPU resources it's still possible to run great amount of games with Barton@2.45GHz with only modest reduction of DosBOX cycles.
-Volume balance between different instruments (even unmodified) needs tweaking.
-Some instruments don't sound like they should. Bad reverb, wrong pitch etc.

At least I could recognize what device this emulator tries to emulate and it looks very promising. Keep up the good work! 😀

Did you manually point the hardware installation to the location of your MT32_CONTROL.ROM? I had to do it when I installed Munt myself, even if the correct file was placed in the same directory as the .inf file.

Indeed I did, Windows installer will recognize that a file called MT32_CONTROL.ROM is there but the stupid install prompt won't take it. Then if I press "skip file", the MIDI for MT-32 Synth Emulator will appear in my Multimedia Devices tab, but it will say it is enabled but inactive due to some unknown problem. It won't appear under the midi tab in the midi output box. Is there anyway to force Windows into making it work?

How exactly did you follow Alkarion's instructions? When I first read them, I ended up merging the two files together end-to-end instead of bytewise interleaving them (so of course it wouldn't work). Both of those ways of doing it would probably result in the same checksum, as would interleaving the files in the wrong order.

After installing with the "skip file" method, have you then tried putting copies of MT32_CONTROL.ROM (and MT32_PCM.ROM) in your c:\windows\system32 folder manually and rebooting? It *might* work. If not, then try installing over the top of it *again* (using the skip file method if necessary) and hopefully it will find the files already in windows\system32. Just a shot in the dark.

I don't remember if I had the problem you're describing (WinXP SP2), but I know I got it working eventually.

Another way to verify that your file is correct is to test it with SCUMMVM like oneirotekt did, since it has the Munt code built into it.

I've been playing around with the ALSA driver, which I pulled out of CVS. I'm noticing, that as with Tristan/Canadacow's version, there's no way to control the samplerate at which this thing plays.

Kingguppy, have you thought of making that an option? It's almost useable on my PIII/600 as it is, but if I could downsample the emulator from 44100hz, to 32000hz, I would expect that this would work pretty snappily.

How exactly did you follow Alkarion's instructions? When I first read them, I ended up merging the two files together end-to-end instead of bytewise interleaving them (so of course it wouldn't work). Both of those ways of doing it would probably result in the same checksum, as would interleaving the files in the wrong order.

I followed them exactly. WinHex says that it will interleave the two files byte by byte. I understand that the file must be created in this way.

After installing with the "skip file" method, have you then tried putting copies of MT32_CONTROL.ROM (and MT32_PCM.ROM) in your c:\windows\system32 folder manually and rebooting? It *might* work. If not, then try installing over the top of it *again* (using the skip file method if necessary) and hopefully it will find the files already in windows\system32. Just a shot in the dark.

I have done the first thing you suggest, and the driver shows no signs of working. Note that the files go into the Windows\System subdirectory, not the Windows\System32 subdirectory.

Another way to verify that your file is correct is to test it with SCUMMVM like oneirotekt did, since it has the Munt code built into it.

I have done this using my MT32_CONTROL.ROM file and it does work. Maybe the .inf file has an error in it.

I have done the first thing you suggest, and the driver shows no signs of working. Note that the files go into the Windows\System subdirectory, not the Windows\System32 subdirectory.

Strange, they definitely are in \windows\system32 on my system. Maybe that's where the bug is - you're using Win98 right? Maybe the INF file assumes you're using Win2K/XP and tries to put it in \windows\system32 directory, when it needs to go in \windows\system on Win9x.

I have done this using my MT32_CONTROL.ROM file and it does work. Maybe the .inf file has an error in it.

Good to know that your file is good at least. My hunch is definitely to agree with your idea that there's a bug in the install routines that prevent it from working correctly on Win9x.

Whilst Windows 98 does indeed accept WDM drivers, no-one suggested it would work or indeed would be painless 😀 Note that the 'shared system' directory on any 9x OS is always 'System'. System32 was introduced in WinNT and its move to 32bit code (system remained for legacy support of 16bit code).

Using my Virtual PC system running Win98 I didn't have any success with the MT32 driver. I did get it to install without error but after reboot the MT32 device didn't load "due to an unknown problem".

The inf file is very basic and, as far as I recall, doesn't include any 32bit OS specific settings.

Consider ditching your ancient OS for something a bit more recent!

The original MT-32 driver did not support pre-XP (maybe 2000) systems, so I wouldn't be surprised if this current one does not either.