Windows 7 and hibernation

On Wed, 24 Nov 2010 19:20:59 -0800, Gene E. Bloch wrote:

On Wed, 24 Nov 2010 20:23:44 -0600, R. C. White wrote:

?Hi, Gene.

I *never* use hibernation :-)

Then you may as well delete that dormant file and stop wasting disk space.
As I recall, disabling hibernation does not erase the file; it just stops
using it. If the file does not exist when Win7 wants to hibernate, it
simply creates a new hiberfil.sys, almost as large as the installed RAM, so
that it can store the full contents of memory to be reloaded when it wakes
up from hibernation. The file has Hidden and System attributes, and is
always in the Root of the Boot Volume (typically C:\hiberfil.sys).

RC

When I'm down to where that ~2.85 GB matters to me, I'll either take
your advice or buy a new computer :-)

If (before deleting it in your reply) you read the report I posted,
you'd see that hibernation is available on this computer. I have no idea
whether that means it's enabled in hardware but not in software, or
enabled in both. If the latter, either installing Win 7 reenabled it, or
my attempt to disable it failed. It doesn't show in the start menu.

Obviously I didn't much care, although at this point it is becoming of
academic interest. Maybe.

--
R. C. White, CPA
San Marcos, TX

Microsoft Windows MVP (2002-9/30/10)
Windows Live Mail Version 2011 (Build 15.4.3502.0922) in Win7 Ultimate x64
SP1 RC


"Gene E. Bloch" wrote in message
.. .

On Wed, 24 Nov 2010 09:33:25 -0600, R. C. White wrote:

?Hi, Gene.

OTOH, I thought I had hibernation disabled. Also, I installed Win 7 a
while ago, and the date on the hiberfile is 1/11/10 (January 11, not
November 1). Maybe it was created under Vista.

The two Hidden, System files hiberfil.sys and pagefile.sys should always
be
dated today, at the time the computer was turned on and Windows was
started.
Mine both now read "11/24/10 7:04 AM".

So, perhaps you do have hibernation disabled.

Or perhaps I haven't hibernated my computer since Jan 11...which was
(possibly) when I (or the Win 7 installer?) enabled it.

I *never* use hibernation :-)

No particular reason. I just don't.

I had to do a bit of learning.

I set "hibernate" as the power button action, but it failed to
hibernate. The properties of hiberfile still showed January as the
creation date and the last access date, but the modified date was 10
hours ago (that's what it said on the general tab; the details tab was
more exact). Clearly the computer only slept.

Clever Hans - I rebooted, and this time the modified date was the time
of that reboot. The previous reboot time had been 10 hours ago, of
course.

Now when I tried to hibernate, the hiberfile was indeed modified at the
hibernation time. I tried hibernating a couple more times, but the file
did not get a new modification time.

Just for fun, I also turned hibernation off at the command prompt,
looked at powercfg -a, then turned it back on and looked again at that
status, just so I could see what it looked like...and that procedure
verified for me that when I looked yesterday, hibernation *was* on in
Windows.

Also, after turning hibernation off and on, I now get a very current
creation time for the hiberfile (all three times are identical, for the
moment).

--
Gene E. Bloch (Stumbling Bloch)

"Gene E. Bloch" wrote in message
...
I had to do a bit of learning.

I set "hibernate" as the power button action, but it failed to
hibernate. The properties of hiberfile still showed January as the
creation date and the last access date, but the modified date was 10
hours ago (that's what it said on the general tab; the details tab was
more exact). Clearly the computer only slept.

Clever Hans - I rebooted, and this time the modified date was the time
of that reboot. The previous reboot time had been 10 hours ago, of
course.

Now when I tried to hibernate, the hiberfile was indeed modified at the
hibernation time. I tried hibernating a couple more times, but the file
did not get a new modification time.

Just for fun, I also turned hibernation off at the command prompt,
looked at powercfg -a, then turned it back on and looked again at that
status, just so I could see what it looked like...and that procedure
verified for me that when I looked yesterday, hibernation *was* on in
Windows.

Also, after turning hibernation off and on, I now get a very current
creation time for the hiberfile (all three times are identical, for the
moment).

Do you have hybrid sleep turned On? That might be adding to the confusion


--

-smithdoerr

Thanks to the crew here that reported successfully using hibernation with
large memory systems (and giving a strong indication that KB888575 does NOT
apply to Windows 7) I was able to abandon testing native Windows for the
problem.

I think I've located the culprit: after building a clean test Windows
installation, installing Pointsec's full disk encryption tool (v7.4)
resulted in the hibernation option being turned off, and while turning it on
again resulted in the (re-)creation of hiberfil.sys, after a few minutes it
was turned off again...and if I try hibernation quickly enough the system
displays the message "Disk hibernation is not allowed on this system" and
the machine goes to sleep.

Perhaps the best part of this conclusion is that I'm not responsible for
Pointsec, so I can regift the Help Desk ticket to someone else for
resolution.

I probably would have found the Pointsec gotcha eventually but y'all helped
do it a bit faster. Happy Thanksgiving!

Joe

On Thu, 25 Nov 2010 10:16:44 -0500, smithdoerr wrote:

