Michael - well, odd then. So the least what should happen is that all normally works. This, btw, includes that "0.0007" message. This is how I arrived at WASAPI and the rest. However, not sure at all what happens when you're in Normal OS *and thus* WASAPI being active. It's a kind of inconsistent situation (well, not of course, but for what we do with XXHighEnd it is).

I hope you can get it to work normally and otherwise we may be able to work on it.
As said, I have no issues ...

Thanks a lot for this,
Peter

Hi there Colin,

Very nice question.

Best sequence would be :

1. Boot into the "Don't use" maintenance OS (or any of the others for that matter);
2. Make a copy of your current OS file (probably MyW10-14393);
3. Boot your normally used OS (14393.0) into BASE;
4. From there boot into Normal OS;
5. Apply the patch (UnRar the UPgradePatch file over your XX folder  (XXHighEnd\2.xx for RAM-OS);
6. Start XXHighEnd to see wether all still works (no playback required);
7. Boot into MinOS;
8. From there boot into RAM again.
9. Happy listening !

Ad 7:
Prior to this step, change the BIOS for ALL cores to be active (I am not sure how your Mach III was delivered, and obviously I don't know whether you changed the BIOS yourself regarding this; so goof do check.
Later, when normally booted (step you can set the number of cores in the Boot Menu (that again requires a reboot). Obviously this (Ad 7) is not part of the upgrade, but a kind of prerequisite to optimally utilise the upgrade to 2.11.

Good luck !
Peter

All right, Michael,

I tested it and it seems to me that indeed it could be for the better. Not sure yet, as at first I had the idea that things possibly became "too white". But, I used the SFS of 10.19 (as I am doing fro a long time), actually being quite sure that making it lower would even worsen that (whiteness). But it did not ! So the last couple of hours in yesterday's session I happily used 0.69 ...

Otherwise things seem not to be right with your setup or (incomplete ?) description. Like for example, that it could well be that you use WASAPI. From there, it could well be that you don't use your NOS1. And from there people could be set on the wrong foot.
Of course this is a bit pretentious, but I derive it from your announcement of running into a few problems (like not being able to use Unattended (duh !)) and more deviates.

Anyway, the most important message I may present is that nothing is wrong with anything that I can see. One quite crucial thing : I never booted into Normal OS from running Minority Clean. And there the problems could start ... Mind you, would I have run it when in the BASE of MinOS. And that I explicitly won't do. Understand ? So when doing it from RAM, then all is and remains harmless because no disk settings will be influenced (except for XXHighEnd settings when saved, but this is harmless).

On another note, and as I just tried to explain in the "RDC" topic, I would be very wary of software which changes things all over, while XXHighEnd also does that, and which could work quite "opposite" up do destructive. But as said, when done in RAM only, nothing can be destructive as such, because "destructive" as such is what I regard unrepairable.

So please be careful,
Peter

Maybe people must be aware that it is easy to see ghosts because one person tries something in a not really approved environment, others suddenly seeing the same problems caused by something else.

This is about RDC now and how there's really not any problems with it for years for me, BUT know what and what not to do (like disconnecting the RDC session yourself, and next not being able to reconnect - this always has been so and probably also will never change).
Anyway, see my settings below, which are unchanged for a countless number of years (like when 14393.0 was introduced).

Notice that the "not approved" environment regarding this could be Minority Clean, or actually any other "hacking" software that was not tested together with XXHighEnd. And mind you, just applying such software may not be problematic, but from there booting into Normal OS may be disastrous because the "reset" of things can't work because it never has been saved (when going from Normal OS to MinOS).

You can imagine that if anyone is always tweaking and booting etc., it is me. Of course, I should know what I (can) do, but there is really nothing that I am aware of of treating specially.

So just in case my related settings, as I see people doubting what to do there or what could be harmful. My response : nothing.

Peter

Kjell Narve, Yes, in the BIOS set to ALL now and let the software control the real number. And relatively easy to compare because it only requires a change of that number and a reboot (just from RAM to RAM is fine).

Btw, is *is* allowed to also set the BIOS to a lower cpu amount, but that will lower the "software" possibilities. But, it may change SQ again (I never tried with such combinations). Thus, set in BIOS the 14 native cores to e.g. 12 and then in software try 12, 10, 8 etc. (14 not available now).

Peter

Don't forget to check/uncheck this "Stop W10 Services" in Normal OS and BASE for those using RAM-OS) (and then go back to MinOS (and RAM).

All right. Can you (Joseph) or perhaps someone else with the same issue, try to UnZip (UnRar) these :

XXHighEnd-211.rar
XXHighEnd-211-UpgradePatchOver204AndBeyond.rar

No need to install for this test ! Just see whether it "unpacks" (use a Temporary folder).

These are created with the 4.20 RAR version.

N.b.: At this moment I have put these same 4.20 versions in the topic for the download(s).
You will recognize them by means of the -02 suffix.

Aha ...
Joseph, great stuff. Thanks a lot.
The link I gave is from 5.70, so there you go. Not sure, but possibly this was necessary for the current W10 I generate the "zip" on.

I will see of the older 4.20 works on this machine ...

Thanks a lot,
Peter

All - It may not even be clear that this is the Activated color of 2.11 (see below).
Demo version shows the text in light-blue as usual.

Peter

Ah, I see you solved it.
http://www.phasure.com/index.php?topic=4228.msg44589#msg44589

Joseph, someone else handed me the trick to UnRar it on another PC. Then copy over the files to the Audio PC. Not sure whether that helps you.

Also, the lot won't be able to deal with Anti-Virus software well. So that may very well bug you in this case.
Please notice that there are no viruses implanted, but Registry hacks the software applies may be seen as such.

Best regards,
Peter

Hi Arvind,

This should help :    
2.11 Upgrade Patch download appears to be damaged.

Kind regard and I hope it doesn't go too bad over at your place ...
Peter

Hi Charlie,

It is best to assume that maintaining two different activated versions is impossible these days. Ever back it was explicitly made for that, but these days the UpgradePatch procedure is - or should be used because it is so much more easy to apply (and you never lose Activation, when applied as intended).

Also please notice that these days it is quite common to maintain two separate disks (or even better, the RAM-OS Disk procedure, but never mind that). So you just boot into another OS, and in there you have an activated XXHighEnd of any form.

Kind regards,
Peter

Hi there Joseph,

I think Ramesh hints in the right direction : Use WinRar to extract the files.
N.b.: WinRar is free, as long as you don't buy it (I am serious).

Kind regards,
Peter