That's funny. Congrats, have fun with sq3!

what's your cpu cycle rate in dosbox? if it's too high the SysEx messages are sent too fast causing buffer overflow. I set mine to 3,000 cycles per second, maybe that'll change anything? oh and btw, are you positive your sound is perfect, only muffled? i.e., compare it to www.queststudios.com sq3's …

I guess these cheap sound cards are mainly for casual users, the midi interface is there for a joystick mainly, being that most games don't even use midi anymore, let alone external midi devices like the mt-32.

mr_btw, my SB live! driver is from microsoft, not the creative labs one. And because of that, in my control panel->sound and media->audio->midi, I'm setting the midi to: "SB live UART chip". my hunch is, try to get the microsoft driver, that's the only thing that's different between our setups. good …

Thanks people. it's working beautifully. Had to change my sound card to SbLive!5.1 though, seems like my old ensoniq es1370 pci128 has a very lousy mpu401 interface and it distorts the SysEx messages sent to the mt-32 causing everything to sound funky. I wonder why do these companies say a certain …

collector wrote: You have to select MT-32 for your audio with the INSTALL.EXE. no kidding. No, the problem was that, ensoniq pci 128 has a cheap imitation of a mpu-401 interface. I used a sblive! 5.1 card instead and my mt-32 plays just like the old days. thanks though.

I have the actual mt-32 module, and I hook it up to my soundblaster 128 pci. my system: Pentium 1ghz, 512mb ram, soundblaster 128 pci, running windows xp sp2 My problem is that the old dos games sound terrible on my mt-32. The SysEx data seems to be going fine: for instance in space quest 3 it says …

Heya people, I have an MT-32 (external module, the black thing) and I hook it up to my soundblaster midi jack. None of my old sierra/lucasarts game are able to contact the MT-32. any ideas how do I do this? thanks in advance.