XXHighEnd

Hi Peter,
I have a problem with the minimize OS function. After my initial install it was working fine. Man, what a sound...
But after switching back to normal I'm not able to minimize again, the OS comes up in a normal state with everything activated. I can use a system restore point from 2 days back and reinstall XXHE, then it is exactly working for one session, then same again. Automatic updates are off and nothing has been installed. I'm using W7 Home Premium 64 with SP1. Do you have any hint where I can check what could be the reason ?
UAC if off, starting with Admin and the player itself is working fine.

best regards,
Bernd

Ah, at last ... someone with a real problem !  :) :)

Ok Bernd, this will require some digging. If you don't mind, we'll take it up from here through normal email. Ok ?

(now I must think about some initial questions for you, so hold on)

Peter

And a question to others please :

Anyone out there with Home Premium using Minimize OS succesfully ? And if so, what OS version do you use ?

Thanks !
Peter

Yep, 'Minimise OS' works fine on the music PC in my office, with Home Premium. (Peter, in case you're wondering, this is NOT the machine with which I had issues initially - that was the music PC in my main room. But of course we got that sorted anyway.)

The Home Premium version is W7 Vanilla (build 7600). I had updated it to SP1, but this has been reversed off, and only three KBs remain on top of a totally vanilla install.

HTH, but let me know if you need anything else.

Mani.

Home Premium here too. One thing Ive done from the beginning is to disable all internet connections and turn off antivirus before minimizing the OS.

Thanks very much Mani.

Bernd, that email is out for "hours" by now. Just that you know it (didn't see an answer yet).

What I wonder in the mean time is how it happens that your signature says Windows 7 Professional, while now it is Home Premium ?
Not that I really need the answer to that, if you're only not making a mistake (by telling me the wrong one).

Peter

PS: boleary, thank yuo too.

Peter,
was out today for the last water skiing this year, so now the winter and music listening season can begin. I have switched from Win7 Professional to a new Mini PC (absolutly passive, 0 db) with a Windows 7 Home Premium. The PC and the Win 7 installation is pretty new, only some Blu-Ray player software and some tools is installed. So far I had automatic updates activated, so it is on the latest patch level, and SP1 is already included on the installation disk. After the upgrade to XXHE 0.9z-6 the first boot into Minimize OS fails with, I think the message was: Error 01 failed to set reboot or something similar. Then I have rebooted again with success, all transperency effects in the desktop disappeared, no disc activity and fantastic sound. Rebooting to normat state with success and then I can do what I want, the OS does always come up in normal state (minimize OS button shows active). If then I do a system restore before the first XXHE 6 install I can repeat the same steps...
So if you dön't have an idea what this can be I will try to re-install Win 7 and if it is working then I will install my required software step by step and always try if minimize OS is still working. Trial and error. I also still have the Professional license on my old PC... so lots of possibilities.

Bernd

Thank you Bernd. That is clear.

Sent you another email ...

Some small problems here as well with the XX-installing and minimizing OS.... After installing XX- and, starting it for the first time, I got the screen where Autohotkey asks to be installed. Hitting the run button brings nothing, only the cancel button. But, the window dissapear if I first start Autohotkey manually from the XX-catalog and then start XX.
 
Hitting the minimize OS-button brought the same problem (with W7/W2008SP1/W2008R2 just the same). XX asks to reboot, but the window showing nircmd64.exe (can't bring the problem back, but quite sure it was this program)does not react on pressing the run button. Manually rebooting though took away the problem, and XX started OK. When again hitting the min-OS button, rebott works OK, but after the restart, I can see no difference from before, and have no clue if I'm in the min.OS state (for server 2008SP1 2008R2, for the time beeing W7 is in demo state - my fault, so can't use the min. OS-function. Need a new code...). So the question, how do I know in wich state the OS is in?

Here too, we better continue by email. But that will be tomorrow. I hope that is ok with you !

IMPORTANT

As far as could be determined, issues may arise because of applying a "wrong" sequence of things; This is prone for

a. the situation right after a new OS install;
b. a new XXHighEnd user.

This should be the sequence of *related* matters :

1. Shut Off UAC and install XX (etc.).
2. Setup your playback to whatever extension you like, but WITHOUT Minimize OS.
3. When ALL is running to your satisfaction, start using the Minimize OS functionality.

Ad 2.
What seems to happen, is that people -right after installing the OS, or right after using XX for the first time in their live, use Mimize OS. With this the OS comes in a numb state. One of the effects of this is that the Privilege changes performed by XXHighEnd at using Mixed Contiguous or Straight Contiguous memory, can not be honoured by the OS. But, this this is security stuff, the OS will mix up things herself (it is an unexpected situation) and it can't be repaired. That is, not by the current 0.9z-6 version because there's no repair in there (if I would know where to be at all).
And so, this wrong sequence of happenings is not allowed to happen, or otherwise the OS must be reinstalled (as it seems).

Ad 3.
This is mainly about using the Mixed Contiguous and Straight Contiguous Memory settings. So, use either once - *and* reboot when XX asks for that, and next allow sound to play with either of these memory settings after the reboot, and only *then* use Mimize OS for the first time.
Now all should be allright (forever).

Also see here for the solution : Minimize OS / AutoHotkey not working (http://www.phasure.com/index.php?topic=1843.0).

Peter

OK, this is totally weird. I came back home from a work trip late last night and just wanted to listen to some music. I switched the PC on and was really surprised to see my LAN still active - my last boot-up/shutdown a week or so ago was with 'Minimise OS' active. Firing up XX, I was really surprised to see the 'Minimise OS' button highlighted. But the OS was definitely not minimised.

Peter, this is with 0.9z-6-0 on my HDD... This was working absolutely fine a week ago. I was playing music with the OS minimised! The only thing I remember changing a week ago was my SFS from 240 to 400 (with SC)... but this was working fine too.

I've quickly tried 0.9z-6-1 with 0.9z-6-1b, but still can't get 'Minimise OS' to work. The computer reboots, the 'Minimise OS' button is highlighted... but the OS is definitely not minimised.

Mani.

OK, I've managed to solve my issue above by applying a fix that Peter suggested I try a few weeks ago when I first received the USB NOS1. (I'd rather not talk about this fix because it shouldn't really be necessary with the latest versions of XX.)

I think what's relevant here is that I shut down my PC with 'Minimise OS' engaged. I wonder if there's something in the OS that doesn't 'like' being in this state for a period of days/weeks rather than hours...

Mani.

When I was changing settings in my BIOS this happened to me too: though the Minimize OS button would cause a reboot the sytem would not be minimized. Changing the BIOS settings back to default didn't help. "System Restore" to a time immediately prior to when "Minimize OS" quit working fixed it. Just an FYI should yours quit working.

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