Debugging the Uniaud drivers
This page lists some of the common problems with the Uniaud drivers and how to resolve them.
If you open a ticket, additional information will almost always be necessary. You can save a lot of time by always attaching the log file created by the TestLog program to your ticket when you open it, rather than waiting for the developer to ask for it.
Known Problems and Limitations
If you are using ACPI.PSD, you must have version 3.20.01 or later. Uniaud32 will not work with ACPI.PSD versions older than 3.20.01.
Some systems have more than one audio adapter, some of which do not work. Uniaud32 always tries to initialize all the adapters in the system, but only selects the first one to use. If Uniaud32 detected more than one adapter, and the first one is the one that doesn’t work, you can use the /A switch to force Uniaud32 to skip adapters and use a different adapter. For example putting /A:1 on the Uniaud32 command line will force it to skip the first adapter and use the second one.
Most problems with Uniaud are incorrect mixer settings. Use a mixer application (or unimix) to check and set the mixer switches and volume settings appropriately for your system.
Capturing a TestLog log file
If you don’t already have the current version of the TestLog program, you can download it here: Get TestLog
Open a command window and execute the testlog command:
Attach the created log file to your ticket. Do not ZIP the log file.
Real Time Logs
You can see the log output in real time by connecting a terminal or second system to the serial port.
Enable the serial output by adding the “/P:1” or the “/P:2” switch to Uniaud32.sys in your config.sys. /P:1 specifies to use serial port 1, and /P:2 specifies to use serial port 2.
Set the serial port baud rate to 115200, 8 bits, no parity.
If you are getting kernel or driver exceptions, a trap dump can often get you the data to figure out where and why this is happening. See How to Get a Trap Dump for a setup guide.