And then you get to boot and Windows pauses to Configure your updates -- and then you get to go to work. Right? Isn't that why you paid money for a computer? To do work? And not just update some company's software?
ZEPPELIN was being really pokey, which happens because you have no good way of telling what the Sam Hell is going on in the background tasks. I had planned to post the Quiz 6 solutions for both classes this afternoon, but as I wrote, I deferred doing anything serious while OUEST was on battery (DW) (LJ) due to the power issues at work.
I had to create two JPEGs from screenshots for the PHYS-1070 Quiz 6 and a PDF for the PHYS-2070 Quiz 6 -- all of this complicated by having to work in both Windows 7 and editing my webpages in Windows NT4 in a virtual machine. This involves having a lot of windows open: Word, Acrobat Reader DC, Paint, Notepad, VirtualBox plus HoTMetaL Pro 4.0 and Ulead PhotoImpact 3.02 in NT4.
The virtual machine crashed when I booted it and I had to try again. Just as I was starting to do my file transfers between Windows 7 and Windows NT4 sessions, I realized there was another icon on the Taskbar below.
Turns out Windows 7 wanted to reboot to finish installing the updates and was running a counter down to forcing a reboot. This in a window WHICH WAS BEHIND EVERYTHING ELSE.
Now I've dealt with this crap before. Basically, it does the eager dog/pestering child routine -- Can we reboot now? Can we reboot now? Can we reboot now? And I swear it is doing this at 85% of the total billions of clock cycles, so drags the whole system down to where, not only does it not work very well, it won't even recognize for a while that you click the Postpone button Microsoft thoughtfully provided. Which, by the way, only restarts this hidden window and its insidious countdown to reboot doom, and polling for permission to reboot NOW, it slows the system down...
So Microsoft fails at coming up with a priority pop-up window for its very own operating system.
But really, it's worse.
Why the HELL did you wait twenty minutes, to where I was knee deep in open windows and doing a bunch of complex procedures, before deciding to let me know you trying to hold it in your pants you needed to reboot so hard?
Microsoft, here's a clue. Windows is YOUR fucking operating system. I think you know how to do a reboot. If this update REALLY needed to have a reboot, you could have built it into the update before I even logged into the computer. After all these years, you should know how to reboot Windows 7.
I'm sure they'd answer that this would delay the startup and... and... and... nothing, guys. Because when I did do the Restart, after interrupting my work and closing NT4 and all the other windows, there was an excruciatingly long Configuring Updates... 28%... 29%... pause... pause... pause... 30%... This was going to take a while.
FINALLY, I got my machine back and sat through more configuring and all. No doubt this was all updates related to something stupid, like future updating to Windows 10 or something else I don't need Right Now.
Man, somedays you gotta wonder if anyone in Redmond has every actually used a computer...
UPDATE: To add insult to injury, at 25:10 EDT, when I shut down ZEPPELIN, I saw the little yellow update shield next to Shutdown and sure enough, Update 1 of 1. How much you want to bet it's supposed some they fucked up yesterday? (evil-grin)
UPDATE2: 10-15-2015 Th 09:46 EDT -- Oh, lookee at that... ZEPPELIN at home is Windows 7 Home Premium. OUEST at work is Windows 7 Enterprise edition. I knew when I shut down yesterday that it had loaded 8 Updates. Today when I booted, it Applied 34,361 updates... and then it rebooted. So somebody at Microsoft is smart enough to manage Updates better, but only for big IT customers. Screw the Home users.
Posted on Dreamwidth Crossposted on LiveJournal