Opened 14 years ago
Closed 14 years ago
#186 closed defect (fixed)
UNIAUD32 not loaded with msg: "ERROR: Initialization failed"
Reported by: | ecki | Owned by: | David Azarewicz |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | UNIAUD32 | Version: | 2.0 |
Severity: | normal | Keywords: | |
Cc: |
Description
UNIAUD32 displays msg "ERROR: Initialization failed". Thus loading UNIAUD16 halts boot process with msg: "unable to attach 32-bit driver .. Press ...". Machine is custom built with an ASUS M2V motherboard. The only UNIAUD version that works on this machine is UNIAUD32 v. 1.9.21-SVN r465.
Attachments (2)
Change History (6)
by , 14 years ago
Attachment: | ECS15044219-20100722-uniaud-2.1.zip added |
---|
comment:1 by , 14 years ago
Component: | Building → UNIAUD32 |
---|
comment:2 by , 14 years ago
Owner: | set to |
---|---|
Status: | new → assigned |
Please test this version to see if it finds your audio hardware:
by , 14 years ago
Attachment: | ECS15044219-20100726-uniaud-1.9.23.zip added |
---|
Output of UNILOG.cmd - after successful test UNIAUD debug
comment:3 by , 14 years ago
Thanks for the quick reaction:
- UNIAUD loads ok
- system sounds work
- sound works ok with Emperoar (short test)
- Emperoar sound controls work
but there is a new effect:
- system sounds are terminated with a "click" or "plop"
comment:4 by , 14 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
You should use the retail version, not the debug version. The debug versions have known problems including the pop at the end of sounds. I just updated the wiki about this.
Output of UNILOG.cmd