why this thread is not sticky?

Not enough honey?

Carrera wrote on 2025-05-15, 07:21:

Not enough honey?

Not enough glue.

JazeFox wrote on 2025-05-11, 16:31:

Hi! Thank you all for your words :) […]
Show full quote

Hi! Thank you all for your words 😀

moturimi1 wrote on 2025-05-06, 08:44:

I would like to know if you plan on improving the detection of the Kurzweil Pinnacle soundcard.

I guess you have a rev.F card (you didn't specify system/card details).
In the next version your card will be detected and initialized. Anyway, I'm afraid that the volume will remain the same. Unisound does not mess with the DSP firmware binaries and code required to manipulate the routing and mixer capabilities.

Thank you for the update. It will always be good to have more exotic soundcards being supported by this great tool.
As there are issues with the Kurzweil Turtle Beach Pinnacle I had to find a compromise by using a EWS64 with Kurzweil Turtle Beach HOMAC daugtherboard. I would have loved to use the Pinnacle directly under DOS, but there seem to be weird mixer settings. Without initializing Windows this can not be solved as there is not DOS mixer tool to my knowledge.

I am currently planning on putting 6 soundcards in one computer.
Currently I have a config running with 5 soundcards:
- Soundscape Elite (W534, I10, D0, P320),
- AWE32 CT3670 (A220, I5, D1, H5 , P0, F0, MPU turned of),
- PAS16 (I3, F388, D0 --> for OPL3)
- PicoGus (A240, I7, D3, P330) with attached WavetablePi
- EWS64XL with internal Wavetable (P310) and attached Kurzweil Turtle Beach HOMAC (P340).
Without UniSound it would not have been possible. When I only set the MidiPorts of the EWS64XL, I would not get any sound under DOS for MIDI at 310 and 340. It is the issue with the muted CS4236 output I guess. Without turning on the Crystal and WSS/DMA/IRQ, CS32MIX.exe would not find any hardware to unmute. Anyhow with installed WSS Crystal all DMAs are occupied. DMA 0, 1, 3. Setting the DMA of the EWS64 to any of these setting mutes the digital sound of the other card sharing that same DMA port.
The current solution is to set the EWS64 with Unisound in a last step to the DMA port that I do not need for the game that I want to play in the next step. So e.g. AWE32 or GUS for digital sound, then I set the DMA of EWS64 to DMA 0. If I want to use AWE32 and Soundcape or PAS16 then I set the EWS64 to DMA 3. This is unfortunately a compromise, but it works.

Therefore thank you so much for this great tool! I am a soundcard freak and without this tool it would not be possible to use the cards together in one computer.

IGNORE ALL OF THIS. IT WAS AN ISSUE WITH MY BATCH FILE.

1set BLASTER=A220 I5 D1 H5 P330

megatog615 wrote on Yesterday, 15:37:

IGNORE ALL OF THIS. IT WAS AN ISSUE WITH MY BATCH FILE.

It's still worth mentioning, for the sake of anyone who may think that they have a similar problem in the future, that this was not at all a problem with UNISOUND. In one case, your BLASTER environment variable was present, and in the other case, it was not. Paying attention to the output of UNISOUND, you will see that it will either say that it has found a BLASTER environment variable and is retrieving the configuration, or it will say that it is loading the default configuration. If you see the loading default configuration line, it is not processing your BLASTER environment at all, and it is up to you to figure out the source of the mistake or incompatibility on your system.

While talking about batch files and environment variables anyway, it's worth mentioning that any environment variables you set in dosstart.bat (for Win9x "restart in MS-DOS mode," a logical place to put unisound), won't stick.