XXHighEnd - The Ultra HighEnd Audio Player
July 25, 2016, 10:06:19 pm *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Dec. 31, 2012 : XXHighEnd + Phasure NOS1 DAC receive 6moons Blue Moon Award !
** "Lonely at the very top" **
Search current board structure only !!  
   Home   Help Search Login Register  
Pages: [1] 2 3 4 5 6 7 8 9 10
 1 
 on: July 25, 2016, 08:12:54 pm 
Started by jhmvl - Last post by jhmvl
Hi Peter,

Here is the screenshot. I am not sure if it will show up because I attached it as a file.

As said, if I select a base OS from this screen then it will only boot me into the service OS. If I select a RAM OS then everything works as expected   wacko bzz.

Regards

Hans

 2 
 on: July 25, 2016, 05:33:48 pm 
Started by jhmvl - Last post by PeterSt
Hi Hans,

In this case I think the screenshot will be informative. So yes please. Just the screen which follows from the "Boot into" choice.

Thanks,
Peter

 3 
 on: July 25, 2016, 03:56:31 pm 
Started by jhmvl - Last post by jhmvl
Hi,

I have some strange behaviour of my RAM OS disk. After successfully upgrading the service OS as Peter described I can now boot only into the service OS and the RAM OS'es but not into the base OS'es. I select a base OS in xxhe to boot into, press apply and then reboot but it goes staright into the service OS and not the base OS that I selected. If I then look in xxhe which OS I selected for booting it points to the service OS, which is definitely not what I selected (I am very sure of that after trying a few times now). Any idea what I can do to boot into the base OS (the RAM OS'es start fine which to me is strange becuase it is the same as the base just booted from RAM if I understand it correctly).

I hope this description makes sense. If not then I can try to post some screenshots, not entirely sure that that will be informative so I did not do it straight away.

Regards

Hans

 4 
 on: July 25, 2016, 12:08:03 pm 
Started by manisandher - Last post by manisandher
I'm going to go back into Normal OS and switch WASAPI off. Will report back...

Well, this seems to have fixed the problem. Everything is working fine when I use RDC with a 1920x1080 screen.

But when I use my laptop with a 3200x1800 screen, the XX window is 3-4 times smaller and pushed up into the top left-hand corner when coming out of Unattended. As before, closing XX and restarting brings the XX window back to how it was originally (before going into Unattended and then Alt-Xing out).

Nothing else to say, I don't think...

Mani.

 5 
 on: July 25, 2016, 11:23:05 am 
Started by manisandher - Last post by PeterSt
Quote
All worked fine with 2.05!

And what ?
Please see that you may imply that I must be careful that such things will work over PC's, which is impossible. Only with luck you won't notice anything of it. Over 400 things are registered (saved) when XXHighEnd is closed, and they are all environemnt related. Load that into another PC and there you *will* go, one way or the other and not today then tomorrow.

No need to further respond to this as I only like to make this clear. Otherwise
a. I said that it won't be the problem anyway;
b. that I *did* change things in exactly the area of your issue.

Ad b.
So it is almost logic that prior to 2.06 you did not notice.

Lastly, I only elaborated so you can pion point the cause, hopefully.

Regards,
Peter

 6 
 on: July 25, 2016, 09:54:36 am 
Started by manisandher - Last post by manisandher
Hi Peter,

Remember, the TRIAL OS is totally unrelated to this all.

Sure - I just wanted to let people know I'd updated the TRIAL OS.

This has to be related to some sound device different setting (for the both PC's you use).

I have WASAPI active in both PCs (so I could play around with a few things). Perhaps this is the issue? Strange then that one PC is 'happy' and the other isn't.

But also : keep strictly in mind that you might imply quite strange issues with using, well ... one BASE for two PC's. Understand ?

All worked fine with 2.05! I've just tried 2.05 again and it comes back from Unattended just fine. Something is not right though with 2.05 too... the monitor remains on (i.e. the screen does not go black as it should with the settings I use).

Can you see whether you have Show Tooltips (bottom of Settings) active and if so, switch if Off and try again ?

I always have this off. Have just tried with it on and off - exactly the same.

I'm going to go back into Normal OS and switch WASAPI off. Will report back...

Mani.

 7 
 on: July 25, 2016, 08:56:25 am 
Started by manisandher - Last post by PeterSt
Hi Mani,

Remember, the TRIAL OS is totally unrelated to this all.

Strangely enough I have been working on exactly what you have there, and it was solved in 2.06/2.06a. Nobody ever announced the problem, but now you do *after* installing this version.

This has to be related to some sound device different setting (for the both PC's you use). But also : keep strictly in mind that you might imply quite strange issues with using, well ... one BASE for two PC's. Understand ?
Anyway that was my first thought when I saw the screen's showing odd, but at second thought the issue starts with that error message and that is internally about sound device stuff.

Can you see whether you have Show Tooltips (bottom of Settings) active and if so, switch if Off and try again ?

Peter

 8 
 on: July 24, 2016, 11:21:53 pm 
Started by manisandher - Last post by manisandher
Not sure if it's related, but I've had the 'initialization failed' error message on both audio PCs.

Also, before applying a presetloader.XXSI, I was not getting the full path in the XX title bar. (I've used Peter's screenshots here, but mine were/are identical with the 2.06 replaced by 2.06a).

Mani.

 9 
 on: July 24, 2016, 10:59:02 pm 
Started by manisandher - Last post by manisandher
I just updated my RAM-OS disk per Peter's instructions. (As an aside, I also had an issue with the Windows 7 DVD DownloadTool. Tried on a W7 and W10 machine, but got the same error message as Juan. 'isotousb.com' worked perfectly - thanks Robert.)

I then loaded XX2.06a onto W10586 base on the RAM-OS disk. Now, I use the same RAM-OS disk on two totally separate audio PCs - one in my office and the other in my main room.

The office audio PC works perfectly. But I've got an annoying issue with the main audio PC. I'm having what looks like a scaling problem when coming out of Unattended. The only solution is to then close XX and open it again - the scaling problem is then totally resolved.

I'm using exactly the same hardware and RDC connection as before - coming out of Unattended has worked perfectly with XX2.05 since I received the RAM-OS disk at the beginning of the year. I'm made no changes to the RDC whatsoever.

I haven't seen anything in the scaling and skinning tutorials (http://www.phasure.com/index.php?board=12.0) that seems to address this issue.

Any ideas?

Mani.

 10 
 on: July 24, 2016, 10:16:03 am 
Started by CoenP - Last post by Robocop
YES with the new settings.

Pages: [1] 2 3 4 5 6 7 8 9 10
Powered by MySQL Powered by PHP Powered by SMF 1.1 RC2 | SMF © 2001-2005, Lewis Media Valid XHTML 1.0! Valid CSS!
Page created in 0.274 seconds with 15 queries.