August 30, 2016
As to Microsoft, the problem is automatic shutdown after idle time. In the power control setup frame I have everything set to "never shut down", but if I leave my computer alone for 15? minutes? and come back to it, it has auto-hibernated anyway. Oddly enough, it wasn't like that when I first switched to Win 10. I wonder if one of the auto-patches was responsible?
Under Win 7 we had "Gizmos" I think they were called. Microsoft decided eventually that they were a security problem and WIn 10 doesn't have that feature.
I used to have two of them on my desktop. One was a clock, and that was nice but not critical. The other was a couple of dials, one of which showed memory usage and one of which showed CPU loading. Memory usage is kind of a non-issue for me; this computer has 12G of RAM and I don't do anything very memory intensive. But the CPU loading dial was very useful because it was a convenient way to notice that a job had hung and gone 100% CPU intensive.
This computer is quad-core and each core is hyperthreaded, so to the OS it looks like 8 processors. If that dial stuck at 12%, it meant a job had run away.
I want that one back.
UPDATE: I went into the power control and set all the timeouts to 25 minutes and then restarted, and then changed them all back to "never" and restarted again. Just now I left the computer on while I took a nap, and it was still on when I woke up.
I think that's fixed.
Posted by: Pixy Misa at August 30, 2016 08:18 PM (PiXy!)
Posted by: RickC at August 31, 2016 03:30 PM (Ir5TZ)
Posted by: mtrigoboff at August 31, 2016 08:42 PM (eBuUt)
Posted by: Pixy Misa at August 31, 2016 11:42 PM (PiXy!)
[spoiler]your spoiler here[/spoiler]
Spoilers which are not properly tagged will be ruthlessly deleted on sight.
Also, I hate unsolicited suggestions and advice. (Even when you think you're being funny.)
23 queries taking 0.0046 seconds, 23 records returned.
Powered by Minx 1.1.6c-pink.