XXHighEnd - The Ultra HighEnd Audio Player
June 27, 2019, 12:23:24 pm *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: August 6, 2017 : Phasure Webshop open ! Go to the Shop
Search current board structure only !!  
   Home   Help Search Login Register  
Pages: 1 [2]  All
  Print  
Author Topic: Minimize OS Problem  (Read 14377 times)
0 Members and 0 Guests are viewing this topic.
PeterSt
Administrator
High Grade Audiophile
*****
Offline Offline

Posts: 15464



View Profile Email
« Reply #15 on: October 09, 2011, 09:50:39 am »

I am not sure about boleary's situation, but for Mani this may have happened :

I think we all know from W7 SP1 that at a (re)boot there can be this gray progress bar at the bottom of the screen which says "Windows is loading files" (that is, I don't recall this from W7 Vanilla ever). After this progress bar has filled up, the system goes into reboot automatically again.
This happens once in a while and I never saw the reason for it. But it does. Also, when you don't pay attention during the boot, it goes unnoticed. But :

What I expect is that this "resets" something Windows thinks is necessary. Something like a "last good boot situation". Now, it seems logical to me that this is taken from a (registry) "save" the OS always applies herself after a good boot, while Minimize OS goes a sort of against this. I know it does, or in other words, I know it can be done a tad more "official".
Btw, I never noticed this inconsistency.

Solution :
When you can see that the state of the Minimize OS button is not consistent with the actual situation, rightclick on the "Minimize OS" text which comes with the button, and choose to flip the state of the button (I think this is in the 0.9z-6 Release Notes as well). Now apply the reboot by means of the button and all should be as intended.
Keep in mind that the next (reboot) action at using the Minimize OS button is always taken upon its shown state. Thus, does it show "I'm minimized" (red) then using the button will go to normal. And the other way around;
When the shown state is the opposite from reality, a reboot using the button in that wrong state will always end up in how it was. So, reality is Normal but state shows Minimized, will obviously boot into normal again.

Important for your understanding :
The above anticipates a "normal" situation, no matter the shown state is inconsistent. Like the OS changing things behind "XX's back", like what could have happened to Mani.
This means that the state the button shows can only confuse you one time;
This is different from something being wrong at the reboot itself, which happened to Mani as well at using the beta-beta version for this, and what happened to someone else as well as which is why 0.9z-6-1b emerged. Then something really is wrong, and the state of the button will keep on being confusing forever.

Of course people will say : so show the real state - detect it;
This is not possible because all anticipates on the things you may have done yourself already. So, it may detect *that* and the button will stay red forever.

Peter
Logged

For the Stealth III LPS PC :
W10-14393.0 - Oct 31, 2018 (2.10)
XXHighEnd Mach III Stealth LPS PC -> Xeon Scalable 14/28 core with Hyperthreading On (set to 10/20 cores) @~660MHz, 48GB, Windows 10 Pro 64 bit build 14393.0 from RAM, music on LAN / Engine#4 Adaptive Mode / Q1/-/3/4/5 = 30/-/1/1/1/ Q1Factor = 10 / Dev.Buffer = 4096 / ClockRes = 15ms / Memory = Straight Contiguous / Include Garbage Collect / SFS = 140.19  (max 140.19) / not Invert / Phase Alignment Off / Playerprio = Low / ThreadPrio = Realtime / Scheme = Core 3-5 / Not Switch Processors during Playback = Off/ Playback Drive none (see OS from RAM) / UnAttended (Just Start) / Always Copy to XX Drive (see OS from RAM) / Stop Desktop, Remaining, WASAPI and W10 services / Use Remote Desktop / Keep LAN - Not Persist / WallPaper On / OSD Off (!) / Running Time Off / Minimize OS / XTweaks : Balanced Load = 35 / Nervous Rate = 10 / Cool when Idle = n.a / Provide Stable Power = 0 / Utilize Cores always = 1 / Time Performance Index = Optimal / Time Stability = Stable / *Arc Prediction Filtering (16x)* / Always Clear Proxy before Playback = On -> USB3 from MoBo -> Lush^2*A:B-W-Y-R, B:B-W-R* USB 1m00 -> Phisolator 24/768 Phasure NOS1a/G3 75B (BNC Out) async USB DAC, Driver v1.0.4b (16ms) -> B'ASS Current Amplifier -> *Blaxius^2 A:B-R, B:B-R* Interlink -> Orelo MKII Active Open Baffle Horn Speakers.
Removed Switching Supplies from everywhere (also from the PC).

For a general PC :
W10-10586.0 - May 2016 (2.05+)
*XXHighEnd PC -> I7 3930k with Hyperthreading On (12 cores)* @~500MHz, 16GB, Windows 10 Pro 64 bit build 10586.0 from RAM, music on LAN / Engine#4 Adaptive Mode / Q1/-/3/4/5 = 14/-/1/1/1 / Q1Factor = 1 / Dev.Buffer = 4096 / ClockRes = 1ms / Memory = Straight Contiguous / Include Garbage Collect / SFS = 0.10  (max 60) / not Invert / Phase Alignment Off / Playerprio = Low / ThreadPrio = Realtime / Scheme = Core 3-5 / Not Switch Processors during Playback = Off/ Playback Drive none (see OS from RAM) / UnAttended (Just Start) / Always Copy to XX Drive (see OS from RAM) / All Services Off / Keep LAN - Not Persist / WallPaper On / OSD On / Running Time Off / Minimize OS / XTweaks : Balanced Load = *43* / Nervous Rate = 1 / Cool when Idle = 1 / Provide Stable Power = 1 / Utilize Cores always = 1 / Time Performance Index = *Optimal* / Time Stability = *Stable* / Custom Filter *Low* 705600 / -> USB3 *from MoBo* -> Clairixa USB 15cm -> Intona Isolator -> Clairixa USB 1m80 -> 24/768 Phasure NOS1a 75B (BNC Out) async USB DAC, Driver v1.0.4b (4ms) -> Blaxius BNC interlink *-> B'ASS Current Amplifier /w Level4 -> Blaxius Interlink* -> Orelo MKII Active Open Baffle Horn Speakers.
Removed Switching Supplies from everywhere.

Global Moderator
Pages: 1 [2]  All
  Print  
 
Jump to:  

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.085 seconds with 19 queries.