Opened 9 years ago

Closed 9 years ago

#186 closed defect (fixed)

UNIAUD32 not loaded with msg: "ERROR: Initialization failed"

Reported by: ecki Owned by: dazarewicz
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)

ECS15044219-20100722-uniaud-2.1.zip (5.2 KB) - added by ecki 9 years ago.
Output of UNILOG.cmd
ECS15044219-20100726-uniaud-1.9.23.zip (16.7 KB) - added by ecki 9 years ago.
Output of UNILOG.cmd - after successful test UNIAUD debug

Download all attachments as: .zip

Change History (6)

Changed 9 years ago by ecki

Output of UNILOG.cmd

comment:1 Changed 9 years ago by ecki

  • Component changed from Building to UNIAUD32

comment:2 Changed 9 years ago by dazarewicz

  • Owner set to dazarewicz
  • Status changed from new to assigned

Please test this version to see if it finds your audio hardware:

http://www.88watts.net/download/UniaudTest20100724.zip

Changed 9 years ago by ecki

Output of UNILOG.cmd - after successful test UNIAUD debug

comment:3 Changed 9 years ago by ecki

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 Changed 9 years ago by dazarewicz

  • Resolution set to fixed
  • Status changed from assigned to 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.

Note: See TracTickets for help on using tickets.