sergm wrote:

If building DOSBox on your own, I think it's always best to take advantage of new features available in the most recent SVN version.
As for building munt programs, I have to run several virtual machines with different OSes each with own set of C++ compilers and build tools. I tend to prefer the "most usual" compiler for each platform with basic set of compiler options for better compatibility, so I don't think it'll be interesting for you to do the same. For release builds, you can find the source files zipped in the download section of the project page.
Good luck! 😀

I guess I wasn't specific enough. I assume you use the VMs for Linux and MAC OS so I'm not planning on working on those versions ATM so you can exclude those for now. 😀

I don't need to worry about any VMs since I will be running the OS straight so you can assume I'm using the actual OS to be compiled in.

SergM, can you be more specific of the actual programs you use to code Munt for XP and for the 9X version?

And what programs do you use to compile the source code for XP and for the 9X version to the final windows executable for release for each?

Ah, These two... 😀
Well, I did mention exact versions of the GNU compiler and the Qt library I used to build the Win9x crap. The 32-bit binary for the fully-functional Windows OSes is built using Microsoft C++ compiler version 15.00.30729.01

Hello sergm,

While Munt98 works fine under 98SE,

I've had time to do more legacy testing. I managed to get the older version running on a Z370 Coffee Lake system I have.

It turns out even on the single core it can handle the necessary CPU strains for the Munt emulation.

This opens the door for using a modern machine for Munt processing with the smallest footprint.

I found some other issues in my Munt98 testing. I starting testing all flavors of 9X and ME.

Unfortunately Windows 95 OEM, 95A, 95B, and I think even on 98 First Edition (might have to recheck this one going off memory). These could not run Munt98 without some popup dependency error.

Can you recompile Munt98 v2.3 so that it supported down to the lowest dependency for Windows 95 OEM?
If it works for 95 OEM it should work for every version all the way to Windows ME without issue.

Let me know when you do and I'll do some more testing.

Hello,
I am trying to activate MT-32 emulation on my Thinkpad T42 with Windows 98. The processor is a 1.5ghz Pentium should do it.

I quickly tried last night with The Games: Winter Challenge (1991) which supports MT-32 but it didn't work.

1) Download this mt32emu_qt-1.7.1-win9x.zip
2) Download this mt32emu_win32drv-git_ac4f1f0dee-win9x.zip
3) I add a new multimedia device by selecting this driver mt32emu_win32drv-git_ac4f1f0dee-win9x.zip (OEMSETUP.INF)
4) I go to Control panel \ Multimedia \ MIDI tab and under "single instrument" I select MT-32 instead of the Microsoft one
5) I start the exe file in mt32emu_qt-1.7.1-win9x.zip which opens a console and another program. I keep them open without closing them
6) I start the game and select MT-32 in the settings

But no audio is played

Update:
I also tried with Space Quest 3 but it tells me it can't find the audio device

However, if I open a .mid file via media player MUNT is activated, I hear the audio and see the information on the virtual display.

If I open a DOS game on the console instead I see this:

1Win32MidiDriver: Invalid midiSession ID supplied: "0x29"
2Win32MidiDriver: Invalid midiSession ID supplied: "0x29"
3Win32MidiDriver: Invalid midiSession ID supplied: "0x29"
4Win32MidiDriver: Invalid midiSession ID supplied: "0x29"
5Win32MidiDriver: Invalid midiSession ID supplied: "0x29"
6Win32MidiDriver: Invalid midiSession ID supplied: "0x29"
7Win32MidiDriver: Invalid midiSession ID supplied: "0x29"
8Win32MidiDriver: Invalid midiSession ID supplied: "0x29"
9Win32MidiDriver: Invalid midiSession ID supplied: "0x29"
10WinMMAudioDriver: Processing thread stopped
11

Works with media player:

Hello matti157,

Unfortunately, there is no simple way to make MT-32 emulation work with DOS games in a raw console session of Win9x. As you can find earlier in this forum, merely installing mt32emu_qt and mt32emu_win32drv is not enough to get MT-32 music output from a DOS game, one also needs to route MIDI messages from the DOS application to the Windows MIDI port the driver creates. If you tried to use DOSBox, it'd work out of the box (since DOSBox is in fact a Windows application and able to connect to MIDI ports directly). However, this way may be unacceptable for you due to additional performance overhead, so you can also try VDMSound for Win9x which is supposed to add proper emulation of MPU-401 device and facilitate MIDI routing as appropriate. Sadly, the project was dropped a long time ago, remaining in the alpha stage...