XXHighEnd

Hi Peter, very, very long time no talk! I hope you, Ciska and Paul are all OK.

I'm trying to load the NOS1 driver onto my work PC (which has W10 updates set to automatic). When I use the 'setup' in the 'Phasure_NOS1_v1.0.4b_768_setup_production' folder, I get the first error. If I use 'update driver' in Device Manager, I get the second error.

Any ideas?

Cheers, Mani.

Edit: sales at phasure dot com is getting bounced back

Hi Mani - this is what I just sent you by email (I surely received yours (twice)) :

Although your screenshots are barely readable, it is my estimate that this is about the Driver Signing not being shut off. This can be done n XXHE settings, remember ?

After changing the setting, reboot (IIRC).

But in here (forum) I am able to read what's in your screenshots and now I don't know. The message about the catalog file and the tampering is unknown to me, although I'd understand what it means.
Try the Signing thing anyway, and let me know whether it helps. By forum would be the best, assumed others may run into this as well ?

Kind regards,
Peter

I got two 'undeliverable mail' messages, so not sure what is going on there.


This is my work PC and I don't have XX installed on this. I'm just trying to get my office NOS1 working with my work PC so that I can use my work PC as a RoonBridge. I don't intend to use XX on this PC and therefore don't really want to install it (but of course, I will if I have to).

I've just disabled driver signature verification in the Local Group Policy Editor... but I'm still getting the same error.

Any other ideas, or do you recommend I install XX and try disabling the driver signing from there?

The message "The hash file is not present in the specified catalog file" sounds a bit more 'serious' that simply disabling driver signing...

Mani.

OK, I've just tried to install the NOS1 driver on my music server, which has XX installed (for Tidal).

1. Click on Refresh button next to 'Driver Signing?' -> "Drivers must be signed"
2. Click on Change button & reboot

Install driver -> same error message as before

3. Start XX and click on Refresh button next to 'Driver Signing?' -> "Drivers must be signed"

(Driver signature verification doesn't seem to have been disabled.)

Any ideas?

Mani.

Mani, what about considering the message to be true and that somehow the copying from whatever source prevented a file to come along ? Or, that the unzipping of the original zip file (I guess you have that) disallows that file(s) ?
As we know, similar can happen with the install of XXHighEnd.

Peter

Hi Peter, I've tried unzipping the original file, but I get the same error.

It's been a very long time since I last installed the NOS1 driver on a HDD because I've been using a RAM-OS disk with the driver pre-installed.

Could you email the 1.04b driver to me again just to eliminate the possibility of a corrupted file please? Thanks.

Mani.

Done.
But after unzipping, you still should compare the files (number of) with the contents of the zip I sent.

Check XXHighEnd for the Driver Signing still to be Off; All the Google finds still lead to that for this message (FWIW).

Peter

Hey Peter, I don't think disabling driver signing in XX works. I did it through W10 startup (as explained here: https://windowsreport.com/driver-signature-enforcement-windows-10/) and I was able to install the driver. (I had to click on 'install anyway' a few times.)

Thanks for sending me the driver (was unnecessary in the end), and perhaps this may be helpful for anyone else attempting to install the driver on an updated W10 machine in the future.

Mani.

The driver installed OK. I disabled 'enhancements' in the Sound Control Panel.

None of the players I had installed on my work PC worked with the NOS1 under WDM.

So I installed XX (still non-activated). KS works fine (and sounds brilliant!). XX WASAPI works perfectly with another USB DAC I have connected to the PC, but I cannot get WASAPI to work with the NOS1. No other player seems to work with the NOS1 WDM either.

This is all pretty confusing. I suspect that one of the recent W10 updates has stopped the NOS1 working correctly with WASAPI.

Mani.

SOLVED!

It was the usual Sound Panel Settings that had to be set exactly correctly.

Firstly, make sure enhancements are switched off in the W10 Sound Control Panel.

Set the Phasure Control Panel to the sample rate that you want. Then set and test the sample rate in the W10 Sound Control Panel.

DO NOT ALLOW ANY OTHER RATE TO REACH THE NOS1.

Phew...

Mani.

Haha.
Well done !
Good that it's all solved now.

Regards,
Peter