Custom Query (242 matches)

For memory savings and other reasons, Uniaud32 should be made to load only the support for installed devices.

Two options are proposed to achieve this. We need to investigate which would be the most prudent.

1. Implement the module loader from Linux, so UNIAUD32.SYS loads module objects from disk the way Linux does.

2. Change the build to generate individual .SYS drivers like UNIAUD32.SYS now, each only for a single device. The correct ones are then added to CONFIG.SYS.

Currently, the only documentation for Uniaud comes in the form a readme text file. My impression is that few people bother getting more than halfway down through the file, and it does not serve as a handy local reference due to its text format.

I propose migrating much of the standard text in the current readme to a .inf, and reserving the readme for changes and updates. Ultimately, unimix documentation should be included in the reference documentation (see ticket #142).

The component on this ticket should be "Docuemntation" and this will be recharacterized when that category is available.

I know that they said, back when VPC was still a live project, that the only supported audio driver was Sander's sbliveos2. But earlier versions of Uniaud did work. Now that I've finally got Uniaud working again with 1.9.8, I was disappointed that I got no sound. That's kind of a deal-breaker for me, because I need VPC for all the things I can't do in OS/2 (e.g. most Flash).

Other comments on 1.9.8: It supports this fairly new Intel HDA chip, and I'm truly impressed by that. The only problem I have apart from VPC is that I get a small hiccup on system sounds -- like a stutter: it repeats about a half-second of the wav file that just finished, like a stinger.