Slashdot Mirror
Microsoft Patents OS Shutdown
An anonymous reader writes "You would think that shutting down software could be fairly simple from an end user's view. If I ask you to shut it down, would you mind shutting it actually down, please? Well, it's a bit more complicated than that, because you need to ask the user if they really want to shut down and if unsaved documents should be saved. And that warrants a patent that also covers Mac OS X. Next time you shut down Windows, remember how complicated it is for Windows to shut down. Perhaps that is the reason why this procedure can take minutes in some cases."
One has to wonder if they are also trying to patent the inadvertent "BSOD" shutdowns. They seem much more complex. ;-)
Or the process where you get halfway through the shutdown, and then it stops for no apparent reason and you have to go and order the shutdown again to get it to finish shutting down.
I read the internet for the articles.
Here's the USPTO link. The abstract:
A user interface and scheme is provided for facilitating shutting down an operating system. Aspects include the operating system receiving a command to initiate shut down, and automatically terminating graphical user interface (GUI) applications that delay shut down which do not have top level windows. Also, aspects provide a user, through a graphical user interface, the ability to automatically terminate all running applications in response to determining that a running GUI application has a top level window.
Read the EFF's Fair Use FAQ
Shutting down Windows, evacuating ones bowels.
Potayto potahto.
No folly is more costly than the folly of intolerant idealism. - Winston Churchill
Yes, but an Apple fanboy takes a lot longer to shut up.
I guess I should patent MY shutdown technique - goes back way before then. Make sure nothing important is going on (like a write operation), and just cut the power.
It still works great on modern OSes with a journaling file system - and the best part is that your whole desktop, including open apps and files, is restored next time you log in, and you only lose 2-5 seconds on reboot (which is less than the time you lose doing a clean shutdown), and you don't have to answer 3-4 dialogs asking if you want to save your session, etc.
Do that every time, and over the course of the year, you've saved 30 seconds x 250 days, oe 125 minutes - that's 2 HOURS of electricity. Be green - pull the plug :-)
Seriously, most of the time I shut down properly, but if I hear thunder close by, I just cut the power unless it's a laptop. Lightning doesn't have to be close enough to hear to induce surges in power lines, so I figure if I can hear it, it's already too close. I haven't lost any data doing this, but I *have* had to replace one cpu because of a power surge (and that was in the bad old days when you had to hand-solder them to the board).
Pull the plug. A *real* OS can handle it.
When can I, um, patent shutting down the USPTO?
No, no, you have it wrong. Please patent keeping the Patent Authorities operational and then refuse to licencense that to anybody.
I can't figure out which patent or application the article is referring to. This patent issued to Microsoft last year and covers OS shutdown methods, so I think it's the right one. The first claim is this:
Basically it covers delaying shutdown while an application wraps something up and informing the user that this is happening via a GUI. The more detailed claims cover the circumstances under which this might occur (e.g., a negative response from the application, no response from the application, etc).
This patent does not cover what Windows XP or OS X do in this circumstance. In fact, the behaviors of XP and OS X are explicitly mentioned in the specification, and the patent is meant to cover an improved method for handling the situation.
I worked at Microsoft for the Windows 95 launch, where I provided Tier-1 support for BOOP (Bill and the Office of the President, i.e. CEO tradeshow tech support). I do recall that Bill specifically called out the 'shutdown' function on Windows 95 as an error. He didn't like it, he hated the idea of waiting for the OS to shutdown, and wanted simply to be able to push the power button to immediately turn the system off, like a DOS PC.
He may or may not have understood the concept of in-memory caches and unsaved user work, but it didn't much matter to him.
It's yet another case of Windows taking a "don't tell the user anything, it might scare them" approach.
Are you sure?
Set your phasers on "funky"!
A: The USPTO looked in the mirror and found prior art!
Hope is the currency of fools
Except for a couple things:
A) You assume someone gives a shit about your sig, and more importantly,
B) You got the term wrong. The correct term is "It is now safe to turn off your computer".
You have had the wrong term in your sig for 10 years. If that isn't an Epic Fucking Fail I don't know what is.
Even better was the time I told my laptop to shut down because I was low on battery. I came back 5 minutes later to find it hadn't shut down because a Windows dialog had popped up saying I should shut down because I was low on battery (true story).
My webcomic
> That's because the slashdot summary and the article are sensationalized. They aren't patenting "shutting down."
>
Um
What the hell else should I think they are trying to patent ?
"sudo dd if=/dev/urandom of=/dev/kmem bs=8192"
is a lot more fun than just /sbin/halt
--Joe
Shutting down windows is like a bad breakup. It's a long and drawn-out process, that you wish you could just walk away from, but there's always some unnecessary complication that leaves you wondering why you settled for this in the first place and if you will have the willpower to avoid coming back tomorrow.
Not so fast! I have a patent on that.
I am literally 3000 tokens away from the chaotic crossbow --Stephen
As a naive user, why should I have to ask my computer for permission to shut down?
Because if you agree to let yourself be inconvenienced slightly around the edges, we (the systems designers) can make the big part in the middle much more convenient.
Ever encountered thrashing (excessive swap file reads/writes)? If you want to be able to turn the system off on moment's notice, you're asking for all data to be written to disk at all times. That is, instead of having RAM between CPU and disk, the CPU should just write straight to disk. That is, it should write to disk all the time.
You're asking for thrashing to be the way computers operate by default. You don't want that. We are in fact so certain you don't want it that we are arrogant enough to make the edge-inconvenient way the default without asking you.
Or rather, given what most people do with their computers, that's the best way for them to work. If you're really insistent, you're welcome to run on a diskless workstation or off a Linux LiveCD, or mount all your file systems read only.
Let's see, your TV doesn't store much data and can afford to sync every time anything changes; neither does your car. Your VCR, I would assume, can sync rather rapidly. Also, you don't install new applications on any of those, and you don't complain when your VCR player can't play the new "DVD" format. I don't know about your cell phone, but my 5 year old dumbphone has a cute shutdown animation to cover up the fact that it's a computer with all its inherent complexity. And my N900 which runs Linux; well, go figure...
In short: computer behave differently because they have to meet different demands. If you want something other than what computers give you, well, all the more power to you I guess. It might be expensive to build if it's only you who wants it, though.