XXHighEnd

Ultimate Audio Playback => XXHighEnd Support => Topic started by: Robert on March 20, 2016, 01:34:50 am



Title: Ram OS issues
Post by: Robert on March 20, 2016, 01:34:50 am
Hi Peter,
          I mounted Ram HD and booted into 10565 no problems stopped Defender and No updates. Then opened XXhighend and then loaded Base 10586.0 into boot menu. Boot menu had nothing in it. I then opened 10586.0 and loaded drivers. I'm only using 10586 for now.

All go and I tried to play a track in normal OS but got a message Filter 5 can not start. Should I be able to start XXhighend in this mode?

I'm also unable to load W10- 10586.0 RAM Memory into Boot menu. What is the procedure for this? Should I have done this when I created the Base?

Do I have to create Drive X and where would I do this?

I presume I would set all the settings required in XXhighend(my DAC and playback settings) then put into Min OS before loading into Ram.

Robert


Title: Re: Ram OS issues
Post by: PeterSt on March 20, 2016, 07:03:28 am
Hi Robert,

It looks like you have another OS disk in the system somewhere. Can this be the case ? Notice that this even can be an old OS disk, now filled with music, but which is bootable.
If so, remove that disk.

And of course you must boot from the RAM OS Disk.

Lastly, it looks like you're not starting XXHighEnd from the RAM OS disk as well. But if you think you do, show me a screenshot of the Title Bar of XXHighEnd.

Too many things not right, as it seems !
Peter


Title: Re: Ram OS issues
Post by: Robert on March 20, 2016, 08:29:26 am
Yes two other OS's I will disconnect them. Then will start again.
Booting from the RAM OS disk is only possible using W10- 10586.0 Memory in the boot menu. I was unable to load this in the Boot menu. But I will try this after disconnecting other OS's.

To load this it needs to point at the 10586 VHD file in the C:\ drive then apply with the tick box in RAM. Is this right?

Robert


Title: Re: Ram OS issues
Post by: Robert on March 20, 2016, 07:10:04 pm
Hi Peter,
           Disconnected other OS's and rebooted and the boot screen appeared with everything on it. I rebooted to 10586 Base and checked settings and that my DAC was connected then rebooted into Min OS.

Then rebooted into 10586 Ram memory and this worked with all now in RAM.

When I push play it won't start and this comes up:

Filter 5 - can not start because of filter sampling rate mismatch.

I have them set to 14-1-1-1 as per normal. Looks like I have broken something.

Sorry for trouble, I didn't read anywhere not to have any other OS's connected. I've always had 2, 1 for xxhighend and one for video, spotify etc.

I will set up other OS's to try this evening.

Can I put my Benchmark driver in the installs folder on the Ram drive? This will save me downloading for every OS.

Robert


Title: Re: Ram OS issues
Post by: Robert on March 21, 2016, 05:47:42 am
Hi further to previous post. I have put Benchmark DAC driver file in the installs file to use with other OS's.

I have managed to get W10565 working in Ram and cured above filter problem by unticking the "Is Phasure NOS1" Box. Yeah!!!! Trap for young players.

But in going back to W10586 and unticking NOS box, it has not worked but it will play if I reduce upsampling to 16/44. Filter problem seems stuck even with rebooting in normal OS and back again.

Now after resetting boot menu 10586 from RAM back to Base it always wants to reboot back to Ram. I can change this at bootup if I'm quick at startup screen.

Robert








Title: Re: Ram OS issues
Post by: Robert on March 21, 2016, 06:18:59 am
Ok more progress after changing 10565 back to normal OS, boot menu has come right. I had unticked NOS box in RAM 10565, bad boy.

It appears I had also unticked ARC prediction box now filter problems in 10586 seem to have gone. I have not tried Ram yet but its looking good.


Title: Re: Ram OS issues
Post by: Robert on March 21, 2016, 07:50:38 am
Hi, found filter problem, custom filtering was set for NOS now all going in RAM 10586.

Gosh is this a conspiracy for me to get a NOS Dac.

I can see this happening oh no more money!!!

Robert


Title: Re: Ram OS issues
Post by: PeterSt on March 21, 2016, 08:56:55 am
LOL!

One thing to add I think :
The boot menu obviously is for the boot setting (which OS to boot into). However, don't forget to click Apply once you denoted another OS to boot from. I fell into that pitfall myself, just the other day.
Thus : Pick OS to boot from, click Apply, click Reboot.

Otherwise well done and apologies it's a bit NOS1(a) oriented. I didn't even do that on purpose. But it is what I said somewhat longer ago by now : it is not even easy to "set" an environment for you all which normally installs from scratch and with that does not require (my) attention.

Peter