Joseph, I am afraid it does not work like that. Removing stuff from the OS - which is what happens when shutting it off in Normal OS - is totally different from not having it so-called not active during playback. And you can see it happening by means of Minory Clean now keeping on running. It surely is not the only thing which keeps on running.

So this is a severe apples and oranges, and comparing is not possible (unless you are able to compare over boots - one with all shut off as should and no M.C. and the other way less (up till nothing) shut off with M.C. active).


:-)

Joseph, isn't there an associated service involved ? If so, you obviously must put that in the list of Services to keep.

Regards,
Peter

Thank you very much, Joseph.

Somehow I myself never got around checking this out. I really wanted to, but ... (always something else at hand)

Best regards,
Peter

Hey Roberto !

I am happy to say that I still use your config, and that I probably can't get rid of it ever. It is exactly as you say : you can now literally see people's moods and intentions and how all play together.

Your config is so different from the others, that it is amazing that it can work out in the first place. Everybody should thank you deeply for finding this !

Hug,
Peter

It runs all right !
A few remarks from what I just experienced :

1. Download and Install of the required Dot-net 3.5 goes automatically.

2. After that, re-start XXHighEnd, BUT use rightclick - Start as Administrator.

3. I also tried to start it without that (#2), and I don't know which anomalies during the start procedure were caused by that, but if you keep on working with Start as Administrator, then eventually all behaves normally.

4. Don't be confused by the possible messages about the script of AutoHotkey (see #3), but do notice that I killed AutoHotKey from memory (Exit at the green H icon) because else it would not work any more (again, see #3).

Now it keeps on starting normally (but As Administrator !). Without being activated of course, but I guess that will work normally.

For others : Please never attempt to go to MinOS with an XXHighEnd version running on W11 because it will fail by (almost) guarantee and you will probably lose the OS (can't get back to Normal OS any more). So this is ONLY for people who want to upgrade their Music Server PC (not the Audio Playing PC), *or* those who use XXHighEnd outside of MinOS for other reasons (these people exists).

Kind regards,
Peter

Ah ...
OK, wait ... I *do* have one other (new) laptop in the house with W11 on it. I can / will try that one !
(not for MinOS)

Will let you know the soonest !
Peter

Hello Tore,

On the back of my mind I have a message from someone who told that XXHighEnd did not want to start under W11 at all. But I am not sure !

All my PC's don't want to upgrade to W11 and it is high time that I start to tweak one so I can try some things myself. But it needs time ...

Can't you just try it ? I understand that at this moment that PC is worthless anyway, right ?

Kind regards,
Peter

Hi there Georg,

Thank you for this.

I think it is a bit of a secret (two actually) that (the) Alldaq was what brought me to creating the Phisolator for the NOS1a/G3; let's say that I stole the chip(-idea) in there because it did not want to work reliably. A replacement by Alldaq also failed. I now know the misery around that chip (Silanna) because half of them don't work (well).

Second secret is that if I am correctly informed, the Alldaq USB isolator is EOL (End Of Life) which is fine if you can still get one, but which would be sad if people focus on that and ask it for Christmas 2022.

Btw, wasn't it you who came up with the Intona idea ? (maybe it was someone else). I still have S/N 000001.

Kind regards !
Peter

Haha, yeah, I understand. But as you can imagine, as long as I myself don't even make something for the (2x) 3 channel speakers I have, while all anticipates those amp channels ...

The psychological bad luck obviously also is that I worked for what ? more than two years on that 8 channel NOS2, which never materialised except for having every PCB and resistor and really all in-house to start the soldering. But the project appeared too large (impossible to troubleshoot because of too many inter-dependent modules). As you may remember, this was even including 8 power amps, which ended up as gain stage in your NOS1a/G3('s).

But I surely can say HAPPY NEW YEAR to you all !!
Peter

Dear All,

The newer users of XXHighEnd among you, may expect XXHighEnd to be compatible with Windows 11. The mere longer term users, will kind of "know" that this is virtually impossible. And I myself tell you it is impossible. At least at this moment.

Many will know the enormous hoopla involved to get a decently sounding XXHighEnd version for Windows 10, with all the so many "upgrades" involved starting with Vista, then W7 (with or without service pack 1), Windows 8 which only wanted to sound OK-ish after a year of working hard (with all of us), skipping W8.1 all together, to eventually end up with something like W10-10074, that several years later ending up in the great sounding W10-14393-0.

And today, again several years later, nothing changed to that. Also, in itself nothing is wrong with that, weren't it that people start to obtain W11 automatically (at getting a new PC/laptop, or even the system performing the upgrade from W10 to W11 automatically), but that does not mean that anything still works. Actually, nothing works much any more and I can't do much about it. Sure, I could dive into XXHighEnd for another 6 months, with a high probability of nothing sounding right, like the later W10 versions already did not. And you know what ? I can't waste my time on this.

The psychological problem ? -> all sounds more than superb today so there is no need.

The need as such thus springs from people obtaining incompatible operating systems, and well, they shouldn't. Not if they want a best sounding system. For that, you should just stick to your good old 14393.0 and preserve the system for audio, as already always was the intention.

But newcomers won't grasp that automatically.

---

What needs to happen is easy to explain :
- Get yourself 14393.0 (you can get that from me if needed).
Now you can do all what XXHighEnd was made for, which includes Minimizing the OS once you obtained an Activation Code. This also includes no destroyed OS when you attempt to go to MinOS with anything newer than 14393.0.

---

N.b.: I wrote this post so people won't waste their time on installing XXHighEnd in a chanceless environment.

Best regards !
Peter

Hi Shreekant,

Yes, this is a known problem for XXHighEnd 2.11(a). 2.12 will solve that, if I ever get round to finishing it.

Do notice that about all MQA is fake(d) by now and that you better stay away from it. In 2.12 you will be able to see that it is "real" or not. With 2.11 you can't.

Kind regards,
Peter

Dear Colin,

I assume you mean the Music Server PC there;

What I have heard in another life is that this is all about sharing, also related to printing. Thus, people receiving that upgrade could not print (never mind how large the company) and all they could do for a real solution is revert the upgrade; because this sharing thing is in the same environment as sharing folders / data, it will be the same problem (though I did not run into that while working on the print problem). Of course this is a temporary solution only, unless MS solves this bug meanwhile.

Big fun is that moving to W11 solves that printing problem.
Bigger fun is that 80% (or much more ?) of PC's is not W11 compatible. Also, upgrading your Audio PC (Mach III) is out of the question.
So *if* this is the same issue indeed, I don't know what to do.

but


This could be your salvation, because this in itself is a very common message (to me). It could tell that you did not reboot the Audio PC into Normal OS, so you can start setting up the (destroyed) connection from there again. At least this definitely won't go from MinOS.
When this is fine in the first place, I would assign an explicit IP address to the Audio PC which is NOT in the range of DHCP assigned addresses by either the Music Server PC or some other DHCP means. You can check whether this worked out by means of RDC also requiring that new IP address for the connection (don't connect by name !).

Lastly, I can imagine that forcing the lot into have the Audio PC ask for the password at making the connection to the Music Server PC (for a first folder) would solve the problem. Regarding this, think of the password not being valid any more (or it suddenly requires one), nothing anticipating this while giving an "invalid" under the hood without you knowing.

https://lizardsystems.com/articles/network-command-line-utilities/
Maybe you can do something with that ?
But I would focus on Net Use; that allows for explicitly giving passwords (use on the Audio PC, working with credentials from the Music Server PC).

Hope this helps man ...
Peter

Colin, I am totally terrible. I better upload the current unfinished version than never upload anything. And if I do that, then I better had done it 6 months ago.

Peter

Hi Shreekant,

No, those numbers are totally unrelated to the channel balance.
Also, XXHighEnd does not have any means to change the balance.

The NOS1 is always checked for having the same output level at 2 decimals of a dB. Thus (at full scale) -2.071 and -2.076 dBFS are considered to be OK. There is no calibration possible at that level and the DAC chips as well as the gain stage in there, are just always fine that we could see (read : we never exchange ships or the gan stage (elements) when something is wrong. The only situation when something is wrong, is when something is not connected at all. And then the difference will be 3dB right away and we will see that.

All in other words : it is your amplifier or your ears. And don't underestimate the latter. If one of my ears is slightly off (which happens quite often in my situation) then this shows as channel imbalance. This can happen (obviously) with incorrect low frequency rendering (of my ears, that is) but even more easily with high frequency problems (and this can happen very easily, also with you).

Kind regards,
Peter

Shreekant, if I may ...
Quite some days we solved a problem for you (see your email on Oct 13).

What are you all doing that on day 1 it does not work, day 2 (10 emails further) it works, day 3 it does not work ... etc.

Not Authorized is a message you will have seen a 100 times before. This includes the more "definite" situation that the Session has expired. But this happens after many months, and yours was created newly a week ago.

If you receive this message on particular albums, then it is just so - your country is not authorized to stream the album.
If this now happens to you for all albums, then again I don't know what happened. But somehow it must be some kind of pilot error (I suggested this earlier on) because I see no further complaints. At least no strange ones.

Are ALL albums now unauthorized ? also the ones which were OK previously ? (please try)

Best regards,
Peter