Yes, I just was thinking that myself.

Not sure whether you did that already, but when you have a monitor attached, you will see the normal Windows boot menu passing by. If you, when that is about to appear, keep on pressing downarrow, you will interrupt the boot menu (without touching anything it stays there for 2 seconds).
In there you can select the OS again, with the notice that your choice won't stick for a next reboot (so if that is necessary in the process, repeat this procedure with the DownArrow).
Notice that I think that now all the OSes fit in that menu, but with Down-/Uparrow you can scroll through them.


No, not at all;
Something else is wrong but it is hard to tell what, as of yet.
If you can imply normal behavior in 10586.0 then 14393.0 became corrupt somehow. If in 10586.0 you see similar problems, it is worse ...

Peter

Booting into the BASE OS gives the same result ?
And if so, what happens when you boot into BAS 10586.0 ?

Hi Arvind,

Yesterday I had the hunch of something not being right with the priority settings, but internally, *or* there is a bug somewhere in XXHighEnd and you changed something regarding the priorities as well. And ... while writing this, what about you changed the Core Appointment settings ? I can't see it in the log (it is not registered) but it could be a "logical" thing you have done, regarding the latest remarks about it ...
Did you ?


So what happens ?

Regards,
Peter

David, if this gets too annoying, in your XX folder there's an OSIsW10.tss file while you can rename to OSIsW10.tst.
The errors should stay away by this means, but it is sub-optimal because there's no explicit support now for 14393.0 (although possibly by accident the support will be for the latest supported W10, which is 14393.0 ...).
Plus the cause will remain so no chance to find out what that cause is.

Peter

Arvind,

Can you give me the XX- logfile of this happening as well ?
If you're not sure which one it is (could be more than one) then it should contain log file entry times between ~14:08:56 and ~14:30:32.

It could be easier for you to zip the whole Temporarydata folder and email that to me (it won't be very large, unless you always have Logging switched on ).

Peter

Arvind - Thank you.

Unless I'm mistaken, where the X3PB ends, the X3 starts (the ones from your last post). IOW, they don't belong to each other.

Possibly you must kill Engine3 (blue led in the right border) after the happening so both log files will be compete(d). Or there is a situation at hand whcih we don't understand (which is likely in this case).

Regards,
Peter

Hi Arvind,

Logging works everywhere. Just look in
c:\XXHighEnd\2.xx\TemporaryData\
of your Stealth PC.

And no idea of course what suddenly could be in order. "Disk full" could be an obvious one, but then from data which is kept somewhere but shouldn't.
How much free space do you have on c: right after boot-up from RAM ?

Regards,
Peter

Hmm ... for me the Q5 to 3 does not work out, or I must give myself more time to get used to the (over here) more Sllshh sound (too white in the highs).

The Q3,4,5 to other than 1 for me is also a psychological thing because I know what it does (and it has to be for the better - haha).

Regards,
Peter

Hi there David,

This is something I have never heard of, but I understand the situation. Not the cause.
Is it correct that when this happens and XXHighEnd is on screen again, and you press Clear (Playlist Area) that in there it shows something like WINNT32 (instead of 14393.0) ?

Also, can you perhaps recognize since when this is occurring ?


This is the (for me) logical consequence of what went wrong initially. Please don't pay attention to it (but true, how to reboot now by remote).

Do you have activated either "Stop All Services" or "Stop W10 Services" ? If so, please try to deactivate both for a while and see whether that helps. It should be related, I think.
Btw, if it is Stop W10 services you have active, then know that you can deactivate that from within Minimized OS and notice (the) effect (assumed all is still OK). This does NOT count for Stop All Services - for that you must deactivate it in Normal OS and then boot back into Minimized OS.

Regards,
Peter

Nah, that is not possible. Or at least I wouldn't know how to ...

Hi Shreekant,


Do you have problems with this ? If Yes ... is maybe the error really "flashing" by as such ? (appearing and quickly disappearing)

Peter

Strangely rough sounding eh ?
Flakey bass.
Etc. what I forgot by now.

Hi Brian - It is no big deal at all. But in the topic I linked to (via my post in there) you "claimed" that. And today you did the same by means of :


I know, you guys call switching on a light bulb also "reboot", but nobody will understand. So in case you meant to "reboot" XXHighEnd, outside of the US we restart it. Haha.


This is completely correct. But also irrelevant because you didn't even switch off the light (you imply here not to quit XXHighEnd).


But then this again is beyond me. And I am pretty sure that at least that you didn't want to say. But if so after all, I need to know more.
Anyway now I am dizzy of inconsistency.

Peter

Hi Brian - Yes, thank you, I already forgot about that. Notice though that it was/is not related to the OS session but to the XXHighEnd session.


Peter

I think you don't know that, because it requires a Refresh first and :


... so how can you tell ?

It is a bit sad that I don't recognize any error there and certainly not a "flashing error" as you describe it. However, I assume it is a matter of speak (flashing would be something which briefly shows) and that you can make a screenshot of the error ?
So I'll wait for that - without that I really can't tell what this is about. OK ?

Kind regards,
Peter