Run the aweutil program like this : aweutil /em:mt32 . Then run the game by typing monkey r .

Also, early floppy releases of MI1 need to be patched to support MT-32 music. The patch is still available from the LucasArts website:
http://www.lucasarts.com/support/update/monkey-1.html

Yup that's right. Monkey Island doesn't support the AWE32 or General MIDI directly, so in that sense the video is a little misleading. It supports MT-32 and it uses the default MT-32 Instruments, so any device that be put into "MT-32 mode" will sound well with this game.

Thanks! Will try it tonight. One question only,
>Run the aweutil program like this : aweutil /em:mt32 . Then run the game by typing monkey r .
Do it in Real-DOS Mode or at Command Prompt in Win95?

Just try it. Music became different from adlib driver, but not as AWE32 should. Sound more poor and like it sounds wrong. I make a record a little later.
PS. I try it at Command Promt in Win95 and set up MT32 emulation in AWE32 setup utility, cause in Real-DOS mode when i running aweutil /em:mt32 program game hangs up the computer. Don't know why is this happen. MFBEN jumper on my AWE32 is set up in ON mode, so it should be work

Currently I can't test but in the past, when I tried to run my AWE64GOLD with the /em:mt32 command I usually got an error. I never looked into it further as I have a MT-32. This was under real DOS.

I believe I was missing some files. Is this possible?

Yeap, you need to have a specific file on a specific directory inside the SB directory. I had played MI on a soundblaster 32 (non-AWE) a couple of years ago, and I remember trying to enable the mt-32 emulation. I think those 3 files needed for GM,GS and mt-32 emulation were missing from the standard dos installation, and I had been searching on the net for them. But the directory IIRC was SFBANK, and the file was named synthmt.sbk. I think you need to have at least 512kb of ram installed on the card.

I had 2MB in my old SB32 PnP and never succeeded to run any game after loading this TSR in GM, GS or MT32 mode under pure DOS.

Reminds that I have to test this and do a recording for mr3dx 😀

Played with this this afternoon and did a quick recording!

http://www.youtube.com/watch?v=t0OIW0YpS1c

Doesn't sound that bad to be honest, though not close enough to the real thing to really recommend using it IMO.

Anyone know where to find that patch now? Lucasarts link is dead.

Televicious wrote:

Anyone know where to find that patch now? Lucasarts link is dead.

Would rather you didn't bump threads that haven't seen a reply in seven years.

Anyhow, try this:
https://archive.org/details/ftp.lucasarts.com-20130427

File browse:
https://ia801703.us.archive.org/view_archive. … om-20130427.tar

Ergo:
MONKEYUP.EXE (Roland Patch) - https://archive.org/download/ftp.lucasarts.co … %2FMonkeyup.exe
MONKEY.EXE (486 Patch) - https://archive.org/download/ftp.lucasarts.co … pc%2FMonkey.exe

But good news, now that thanks to entering the original patch URL into the Wayback Machine to get the filenames, we now know... that Disney has a partial backup of LucasArts:
https://appsupport.disney.com/hc/en-us/articl … ucasfilm-games-

So...
MONKEYUP.EXE (Roland Patch) - http://static.dolimg.com/mh_netstorage/lucasf … pc/Monkeyup.exe
MONKEY.EXE (486 Patch) - http://static.dolimg.com/mh_netstorage/lucasf … s/pc/Monkey.exe

You my hero.

Stiletto wrote on 2019-09-16, 06:00:

Would rather you didn't bump threads that haven't seen a reply in seven years.

I am potentially violating the admin's advise. I get torn between bumping something that already exists, vs duplicating a conversation to another thread. Please advise me if I am bumping too many old threads inappropriately, or how to best decide based on your preferences. I tend to do this often when I dive into DOS fun.

So I am trying to get mine working with "aweutil.exe /em:mt32" for my AWE64gold. If I do nothing with aweutil, besides the standard /s upon boot from autoexec.bat, then "monkey.exe r" plays in VGA with no music. If I run "aweutil.exe /em:mt32", then I get this message on my screen.

Here is a series of screenshots, after boot, initializing the mt32 emulation (with a AWE64, not MUNT), and starting the game.

Fresh boot (not yet sure about the situation with the insufficient environment space message above.)

Initializing the soundfont appears to be ok.

Using "monkey r"

Beautiful blue error of somekind. I struggled to find much about what it means.

Stiletto wrote on 2019-09-16, 06:00:

Anyhow, try this:
MONKEYUP.EXE (Roland Patch) - https://archive.org/download/ftp.lucasarts.co … %2FMonkeyup.exe
MONKEY.EXE (486 Patch) - https://archive.org/download/ftp.lucasarts.co … pc%2FMonkey.exe

My game is the floppy version with interpreter 5.0.19, no modifications. Am I interested in any of these patches mentioned. I tried the Roland Patch (monkeyup.exe) and it produces a DISK09.LEC. But I don't know what to do with it. I placed it in the game directory, but it didn't seem to have any effect.

Thank you for the great info above.

I disabled the L1 cache (L2 cache still enabled) of my PIII, and the game works with MT32 emulation on the AWE64. I do not really know what this did, but I did quite a bit of trial and error, and this seems to be a singular change that makes this work, in my system. I don't know enough to really explain why. Yes it's an old game, but the game doesn't seem to have any issue running, when using FM synth and all PIII features enabled.

So I really an wondering what disabling PIII L1 cache is supposed to do, to assist my sound card's MT32 emulation.

bytesaber wrote on 2024-05-05, 07:11:

So I really an wondering what disabling PIII L1 cache is supposed to do, to assist my sound card's MT32 emulation.

That's indeed surprising behaviour. I don't see a way L1 cache (even if you might have DMA coherency issues, which by itself is extremely uncommon except in mis-jumpered 486 systems) should change the theory of operation of AWEUTIL / NMI feedback, so the side effect of disabling the L1 cache, that is slowing down the system, is likely the root cause of the fix. Pleas make sure the ISA bus is not overclocked. You should not have an overclocked ISA bus unless you changed fancy settings in the "Advanced Chipset Setup" of your BIOS setup, though. You can also try adding wait-states or delays between ISA I/O cycles by increasing "I/O recovery time" in the BIOS setup, if your system provides an option like that.

Hi mkarcher. This is me attempting to consolidate my posts. The thread below may match what I am experiencing.
Aweutil /EM option - speed sensitive