🤣

You have to have a UNISOUND on your computer. Copy it somewhere in your PATH or run it from correct directory where it's located.

scroeffie wrote on 2024-10-13, 18:45:

doesnt work what am i doing wrong ?

Are you using DOS for the first time? Obviously there's no UNISOUND.COM file in the root directory of your C drive, nor in the directories specified by PATH.

iam not using dos for the first time i figured it out i had to add a line to my autoexec did not make sense first i thought it was like a option i could change in the command line of dos or some program i had to run first
but iam happy with my result

https://youtu.be/gIHNPo2usww i set the audio to 85

any chance to add OPTi 82C930 card (with wavetable onboard ) to work with this amazing tool ?

boggit wrote on 2024-03-03, 19:20:

Thank you! I'm sure I will! […]
Show full quote

640K!enough wrote on 2024-03-02, 22:39:

Welcome to the forum! Hopefully you'll find that it's a useful, welcoming place, as many of us do.

Thank you! I'm sure I will!

640K!enough wrote on 2024-03-02, 22:39:

Then, from the command line, use only UNISOUND /CL. The purpose of that is simply to list the ISA Plug and Play cards that it finds. We first want to know if it is able to identify your Crystal-based card at all. If that works (please post a screenshot of what you see), then we will be able to work on figuring out the rest of the options that you need.

Doing that also makes my computer freeze, to a point where even ctrl-alt-del won't restart it, at this point:

stanwebber wrote on 2024-03-03, 13:46:

the aopen iplaw35 is the exact card i'm running right now in my kt133a system. it works flawlessly with unisound simply using: s […]
Show full quote

the aopen iplaw35 is the exact card i'm running right now in my kt133a system. it works flawlessly with unisound simply using:
set blaster=a220 i5 d1 t4
unisound.com

maybe try removing the rem from in front of your set blaster line?

Hi and thank you for replying! As I said, I've tried both with the set blaster line and without it (ie by adding REM first), without difference.

The mere act of starting unisound, with or without parameters, is enough to freeze my computer to a point where I have to power cycle.

I got my 286 up and running again and made a new attempt at getting the sound card to work with Unisound. Strangely, it now works perfectly.

Hola JazeFox!
I'm one of those people who have to automate everything, so I have a bunch of BAT files that take care of sound, networking, mouse, and whichever other drivers I need on any given machine. I'm obviously using UNISOUND for much of this, but there's a tiny thing that is bugging me: There is no "detection only" mode for non-PnP cards.
This is mostly a non-issue; my scripts run UNISOUND twice, once to locate the card I want to configure, and again to actually initialise it. This works fine when all my cards are PnP - e.g. a GUS PnP and some other PnP card for SB compatibility. It also kinda works for the non-PnP SB16, but it .. I don't know .. feels wrong? To initialise the card twice.

That's basically what this feature request boils down to: UNISOUND does everything I need it to do. I'm just bugged by the fact that I can't use it to detect - or rather, confirm the existence of - non-PnP cards in the system *without also initing them*.

So in case it was not clear: I love unisound, this is not a flaw. Just me being silly, I guess. :D

Take care,
/Eirik

Hey,
I just came accross this tool.

What is its role, I was hoping that I dont need any drivers, just need to do UNISOUND /V8o and it should work, but... I got "no pnp card found" and there is no snd.

I had to use back the CFG801, DOS801.

What is the difference?

retropol wrote on 2024-12-01, 13:33:

I had to use back the CFG801, DOS801.

You have Fortemedia FM801, for PCI, right?
UNISOUND is for ISA cards only.

ahhhh 😀 mental shortcut, thought it is universal driver for... every card 😀

I'm wondering if it would be possible to add this feature to UNISOUND: setting the BLASTER environment variable, maybe even other variables as well, eg. ULTRA16 for WSS-compatible cards.

Currently, if there's no BLASTER variable set, UNISOUND inits the card with defaults settings - OK.
But it's not enough for certain programs, as they need the variable.

It would be convenient if UNISOUND took care about that as well - but would it be reliable?
In general, the only place I trust for setting the environment is AUTOEXEC.BAT - in other places, it often ends up with "Out of environment space"...

What do you all think?

