perris said:
that's a good discription henyman, but to be perfect, the system won't boot from hibernate at all.
it'll resume
What does boot mean though?
If boot means starting the OS cold, then yes, it does not boot, but if boot means have bios go through it's post, and then having whatever OS is installed dump it's stuff into ram, and cache and start all it's crap, then yes it is a boot.
Windows has to dump the hibernate file back into memory, then synchronise all the calls, check all the states for all the open files/programs.
perris said:
interesting side benefit here you just reminded me of ming;
hibernate time counts toward uptime!
Yeah, that is an unfortunate side effect, people say they have left their PC on 24/7 and have a 30 day uptime, can in effect just Hibernate and still try to prove it with their uptime.
--
As for 24/7 or hibernate/shutdown + bootup.
I have personal experience that hardware which is on 24/7 has less problems when there finally is a shutdown/reboot. I have had several HD's die while powering up. PSU burnouts.
But then again, energy makes the difference. In my house we have so many devices that always stay on, that it is moot point of one more joins the club. We do have our HP printers set to auto shutoff past a certain point, and we make the point of turning the TV, DVD player, cable box, and other devices off during the week, when they are not used anyways.
But PC's, never.
Dublex said:
I think users should hibernate as well.. you would get less tech calls that way
Indeed, no more programs that can **** up at boot
.