Usually the only time I feel like digging a big hole and climbing in is when I make some inappropriate remark at an important social event, or tell a rather too risqué joke during a posh dinner party. However, since I never get invited to posh dinner parties, and extremely rarely have the opportunity to attend any “cream of society” gatherings, I’ve so far avoided the need to invest in a new shovel. And, not being a polar bear, I don’t have a tendency to view large holes in the snow as suitable resting places for the winter either. In fact, even though I’m quite adept at sleeping, it turns out I’m a rather late convert to the notion of hibernation.
As we’ve probably already reached the “what on earth is he rambling on about this week” moment, perhaps I need to mention that I’m rambling on about my recent epiphany in terms of turning off the computer at the end of a working day. Maybe it’s because of the many years working with operating systems where you could quite safely just pull the plug or do the BRST (Big Red Switch Time) thing, yet be confident that the whole caboodle would happily start up again fully refreshed and ready to go the next day as soon as you applied some volts to it.
None of my old home computers, Amstrad PCWs, or DOS-based boxes ever minded an abrupt termination of electricity (except you lost whatever you forgot to save), and the Wii and other more consumer-oriented stuff we have also seems to cope with being abruptly halted. But not Windows Vista (and, I assume, Windows 7). You get those nagging reminders that you’ve been naughty, and a threat that it will spend the next four hours rummaging round your system just to see if you did any damage. I suspect this is probably just a long “wait” loop that prints random stuff on the screen, designed to teach you a lesson.
Of course, when XP was king, we were offered the chance to “Hibernate”, and sometimes even “Sleep” rather than turning the thing off. I don’t know if anyone actually made this work reliably – it never did on any of the laptops I’ve owned, and the XP-based Media Center box we had up till recently only managed it through some extra bolt-on hardware and software. Even then, I had to reboot it at least once a week to let it catch up again. So I’ve been extremely reticent about anything other than a proper “shut down” at the end of each session.
But recently I’ve noticed that colleagues seem to be able to shut the lid and briefcase their laptop, yet have it spring almost instantly into life when they open it up again; and without burning a hole in the side of the bag, as my tiny Dell XPS tried to do last time I attempted this. Aha! It turns out they are running Vista. Maybe the time it takes to actually get started from cold (even if you hadn’t been naughty last time you turned it off) was a contributing factor to their hibernation behavior…
For me, matters came to a head with the machine we use to view the signal from the IP camera that my wife uses to watch night-time wildlife (foxes, badgers, etc.) in our garden. Like most software written by companies that actually specialize in hardware, the viewer application is quirky – and that’s being kind. It won’t remember connection details, has no automation facilities, and accepts no startup parameters. The only way to get it running is to mousily fiddle with the UI controls. There aren’t even any shortcut keys or a recognizable tab order, so my usual kludge of using a program that generates key presses won’t work either.
This means that, even though I can enable auto login for Windows (it’s not part of my domain), I can’t get the **** viewer to connect automatically at startup. It was only after a lot of fiddling about that I decided to try hibernating the machine with the “login when waking from sleep” option disabled, so you only have to close the lid to turn it off, then hit the power button to get back to watching wildlife. And, amazingly (to me at least) it seems to work flawlessly. The only time it actually gets turned off is when it needs to reboot for an update patch.
Suitably impressed, I enabled Sleep mode on the new Media Center box; which runs Vista Home Premium Edition. I managed to get the screensaver I adapted some while back (see The Screensaver Ate My Memory) to run on Vista. It shows assorted photos from our collection for a specified time and then terminates, allowing the machine to go to sleep. Yet it reliably wakes up in time to record scheduled TV programs, collect guide data, and do all the other complicated stuff that Media Center seems to require (to see how many things it does, just take a look in Task Scheduler).
So, somewhat late to the party, I’m now a confirmed sleeper and hibernater. My laptop is happily slumbering away (though not in a large hole) as I write this – on another machine obviously. And the incredible thing is that it comes back to life faster than my (somewhat dated) mobile phone does. In fact, it takes the Wii box, the consumer DVD player, and the TV longer to get going than my laptop. I’ve even got my wife’s tiny Vista-based laptop set up to hibernate so she can get to her vital email inbox more quickly. Maybe we’re at last reaching “consumer-ready” status for computers? Though I’d have to say that I haven’t needed to reboot my phone three times in the last month to install updates.
And while we’re on the subject of screensavers (yes we are), I still can’t figure why I had to completely rebuild the one that worked fine on XP to make it run on Vista. The problem was that it has a series of configuration settings, which include the path to the root folder containing the pictures to display. It saves these using the VB built-in persistence mechanism, which quite happily remembers the settings each time you open the configuration window. But when Vista fires up the screensaver after the requisite period of inactivity, it suddenly forgets them all again.
At first I thought it was to do with the weird path mappings Vista uses for the Public Pictures folder, but no amount of twiddling would make it work (have you ever tried debugging a screensaver?). And I can’t find any sample code that shows how you get to it using environment variables. However, after a lot of poking about in the code, it seems that Vista may actually run the screensaver under a different account or context from the current user context (though I haven’t been able to confirm this), so the user-specific settings you make in the configuration window can’t be located. Finally, after applying my usual large-hammer-based approach to writing code (I made it store and read the settings from a simple text file in the C:\Temp folder), it works again.
At last I can sleep (and hibernate) easy…