Cutemouse 2.0 solves an issue where the mouse works but the game freezes if you move the mouse while playing soundblaster audio, it may not help in your situation

I think your issue may be related to the MPU401 port, the game offers port 330, 332, 334 and 336 (using r/r1, r2, r3 and r4 respectively) but most sound cards will only offer 300/310/320/330 as MIDI ports. So if unisound has initialised the MPU401 port to anything other than 330, roland will not work with this game.

Or maybe it was hard to understand, if you launch with "atlantis.exe m r" then the mouse and roland is working?

Sorry but I don't even think it's related to UNISOUND...
You MUST declare

indiana.exe m (mouse) s220/5/8 (addr/int/k bufsize)

and you can concatenate arguments like:

indiana.exe m s220/5/8 r

as I read on the help_me.doc of Indiana Jones:

The product will support a combination of Roland and SoundBlaster
capabilities. Simply select both options.

Thankyou all !!!

Where is the best place to report bugs?

I am using the latest v0.82a with my ESS MK1869 XTREME. According to the readme:

... the remaining resources will be disabled (... MPU address ...

When configuring my Ultrasound after setting up a Sound Blaster 16 PnP with its MPU port on 340, the Sound Blaster port stops working (even after reinitializing it with Unisound). It seems like the Ultrasound is configuring it's MPU port at address 340 and overriding the Sound Blaster.

It works fine on other ports, but I would prefer to use 340 on this particular device.

Kahenraz wrote on 2026-09-13, 08:17:

Where is the best place to report bugs? […]
Show full quote

Where is the best place to report bugs?

I am using the latest v0.82a with my ESS MK1869 XTREME. According to the readme:

... the remaining resources will be disabled (... MPU address ...

When configuring my Ultrasound after setting up a Sound Blaster 16 PnP with its MPU port on 340, the Sound Blaster port stops working (even after reinitializing it with Unisound). It seems like the Ultrasound is configuring it's MPU port at address 340 and overriding the Sound Blaster.

It works fine on other ports, but I would prefer to use 340 on this particular device.

GUS utilizes ports in 3x0 range (where x is the same as 2x0 in the base port) for MIDI and DRAM related functions. If you use 240 for GUS then it will conflict with your SB16 PnP on 340.

If you want SB16 PnP's MPU port on 340 you'll need to move the GUS base port to something like 260. GUS will then use ports in 360 range for those purposes.

That's it, thank you. Moving my Ultrasound to 260 was the solution.

Also, setting up resources for the ES1869 requires allocating two DMA channels, I assume for full-duplex playback and recording. But my MK1869 doesn't even have a microphone jack. Is there a way to configure the device in half-duplex mode so that I only need to assign one DMA channel? DMA channels are a limited and precious resource.

Kahenraz wrote on 2026-09-14, 05:49:

Also, setting up resources for the ES1869 requires allocating two DMA channels, I assume for full-duplex playback and recording. But my MK1869 doesn't even have a microphone jack. Is there a way to configure the device in half-duplex mode so that I only need to assign one DMA channel? DMA channels are a limited and precious resource.

From the example in the UNISOUND manual (using an ES1868 card), it seems you can just put "D1 H1" in the BLASTER environment variable so UNISOUND would set both DMA channels to 1.

This can also be used for SB16 cards to use low DMA channel for 16-bit audio if needed.

Yes, I thought so too. And this works for my SB16. But when I try to do the same with the ES1869, for example, "D1 H1”, Unisound sets it to DMA:1/0.