What Microsoft got right about power users, but not quite

Post by josteink » Wed, May 27, 2020, 9:01 PM UTC

jpalomaki wrote: post #112

josteink wrote: post #71

Earlier quoted context omitted.

> How is Windows Task Scheduler broken? Fundamentally. Try to schedule a simple script to run once an hour, while the user is logged in. No other conditions. Nothing complex. Wait an hour and wait to see one window pop open running your script. Wait one work-day. Work on your machine. Observe 10+ executions of that script, in parallel, on the mark the script was scheduled to run once. Watch this get worse every day,…

Did you check "run task as soon as possible after scheduled start is missed"? And what about "If task is already running, then the following rule applies: Do not start a new instance".

Not sure. Why should those be needed?

It says run once and it literally launches 10+ within the same 100ms.

That’s just broken.

Post by jve » Mon, Jun 01, 2020, 6:37 AM UTC

pwdisswordfish2 wrote: post #85

jve wrote: post #80

Earlier quoted context omitted.

Nonsense. Different products (from MS) are for different people. If it was true what you are telling, doubt they woild provide loads of diagnostic tools for windows, debugging tools, kernel symbols, performance tools, etc.

Before they hired/silenced him, those tools were developed by Russinovich. Comparing the most important product(s) at MS with any other MS product/project and arguing they are somehow "equal" in the eyes of MS (because press releases, marketing) is a losing game.

Kernel symbols are NOT published by Mark Russinovich. What would be the purpose to publish them other than aid debugging the kernel and making sense of what's happening under-the-hood?

Debugging stuff and analyzing performance stuff doesn't make me feel like MS would like to hide internals.

Re: What Microsoft got right about power users, but not quite

Re: What Microsoft got right about power users, but not quite