2.06a Unattended scaling problem

[PeterSt]

- W10 scaling level = 250%

That is your problem, in combination with the 3200 resolution.

For your mind, try to avoid any "but 2.05 was fine !" because even if it was, I think it can't work OK in the first place.

XXHighEnd is set to a Scaling factor of 1.7, which is about smaller than normal visiblilty on a slightly smaller physical screen (assumed for the laptop). Combine that with the 3200 resulotin and you're nowhere (and it just shows as you showed and what I promised (with the 4x smaller button example)).

Your real problem is that you try to work with a 3200 resolution which is (allow me) foolish, because everything will be way too small and only specialized software will utilize it properly (like video playback). So your solution : set the DPI higher (the 250%) and think all is fine. But it is not at all.
Set to 100%, set to 1920 (or even smaller), set XXHighEnd to whatever you like (around 2.00 I'd say) and you will see that all is fine.
And oh, do notice that with 1920 any laptop is already unmanageble (with the scaling at 100% which is the only setting which by guarantee will show all right). With an 21" screen it starts to work out ...

Now I know you are ignorant as hell and don't believe a thing I am saying, so :

But closing and then re-starting XX brings it back to the 'correct' size. So, whatever re-scaling mechanism is working on the restart doesn't seem to be working when coming back from Unattended. Does this make sense?

The only thing I can imagine at this moment is that whatever Windows needs to do for its scaling (the 250%) is not active with certain services shut down. Also good to blame 2.06(a) for it now, right ?
But ...
So what you can try is make as many services NOT to shut down while being in Minimized and see whether that helps. Just to see.

Peter

[PeterSt]

PS:
It is a bit hard to check, but it looks like 14393.0 not being able to scale at all, once in Minimized OS.

PPS: Maybe again try to reason out the difference between Office and Main. I ask this because I removed some ever occurring message (I think it is the one starting with "This message should not occur") because 14388 came up with it by default and this is related to the Sound Device initialisation. So if we now think about DAC's being different somewhere, it can just as well be this. Furthermore the showing of the message implied some early "Windows initialisation" (too difficult to explain) which just as well may have caused the services required here to start (early).

Regarding this all, there could be a difference between Alt-X and Ctrl-Alt-X ... (just try it out).

Peter

[manisandher]

Your real problem is that you try to work with a 3200 resolution which is (allow me) foolish, because everything will be way too small and only specialized software will utilize it properly (like video playback). So your solution : set the DPI higher (the 250%) and think all is fine.

I bought my laptop earlier this year. I never set anything - the screen resolution and DPI were factory set to 3200x1800 and 250% respectively. Everything has worked fine until now, so I never bothered to change anything. But now that there is a problem, of course I'm happy to try whatever.

I've just changed the settings on my laptop to 1920x1080 and 100%. The XX window still comes up smaller after Unattended than before, but it looks 75% or so of the size now (rather than 40%, as before). So the issue remains when I use my laptop...

I can live with this, but I'm assuming there will be more and more people buying new devices (laptops, tablets, etc) with screens factory set to very high resolutions, so perhaps a solution for this issue is still worth pursuing.

Mani.

[PeterSt]

Now we're talking ...

So I think that now you are proving that something is wrong.
But what.
With the Windows scaling at 100% this is now out of the (XXHighEnd) equation.



How can we prove it is something with a Service required to run ?
I think it can even be that W8 is fine with it. Easy to check ? (no is fine !)

[manisandher]

Easy to check ? (no is fine !)

Haha... Maybe when have more time... (I thought I'd try 14393 yesterday and didn't anticipate needing to put the video card back in because the IP address had changed. It all starts taking way more time than you initially think it will.)

Mani.

PS. 14393 is sounding very nice!