Custom Query (242 matches)

This is closely related to Ticket #51.

While not entirely impossible, the DDK is hard to get these days, so it does keep some people from building Uniaud32 who might otherwise.

This makes it extremely difficult to debug Uniaud in the same way that ALSA does, as they rely on testers and bug reporters to build the driver themselves for testing.

It is important to note that under the GPL, we can include the DDK headers as-is, but any replacement code must be GPL, so essentially it must be implemented anew in Uniaud.

Skimming through the instructions on the wiki site, I'm pretty sure they aren't right anymore, now that the uni32 and uni16 builds are separated.

It should be very clear exactly what is required to build uniaud32 and uniaud16. Some missing details are the OS/2 toolkit, ilink, lxlite. I've heard of difficulty when 4os2 is not present as well, though that needs to be verified.

Also there is no mention of the ACPI toolkit. There should be some verbage on the meanings of the build types, e.g. KEE, ACPI, W4, DEBUG.

Once updated, it might also be good to include the doc in the package.

As one tries to run install.cmd it exit immediately. I then compared the contents of the package with a previous version and came to the conclusion that cardinfo.dll was/is not a part of Uniaud but rather the setup procedure. I replaced cardinfo.dll with a version from the previous package and then minstall run and install fine.