OK Dennis, thank you.
In the end of the afternoon I plan to have a 2.08f which theoretically also won't nag about the Group Policy thing. But then in the way I like it.

Peter

Hi Dennis,


Haha, yes. But you had this from your previous attempt with 2.07.
Not that I can follow really what happened now and why it now works fine.


Well, it should. But only if that USB stick is still in ... 

OK, good. Problem solved.

Have fun now !
Peter

PS: But still waiting on that Group Policy thing, because at this moment (2.08e) something is On which can be Off.

So the 2.08e is for testing what happens with this Group Policy Message. I hope you can let me know when you are confident it will stay away, or is still there.

Peter

I suppose this works differently from what you expect;

The check for the LAN goes by means of checking whether the last file played (actually the track selected in the Playlist Area) can still be found. If not, the LAN is reported not to be there ...


Sadly this is not a build-in feature and merely a kind of bug. I mean, when you don't have the LAN you also won't have an RDC connection, right ? Well, sort of, because when you Keep the LAN "not persistent" it shuts off when playback starts but RDC activity remains.So the bug in this case comprises of shutting off the LAN (in normal OS arranged for) while using RDC overrules that partly (as it seems).
Btw, the sheer fact that you try this (for its working) could imply some kind of pilot error I don't think of.

These should be the crucial settings :
Be in Normal OS
Load a track (or more) in the Playlist Area; select it.
Stop Desktop
Stop Remaining
Stop W10 (just because I use it like that myself)
Use Remote Desktop.
Keep LAN, Not Persist (the latter means it shuts off during playback, the former means it will not be cut off right from the start (the boot).
Boot into MinOS.

No need to test or report about Attended Playback. Only Unattended.

Can you now try this :
Go back to Normal OS again.
Make OSIsW10.tst active (you will understand what I mean) because it should imply the same siuation as with 2.07, regarding this.
Same settings as above.
Go to MinOS.

Now it works ?

I suppose it is totally obvious, but I don't see what "WS" services are ?

Dennis, a quick note : please do not edit posts like you did with this one, because I am waiting for your response (after your initial "working on it"), while you edited it in in the other post. I (or anyone) just won't see that (unless by accident).

Peter

Thank you for that extra check, Nick.

Peter

Hi there Joel,

First of all it is quite crucial that you use 2.08d (or beyond when there) because the ZIP packing of the previous 2.08 versions cause something very similar to what you describe (2.08d is RAR).

Also see this topic : 2.08d on WS2016 first impressions IOW you should be able to get further than right now. So if all else seems right to you, I’d indeed deactivate Fidelizer for now/test.

Kind regards,
Peter

Thank you for this, Charlie. Great stuff.

Maybe this is part of the explanation why our ever $1 cable of 1m80 was best for most, and why my own attempt of the 70cm Supra didn't hold for even 3 minutes against that $1.

For the other cables we sold (many 100s of them) I still don't have any consensus. They all stay out and nobody complains. For the Lush the story is no different. Most go at 70cm and 100cm, then maybe 5% is 150cm (and the few at 200cm and 300cm just can't weigh in anyway).
I myself use 100cm and never tried another.

With the "knowledge" of today, I am pretty sure that the length will matter, but how I don't know (or anyway can't predict).

Maybe it is also good to know that something like a 100x 30cm Clairixa is out (the so-called "Short Clairixa" for Intona) and that here too there isn't a single feedback about a poor result. But then people will always use it with the Intona (like I did) and can't tell the difference (and officially it is too short to interconnect a PC and a DAC).

Maybe we should start focusing on this and have a great finding or whatever.

Great thanks, Charlie !
Peter

For this one, see below 2.08e (paste over 2.08d would be best for my own interpretation of matters).

This is only a test and the question to you whether you are still "able" to see this "waiting for" message. If not and you are persistent in being sure it has gone, there will be a next step in this one.

I also eliminated a check for 14393.xxx (14400.xxx actually) so for anyone who has a newer build than that (not you Dennis, unless very recently) a certain approach is now done for those newer builds just the same (resulting in something which was necessary from of 14388).

Peter

In Settings, Services and OSD section, there's a Stop W10 Services button. Do you have that active (red) ? If Yes, can you quickly check what happens with your RDC connection if you deactivate that ? Please apply the deactivation in Normal OS and then boot into MinOS.

If you are not there at this moment to try it, just let me know that, so I will not be waiting for your answer (and continue with something else first).

Thanks,
Peter

I think I know what is going on in there - some specific check for a combination of the OS Name (which is W10 for the desktop version and WS2016 for the server version), which check(s) must be performed for WS2016 as well. For 2.07 this would have worked out OK because there the server version was just denoted W10 ...

So let me try to find all the code checking for this ...

Peter

Hi Robert,

Is this 16/44.1 or 24/xxx ?

Is the interval of the tick related to the SFS ? -> it should. But you need to try it. So if you can easily perceive it and double the SFS, you should perceive it half of the time from the previous setting.


Windows 10 is somehow poor in something "first". Just think of the long time it takes for 14393.0 before the "Services Stop" screen disappears and you know what I mean; only happens once for the day's session (even when the PC is on 24/7).
So what happens if you start that first album, let it play for a second, stop, and restart playing it ?

Peter

Hi David,

I recall I had this one time maybe 2 months ago. But then it happens maybe once a year to begin with.

I am positive this is because you do something in advance of which you can see or feel it ain't right. Example : Press Stop - change your mind and press Play again within half of a second. This is only an example.

So carefully think what you might have done in advance of this, and tell me so I can look into it.
It should be coincidence but thus may depend on your "workflow". Like you said it yourself from previous times : change the volume fast. I know that if we do this today, sound will stop. Or worse ... O I taught mysef to not change the volume fast. But then this is not necessary any more.

Notice that with Alt-s (see XXOSK.exe and the S on it) the music stops instantly. So always have that on screen (you should anyway), and now you can stop the possible noise as fast as you are yourself.

If you use a quite random SFS number (and not a calculated one for your own reasons) then you can add/subtract 0.1 to.from it. This does matter, as all is relatively fragile inside for things coming together which should not. So if you just changed something regarding (all) these settings, it easily can be bad luck on the combination.

I hope I am clear enough on wanting to solve this, instead of you being able to deal with this ... But it needs the example !

Best regards,
Peter

Dennis,

With always the anticipation on a fresh OS install ...

Is this in Minimized OS as well ?
I ask, because Windows 10 has a famous kind of bug of not being able to sustain the RDC connection in Normal OS while it is fine in Minimized OS.

The Explorer error is also know, but actually from Minimzed OS and shutting down / rebooting (and an ealier W10 Build than today's).


That happening in Attended mode would be new to me (or maybe I just never tried - if only this happens in Normal OS and not in Minimized OS).

Regards,
Peter