XXHighEnd - The Ultra HighEnd Audio Player
August 25, 2016, 11:55:20 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
 71 
 on: August 19, 2016, 07:42:26 am 
Started by PeterSt - Last post by acg
To add to this, I have figured out that I can boot into the various RAM versions ok (so long as they are not an expired OS) but as soon as I try to boot into any of the BASE versions (by setting it so in XXHE) W10568 RAM tries to load and of course that is an expired OS.

I need to boot into a BASE version to set the network mapping for the music and streaming directories.

 72 
 on: August 19, 2016, 05:43:57 am 
Started by PeterSt - Last post by acg
All,

I was wondering ... Does the procedure work in the first place ?
I'm asking because I don't see any feedback so I just wondered. If it sounds like sh*t you can say it too, of course.

Peter

Procedure does not work for me.  The instructions are quite vague and can be read a few different ways so I am not sure if I have followed what you intended us to do precisely (well I probably have not it seems), but the boot procedure for my AudioPC is now dysfunctional and will only boot into W10565 by itself (which I have never used) regardless of what it is set to start into from XXHE boot menu.  W10-14393 is not available in the boot menu at computer startup at all. 

I need the monitor back so I can work so currently have no functioning AudioPC.  Not sure what to do.  Are you able to write out a set of steps 1,2,3 from a known starting point?  That would be less cryptic.

Anthony

 73 
 on: August 18, 2016, 07:19:57 pm 
Started by CoenP - Last post by CoenP
I can imagine that you have the same problem as me ... which log file is the actual one. Well :

Quit XXHighEnd;
Delete all the log files;
Start XXHighEnd;
Stop-RightClick - Boot Into;
Grab Log File.

Happy

Great tip!

I actually found two logs in the emptied directory.

See attachment,

regards, Coen

 74 
 on: August 18, 2016, 07:04:23 pm 
Started by CoenP - Last post by PeterSt
I can imagine that you have the same problem as me ... which log file is the actual one. Well :

Quit XXHighEnd;
Delete all the log files;
Start XXHighEnd;
Stop-RightClick - Boot Into;
Grab Log File.

Happy

 75 
 on: August 18, 2016, 06:47:08 pm 
Started by CoenP - Last post by PeterSt
Quote
a selection of recent logs

Coen, I am super sorry, but this is useless to me. Obviously I am asking for the situation, well, I asked for.
Do notice that Dates/Times don't tell a thing in this case (have a look yourself and you will understand).

Peter

 76 
 on: August 18, 2016, 05:47:48 pm 
Started by CoenP - Last post by CoenP
We're getting all mixed up with these versions, but I followed your instructions without making the boot form 14388. Yet a selection of recent logs of the 2.xx\TemporaryData\ have been added to the zipfile that is attached.

regards, Coen

 77 
 on: August 18, 2016, 11:13:53 am 
Started by CoenP - Last post by PeterSt
OK, thinking outloud ...

I can try to do it in the blind, but better would be to show the log after choosing Stop-RightClick - Boot Into.
No need to switch on the logging.

Thus :
Start XXHighEnd (maybe it is best to be in 10388 following the attempt to boot into 10586.0 BASE);
Stop-RightClick - Boot Into;
Grab the logging and post as attachment.

What I hope is that I recognize my own situation and from there know again what (steps) to do for real.

 78 
 on: August 18, 2016, 10:21:03 am 
Started by CoenP - Last post by CoenP
If I understood well (by some PM you sent me), the problem emerged from abusively booting 14388 into MinOS. Or maybe you weren't sure about that, but anyway it could be a good reason because at least that is not any scenario to apply (TRIAL - Do not use etc. blah).

Whether this knowledge helps us, I don't know. But it is always good to find causes for a next time.

Can you by now confirm that this happened (be in 13488 TRIAL and go to MinOS from there) ?

It is true that I was under the impression at first that I booted into 10586. Then I went into MIN-OS and noticed after the boot that I was not in the proper OS version and rebooted immediately back into normal OS. This could have caused the problem, however I have no reference for this behavior, because it was the first time I tried to boot into a BASE version in order to MIN-OS it.

regards, Coen

 79 
 on: August 18, 2016, 10:02:30 am 
Started by CoenP - Last post by PeterSt
Talking to myself (and for later reference only) :

I have had similar recently, and I am almost sure it happened at setting up this TRIAL OS (143xx) myself. However, I also recall that I did something wrong myself, so I did not put real attention to it.
Additionally, quite some people by now have performed this 10565 -> 14388 upgrade and no complaints so far from anyone else.
Still I had similar ...

I solved that by means of manually adjusting things in the BCD Store, but in aftermath I think it can be done differently. I will try to work that out in the next post(s), if you, Coen, bear with me to try those things. Maybe to no avail ...

 80 
 on: August 18, 2016, 09:58:16 am 
Started by CoenP - Last post by PeterSt
If I understood well (by some PM you sent me), the problem emerged from abusively booting 14388 into MinOS. Or maybe you weren't sure about that, but anyway it could be a good reason because at least that is not any scenario to apply (TRIAL - Do not use etc. blah).

Whether this knowledge helps us, I don't know. But it is always good to find causes for a next time.

Can you by now confirm that this happened (be in 13488 TRIAL and go to MinOS from there) ?

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.498 seconds with 15 queries.