XXHighEnd Model 2.00 - Installation of driver release 1.04

[christoffe]

Hi Peter,

installed the new driver as per "driver + manual" (on within the normal OS - not minimized) several times (at least 5x) and the driver don't see the DAC. ***(XXH 2.0 not activated until now)***
The driver release 1.03 installation works without any problems and recognizes the DAC immediately.
Any idea?

The W7 shell installation is the same as with the preXXH 2.0 release, right. So I left the previous W7 shell installation untouched.

Thanx

Joachim

[PeterSt]

Joachim,

Can you show me the state of that button/function which needs to be set ?
If you don't know what I mean then that's the problem.

W7 Shell is unrelated. Activation is also not related.

Peter

[christoffe]

Can you show me the state of that button/function which needs to be set ?

General - New / Changed

    There's a new Driver available for the Phasure NOS1a D/A converter for Windows as well as Mac. Drop us an email when you want it BUT do that only when you really need this (do it for fun is useless).
    Important (only for NOS1a owners) :
    - Once this Driver has been installed, the unofficial XXHighEnd 1.186-i version should *not* be used (1.186-a is OK).
    - When on Windows 8 or above and this Driver is to be used *and* you want to use XXHighEnd, you will *need* XXHighEnd 2.00 (see next topic).
    - When you use XXHighEnd 2.00 you will *need* this new Driver (1.04) or otherwise you can only play 44.1 based material ( 44.1, 88.2, 176.4, 352.8 ).

    Phasure NOS1a owners only (important) :
    In Settings there's a new button in the Output Section tagged "Driver Signing". This button needs to be set to "Drivers need not be signed" when the 1.04 Driver has been installed on Windows 8 (or higher). A necessary reboot wil be the effect.
    The text on the button itself will at first show "Refresh" and clicking it will show the current state. Next the text on the button will show "Change" and once the button is now clicked again, a reboot is required; not doing so (like clicking the button again) will make the state unreliable until a reboot happens. So always reboot right after an attempt to change.
    (and change back to the necessity to work with signed drivers is possible just the same; but there's no real reason for this)
    Do this (set to "Drivers need not be signed" + reboot) before installing the new driver.

-----------------------

That's what I found

Joachim

[PeterSt]

Ok, good find. I assume you did that.

Can you see anything during the driver install that looks like an error ? So I think you can see the log data passing by and when it doesn't install because of for example this Driver Signing you will surely see something which isn't right (I recall the log just ends with that).

Peter

[christoffe]

Ok, good find. I assume you did that.

Can you see anything during the driver install that looks like an error ? So I think you can see the log data passing by and when it doesn't install because of for example this Driver Signing you will surely see something which isn't right (I recall the log just ends with that).

Peter

Hi Peter,

The installation ends with the same sequence as with the driver 1.03, "disconnect .... etc." The process looks normal.

The notes in the driver panel see the PDF file attached.

Joachim

[PeterSt]

Very very strange, Joachim.

You also have a normal Desktop PC, is that right ?
If so, is it cumbersome for you to test that ?
(it just should work and now I don't understand why)

Thanks ...
Peter

[christoffe]

Very very strange, Joachim.

You also have a normal Desktop PC, is that right ?
If so, is it cumbersome for you to test that ?
(it just should work and now I don't understand why)

Thanks ...
Peter

Ok, i will test the driver on the PC.
Joachim

[christoffe]

Very very strange, Joachim.

You also have a normal Desktop PC, is that right ?
If so, is it cumbersome for you to test that ?
(it just should work and now I don't understand why)

Thanks ...
Peter

Hi Peter,

the installation of 1.04 on a desktop PC was finished without any problems!

Strange, on the laptop it did not work, as mentioned before.

Joachim

******Within the "hardware manager" there is a note about the driver - code 52****

[PeterSt]

Joachim, thank you for trying this.

Your Sig says that the laptop uses a 64bit OS. Is that correct ?

Thanks,
Peter

[christoffe]

Joachim, thank you for trying this.

Your Sig says that the laptop uses a 64bit OS. Is that correct ?

Thanks,
Peter

Hi Peter,

correct, 64 bit W8.

I sent you two emails with some info's.

Joachim

[PeterSt]

All,

If someone else runs into this issue ... with the great help of Joachim there is a solution to this. Will post tomorrow !

Regards,
Peter

[PeterSt]

All,

It is now known that the proposed procedure for installing and using the 1.04 Driver version for the NOS1a for at least one person does not work. This can be solved by downloading this version of the Sound Engine :

XXEngine3 for Driver 1.03

In this small package there's also a Driver103.tss file;
When this is renamed to Driver103.tst you can work with the old 1.03 Driver Version for your Phasure NOS1a D/A converter.
Notice that it now will work by the same means as was applied to XXHighEnd version 1.186-i and that this implies that you need XXHighEnd (2.00) to switch between 44.1 and 48 based music files (that is, if you want the clock speed to be correct for 48 based files). In other words : External programs will not switch to the correct clock base - for that you will need the 1.04 Driver to get running.

Procedure :
1. Kill XXEngine3.exe from memory;
2. Unzip the doanload over your current XX Folder (only 2.00(-a) version !);
3. Rename Driver103.tss to Driver103.tst;
4. Start playback.

Watch out : This is already obtained in the today uploaded 2.00-a Version of the complete XXHighEnd package.

Questions ? just ask.

Peter