XXHighEnd

Ultimate Audio Playback => XXHighEnd Support => Topic started by: bgjohan on April 02, 2010, 06:58:41 pm



Title: Problem running XXHIGHEND on XPSP3
Post by: bgjohan on April 02, 2010, 06:58:41 pm
Peter

I tried installing XX0.9y-08 on my son's PC running XPSP3 (AMD Athlon 3000+, 2GBRAM, 150GB IDE HD), but got an error message
"The application failed to initialize properly (0xc0000135). Click OK to terminate the application".

I thought problem possibly with XX0.9y-08/ XX0.9y-08c, but same problem with XX0.9y-06 and XX0.9y-04, which leads me to think something may be wrong with the PC (memory?).
Sound on motherboard is Realtek AC97 Audio, but it also failed (same error message) when trying with Logitech USB headphones that work fine with XX on my main Vista64 PC.
Would appreciate your assitance to diagnose and suggestion how to fix.
For a start, I do not really know if the error message is a WIN XP message or a XX message.

No panic with this - not my intention to prevent you from enjoying an Easter break.

Happy Easter
Bjorn   
 


Title: Re: Problem running XXHIGHEND on XPSP3
Post by: PeterSt on April 02, 2010, 07:58:07 pm
Hi there Bjorn !

I think this will solve it for you : How to delete a misbehaving ConfigFile (http://www.phasure.com/index.php?topic=709.0).
Let me know if this brings you an even better easter !

Peter

PS: But I'm also thinking of dot-net not properly being installed ?


Title: Re: Problem running XXHIGHEND on XPSP3
Post by: bgjohan on April 02, 2010, 08:51:13 pm
Peter

Unable to find any Phasure sub-directory or a Config file, as XX never loaded.
However, Realtek Audio is showing problems (even with updated driver); Realtek sound OK in WIN Media Player, but does NOT play music on HDTracks on the Net.
With USB Logitech earphones, I have sound both in WIN Media player and to play music samples on HDTracks on the Net.
For that reason , I have now disabled Realtek and using Logitech USB earphones for sound (at least until XX can be loaded)

So, thankful for direction re your mention of dot-net possibly not properly installed.
FYI, XPSP3 newly re-installed after a HD malfunction, thus very possible some essential XX support functions not (yet) properly installed.

Best regards

Bjorn