• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Delete hiberfill.sys on boot without disabling Hibernation?

CZroe

Lifer
I use a netbook with 1.5GB of RAM and a paltry 8GB SSD, so dedicating 1.5GB of that to a persistent hibernation file is ludicrous.

That said, if I *really* need hibernation (and I sometimes do), I don't want to have to waste time enabling the option. Basically, if I have 1.5GB of free space, I should be able to hibernate and have it make the file then regardless of fragmentation or whatever the persistent file was meant to minimize. If I needed the space for something temporarily, I will simply lose the ability to hibernate until I copy some stuff off to another drive/PC.

Any way to accomplish this without the tedious steps of manually disabling, deleting, and enabling when needed? Any way to automate the process of enabling and activating it, like a "Hibernate Now" shortcut that enables Hibernate AND puts the system into Hibernation?
 
Negative. The file is there to make sure that you have space FOR hibernation. Why not disable hibernation and use sleep mode?
 
Because having it sleep when you are out of juice and nowhere near an outlet assures that you will lose your work. They are not interchangeable functions. If I have free space and I want (or NEED) to use it, it shouldn't be a 12-step process while my battery ticks away... even more if I don't have the space and need to make room.

I know that the file is there to make sure that there is room for hibernation, so how about just not letting me hibernate when there ISN'T room and letting me when there is?! That's the only appropriate behavior for a netbook with such limited capacity, or any other system with such limitations.

That'd be a whole lot better than having to waste precious battery life to check on the setting, delete files, check again, delete more, check again, uninstall something, check again, compress some stuff, check again, move some stuff to SD/USB, check again, enable, then hibernate. Hell, the vast majority of the 1.5GB of RAM isn't even in use, so a better (albeit, slower) implementation could work much better by only using the space needed. I mean, I had to upgrade the 512MB of soldered-on memory because hitting the cache file on such a slow machine was unacceptable (the 8GB SSD is known as being the most painfully slow model on the market). Why punish me more for that? I essentially lose my ability to hibernate because I had to upgrade the memory. Just like Microsoft's perpetually annoying taskbar auto-hide feature, it's poorly implemented.

I don't think it would be impossible to make a utility that simply deletes it on boot, disables hibernate while making it still appear to be available, and enables/allows the OS to recreate it if/when needed, so I'd like to know if something similar exists. Hell, just a utility to enable it with a keystroke and report if successful would be enough.
 
I know that the file is there to make sure that there is room for hibernation, so how about just not letting me hibernate when there ISN'T room and letting me when there is?!

Because in your "I'm out of juice and need to hibernate now" scenario that's even worse since you'll be scrambling to free up space just so that you can hibernate.

Hell, the vast majority of the 1.5GB of RAM isn't even in use, so a better (albeit, slower) implementation could work much better by only using the space needed.

Except that writing to a hibernation file is a very difficult process since most of the system is halted and you can't risk changing just about anything in memory at that point. Linux has gone through at least 3 different implementations of hibernation trying to find the best tradeoff of features and safety.

Why punish me more for that? I essentially lose my ability to hibernate because I had to upgrade the memory. Just like Microsoft's perpetually annoying taskbar auto-hide feature, it's poorly implemented.

So implement something better...

I don't think it would be impossible to make a utility that simply deletes it on boot, disables hibernate while making it still appear to be available, and enables/allows the OS to recreate it if/when needed, so I'd like to know if something similar exists.

Not for Windows. I can imagine something like that not being terribly difficult on Linux because it generally suspends to swap and you can add/remove swap files at runtime. But you'd still be in the position of clearing up free space at a bad moment when you're low on battery an go to hibernate only to see it fail because you don't have enough free space.
 
Back
Top