XXHighEnd

Peter,

In unattended mode, with "Don't do anything with Coverart" checked, 2.04 always left me with a completely black screen during playback. However, after applying the 2.07 patch, in unattended mode the desktop icons and wallpaper all disappear as before, but the blue background color still remains.

Since I am using W10 Build 10074, there is no provision for turning the background black by itself and I find the background color to be distracting. No settings were changed from 2.04. Is there something that I'm missing? I only play .wav files ripped from CD's.

Thanks in advance!
Joseph

Hi Joseph,

a. Did you apply the 2.07 patch directly to 2.04 ?

b. If you'd use Coverart, everything is fine ? (black background with Coverart or the large X logo when not present)

I don't recognize this, but I always use Coverart ...

Regards,
Peter

Hi, Peter,

First I applied the 2.06 upgrade patch over 2.04. I tested it to make sure the license still worked and played some music. Then I applied the 2.07 upgrade patch to 2.06, all in the same folder.


Yes, that worked OK.

I spent more time experimenting today and was able to get the background to disappear as usual with the OS minimized in unattended mode. However, I am not sure if I cured the problem or if the program corrected itself.

First I only checked "Stop Desktop Services" and allowed all of the remaining services to function as usual. Now, in unattended play, the background disappeared along with the wallpaper and icons.

When the GUI came back, I stopped all of the other services and voilà, with the OS minimized, everything worked as before under 2.04 -- the desktop, icons, and background all disappeared during play. My only conclusion is that the PC had forgotten how to perform a complete shutdown of desktop services and had to be shown how to do it separately from the other services. This does not really make sense to me, but at least the problem is solved.

One unrelated issue with 2.07 remains, but I will post that separately in a few days.

Thanks for your support!
Joseph

Joseph,

Try to envision that all works relative; So there is a state, and that state needs to change relative to how it currently is. But, the change itself anticipates that. Example of how it will not work : make a new kind of change with MinOS active and when now going to Normal OS, something goes wrong because normal OS is the base of it all. Read : such changes should be made in (applied to) Normal OS and only then all will be consistent and will be consistently working after that (going back and forth to MinOS).

I am sure this is totally unclear, but to me it would tell that what you experienced can very well be "normal" (and includes a bit of pilot error, so to speak).

Regards,
Peter

Hi, Peter,

I think I understand what you are saying.

I usually make adjustments in MaxOS and then go to MinOS, so I am still not sure how the problem was solved.

Thank you, again, for your attention. BTW, the SQ in 2.07 is outstanding! It is amazing that you can keep making improvements like this.

Cheers,
Joseph

Thank you Joseph,
Peter