At least for BLASTER it is possible, by removing the non-standard things and leaving the essential ones: A, I, D, H, P, E and T depending on whether it is a SB16, AWE or an SBPro-compatible sound card. WSS doesn't have a properly standardized environment variable and ULTRA16 was originally intended for GUS sound cards that have the Crystal codec, so it won't work with everything.

As for "Out of environment space", try increasing the environment size when loading COMMAND.COM with the /E command line switch.

1SHELL=C:\COMMAND.COM /P /E:1024

In this case, 1024 bytes will be used for handling environment variables. Memory usage will be increased but the trade-off is worth it.

Gmlb256 wrote on 2024-12-01, 16:57:

WSS doesn't have a properly standardized environment variable and ULTRA16 was originally intended for GUS sound cards that have the Crystal codec, so it won't work with everything.

Mpxplay uses ULTRA16 to detect WSS, so I always add it to AUTOEXEC.BAT when installing a WSS-compatible card.

As for "Out of environment space", try increasing the environment size when loading COMMAND.COM with the /E command line switch.

Yes, but the goal is to simplify things - if UNISOUND can reliably set the environment with default DOS configuration, then it would be nice.
But if it's necessary to edit the SHELL statement, then the user might as well add the SET command(s) instead.

Grzyb wrote on 2024-12-01, 19:53:

Mpxplay uses ULTRA16 to detect WSS, so I always add it to AUTOEXEC.BAT when installing a WSS-compatible card.

True. What I meant is that the use of ULTRA16 for WSS isn't guaranteed to work with every DOS software that detect sound cards by only checking the environment variables.

Hi

I first tried this utility today and it's helped to reconfigure my Yamaha ISA card in DOS. I swear, when I installed some drivers for it (which I don't remember what they were now), DOS configured it automatically...? Now, it doesn't. Even if I add SET=BLASTER to my autoexec. This tool gets it working correctly, which is ace. 😁 However, having scanned through the Readme, I'm still unsure how to get it configured automatically every time I load into DOS. I did try adding SET BLASTER=A220 I5 D1 T4 J200 P330 UNISOUND.COM /V70, but it hasn't worked. Not sure if I need to set it up differently...?

This is the configuration:

EDIT: Okay, JazeFox’s post on the first page looks to have worked. 😁

If that's the folder you've extracted unisound.com into, then it won't be in the PATH variable, which is where DOS checks for programmes that you type at the command line.

Either put the FULL path in front of unisound.com in autoexec.bat, or, preferably, edit the PATH variable in autoexec.bat to add the unisound folder, so that you can run unisound.com anywhere you are.

Something like:

PATH=C:\DOS
PATH=%PATH%;C:\WIN98G~1\DRIVERS\YAMAHA~1\UNISOU~1\
unisound.com

or

PATH=C:\DOS
C:\WIN98G~1\DRIVERS\YAMAHA~1\UNISOU~1\unisound.com

The former is the better long-term option, as you are likely to want to call unisound.com before/after a game to set volume options... and you don't want to be typing that nasty long filename path over and over again.

megatron-uk wrote on 2024-12-04, 17:55:

If that's the folder you've extracted unisound.com into, then it won't be in the PATH variable, which is where DOS checks for pr […]
Show full quote

If that's the folder you've extracted unisound.com into, then it won't be in the PATH variable, which is where DOS checks for programmes that you type at the command line.

Either put the FULL path in front of unisound.com in autoexec.bat, or, preferably, edit the PATH variable in autoexec.bat to add the unisound folder, so that you can run unisound.com anywhere you are.

Something like:

PATH=C:\DOS
PATH=%PATH%;C:\WIN98G~1\DRIVERS\YAMAHA~1\UNISOU~1\
unisound.com

or

PATH=C:\DOS
C:\WIN98G~1\DRIVERS\YAMAHA~1\UNISOU~1\unisound.com

The former is the better long-term option, as you are likely to want to call unisound.com before/after a game to set volume options... and you don't want to be typing that nasty long filename path over and over again.

Yep. Adjusted it. I also simplified the directory so it’s easier. Now it’s in C:\UNISOUND\UNISOUND.COM 😀

For some reason, when I tried to test it with the on-board Crystal audio in this AST Advantage 824 (I think it has a CS4232, as it also has the QDsp stuff), it gives an error saying the only card it can find is the Rockwell modem (which it can't initialize).

Does unisound support the AuxB volume setting for the ESS 1868/1869 chips?
I cannot seem to find any setting for this, am I missing something?