I'm sorry (for you).

Please stop nitpicking. My comment wasn't about version details but about the fact that the advancements in Munt Reloaded are still completely unknown to the public at large.

2nd AFAIK Munt reloaded IS part of Munt already... http://sourceforge.net/projects/munt/ The regular build which is downloaded hundreds of times per week is still the acient, 7-year-old 0.1.3. It's the same version which is included in ScummVM. Probably 99% of all munt users still use this build ( …

After all the awesome work sergm has done on Munt Reloaded during the past year, I wonder when Munt Reloaded will finally be merged into the Munt main branch? It's unfortunate than only this rather esoteric crowd on Vogons knows about the huge advancement in Munt Reloaded (which has been downloaded …

collector wrote: The installer was not written with the INI in mind, so it expects the ROMs to be in the same directory. But how does to the installer tell the dll to look for the ROMs if not by creating an ini? Does it write to the registry?

Thats really strange. I tried it again and again - no sucess. It works only with the original dll from the installer. Have you changed anything else? OK, finally I solved the problem. The installer (MuntSetup.exe) copied the ROM files to the system32 directory, and set the PathToROMFiles parameter …

Mikity wrote: Yup, works for me - copied the new DLL to the SysWOW64 directory. Thats really strange. I tried it again and again - no sucess. It works only with the original dll from the installer. Have you changed anything else?

Kaminari Redux wrote: C:\Windows\System32 C:\Windows\SysWOW64 I have a copy there too. Where does the exe get the path from? There's no ini file included in the zip archive, just the exe and a readme...

Keep in mind that it installs an older version of the driver, but you can update it simply by overwriting the driver with the latest from Sergm's Git download page . Well I tried exactly that, but whenever I replace the dll, the emulator stops working. Does it work for you with the most recent dll?

If you had read the thread in the MT-32 Development forum you would see what the reason for it is. The inf does not install on 64-bit systems. The driver can be manually installed, but involves steps that some would not be comfortable doing, such as manually registering the DLL and making a …

Hi, since the driver version of the lastes munt build won't work with Windows x64, I tried to run the WinMM command-line application (mt32emu.exe). However, it terminated with "Missing or incorrect MT32_CONTROL.ROM". Of course I have put both ROM files in the exe's directory and they do work with …