Yes, its quite common to run multiple soundcards in your DOS machine, especially with Gravis cards as their sound blaster emulation isn't great.
I used to run a SB16 and a GUS Classic in mine. It's just a matter of giving them seperate IO address ranges, IRQ and DMA channels. Then configuring your games to use the appropriate card.
I did find the GUS was much louder than the SB16 was so you may want to invest in an external mixer.

Actually I think there are more GUS cards in systems together with SB than without. 😉

The GUS PnP is a resource hog, but fortunately all the unnecessary/redundant stuff can be deactivated and the two IRQs/DMAs can be shared, so you may get away with only one I/O range, one IRQ and one DMA for the GUS.

In case you are not familiar with the GUS PnP yet, I recommend installing the GUS alone first, trying to avoid the resources you need for the SB16 clone.

Well I've used the PnP more then this clone. And yeah, emulation is horrid D:
I'll give it a shot.

Battled it out recently to get a GUS PnP work next to an AWE64. I know that the GUS is loved my many, but seriously that card is a pain to get going sometimes. I could only manage it with help from others and doing it through the "backdoor way" by editing ini files and whatnot and configured it so I just ran a GUS.BAT when I need the GUS support.

We warned 😁

I'm on the lookout for a GUS ACE now. It should be much easier to work side by side with a Sound Blaster.

From my experience, the installer is just good to depack the files ones and to give a template for a config.
Everything else is always ini file editing and writing some batch with the appropriate calls.
Never expect that an installer finishes with the correct configuration and everything is set. Usually an installer is a quick and dirty bug ridden program that was hacked together in the last moment before release to get a default configuration that was tested by the developers by ini file editing and batch writing written to disk. So every installer assumes that the card is the only one in the system, it will usually f... up your config.sys and/or autoexec.bat and you will have to edit them anyway to get the changes to the correct locations. So the best way to install a sound card is to do it without running the installer.

I love my PnP 🤣, but it's SB emulation is...hilariously bad.

Put the new box back together, with the Gravis installed properly. About to install the SB-Clone

Been a long time since this thread 😜
But as the situation sits now...I'm using a Gravis Classic, and a real SB16 (no PnP).

I've been able to get them to co-exist fairly well for the most part...but there seem to be some minor conflicts that the PC is complaining about.

I do know if I run the GUS setup, it'll run through testing the ports/addresses fine...but when it starts to test SB/MT-32 emulation....it "fails".
Naturally...I don't want emulation (I have the real things). Would the tool EEPROM work on a Gravis Classic? It worked wonders on my GUS PnP.

Also...Ultramid doesn't seem to work...at all. Can't load it o.o'

My Yamaha SW20-PC and GUS ACE combo worked well in DOS. The only trouble I had with it was in Linux, long time ago. And it was just a small and hilarious problem which did not affected functionality.
Yamaha has an AD1848 codec, same was used on GUS MAX, and the Linux kernel believed I had an OPL4 card and a GUS MAX, instead of OPTI 928+AD1848+OPL4 and GUS ACE.

Started over, just installing the Gravis. All works well without conflicts, but I have one issue. When I try opening Ultramid...

"configuration file not in $(ULTRADIR)/midi directory"

Did you insert SET ULTRADIR=..... in autoexec.bat?

The Ultradir line is in place, set to C:\Ultrasnd, which is where the files are.[/list]

So Ultramid.ini and ultrasnd.ini is present there?
And the path in those files is also correct?

You may try Megaem as it also implements the ultramid functionality required for AIL games.

Found the problem. The driver files weren't copied over to the C:\ properly.
Opps! Dont forget to use XCOPY /S kids -.-