"Gene E. Bloch" wrote in message
...
I had to do a bit of learning.

I set "hibernate" as the power button action, but it failed to
hibernate. The properties of hiberfile still showed January as the
creation date and the last access date, but the modified date was 10
hours ago (that's what it said on the general tab; the details tab was
more exact). Clearly the computer only slept.

Clever Hans - I rebooted, and this time the modified date was the time
of that reboot. The previous reboot time had been 10 hours ago, of
course.

Now when I tried to hibernate, the hiberfile was indeed modified at the
hibernation time. I tried hibernating a couple more times, but the file
did not get a new modification time.

Just for fun, I also turned hibernation off at the command prompt,
looked at powercfg -a, then turned it back on and looked again at that
status, just so I could see what it looked like...and that procedure
verified for me that when I looked yesterday, hibernation *was* on in
Windows.

Also, after turning hibernation off and on, I now get a very current
creation time for the hiberfile (all three times are identical, for the
moment).

Do you have hybrid sleep turned On? That might be adding to the confusion


Indeed I do.

The disk activity lights made me think that on those occasions when the
hiberfile was not modified were sleepy times, but I didn't look at the
status of hybrid sleep until you asked :-)

This is not a laptop (although as an all-in-one, it's similar to one),
so hibernate and hybrid sleep are not really important to me. I normally
just shut down when I'm going to be away for a significant length of
time, but sometimes I sleep the computer, since I have a script that
will wake the computer from sleep in the wee hours to do a backup.
Still, I usually backup up manually: my backup programs take advantage
of Windows's shadow copying, so I can work safely while backups happen
in the background.

Anyway, since I rarely sleep[1] or hibernate the computer, I pretty much
ignore all the above, so I'm glad you and others keep asking questions
:-)

[1] That's to be read "I rarely sleep the computer". I often sleep. Just
sayin'.

--
Gene E. Bloch (Stumbling Bloch)

"Joe Morris" wrote in message ...

Thanks to the crew here that reported successfully using hibernation with
large memory systems (and giving a strong indication that KB888575 does NOT
apply to Windows 7) I was able to abandon testing native Windows for the
problem.

I think I've located the culprit: after building a clean test Windows
installation, installing Pointsec's full disk encryption tool (v7.4)
resulted in the hibernation option being turned off, and while turning it on
again resulted in the (re-)creation of hiberfil.sys, after a few minutes it
was turned off again...and if I try hibernation quickly enough the system
displays the message "Disk hibernation is not allowed on this system" and
the machine goes to sleep.

Perhaps the best part of this conclusion is that I'm not responsible for
Pointsec, so I can regift the Help Desk ticket to someone else for
resolution.

I probably would have found the Pointsec gotcha eventually but y'all helped
do it a bit faster. Happy Thanksgiving!

Joe



Thanks for the heads up Joe, always interesting to know 'why'
..
Found this page that may explain why hibernation is turned off.
http://www.itbusinessedge.com/cm/blo...tion/?cs=13646
i.e. 'in theory' so Pointsec is covering it's ass.

Best
Paul.

On Sun, 28 Nov 2010 16:31:12 +1300, "PeeCee" wrote:

Thanks for the heads up Joe, always interesting to know 'why'
.
Found this page that may explain why hibernation is turned off.
http://www.itbusinessedge.com/cm/blo...tion/?cs=13646
i.e. 'in theory' so Pointsec is covering it's ass.

Best
Paul.

Please, please, please learn to quote properly. Your follow-up was
absolutely indistinguishable from the post you were replying to.

--

Char Jackson

On Sat, 27 Nov 2010 23:25:31 -0600, Char Jackson
wrote:

On Sun, 28 Nov 2010 16:31:12 +1300, "PeeCee" wrote:

Thanks for the heads up Joe, always interesting to know 'why'
.
Found this page that may explain why hibernation is turned off.
http://www.itbusinessedge.com/cm/blo...tion/?cs=13646
i.e. 'in theory' so Pointsec is covering it's ass.

Best
Paul.

Please, please, please learn to quote properly. Your follow-up was
absolutely indistinguishable from the post you were replying to.

Poor quoting is somewhat excusable with WLM's latest version, but that
isn't the case with "PeeCee".

On Sun, 28 Nov 2010 08:01:20 -0700, Sir_George
wrote:

On Sat, 27 Nov 2010 23:25:31 -0600, Char Jackson
wrote:

On Sun, 28 Nov 2010 16:31:12 +1300, "PeeCee" wrote:

Thanks for the heads up Joe, always interesting to know 'why'
.
Found this page that may explain why hibernation is turned off.
http://www.itbusinessedge.com/cm/blo...tion/?cs=13646
i.e. 'in theory' so Pointsec is covering it's ass.

Best
Paul.

Please, please, please learn to quote properly. Your follow-up was
absolutely indistinguishable from the post you were replying to.

Poor quoting is somewhat excusable with WLM's latest version,


My view is different; I don't think it's ever excusable, regardless of
what newsreader you use. Everyone *should* use a newsreader that does
the proper things, but even if your newsreader doesn't, you can make
it do the right things with a little manual effort.

Ken

but that
isn't the case with "PeeCee".