As I blogged about last February, I often carry a second computer, an ASUS EEE PC 701 , so I can work while I wait for my Windows laptop to boot up. Some enterprising folks at Splashtop have taken this concept one step further and embedded a compact version of Linux with applications in the BIOS, so that within 30 seconds of pushing the power button on your computer you can be browsing the web, making a call using Skype or viewing photos or videos. But this requires buying a mchine with an enhanced BIOS to allow you to do this.
Dell has taken this one step further with something called Latitude On . Latitude On is a fully dedicated subsystem with its own low voltage processor, WiFi and WAN, operating system, and essential applications like email (Exchange and POP), view attachments, and internet. It is believed that the processor is ARM and Dell says the OS is an embedded Linux (not Splashtop). Dell laptop computers with Latitude On run Linux within seconds of pushing the dedicated Latitude On button. If you just use the ARM/Linux subsystem, Dell says you can expect days of battery life, not just hours which is what you can expect if you boot Intel/Windows. Of course if you need to do some serious work or play games, you can always boot Windows which will run using an Intel dual core processor.
Phoenix's HyperSpace is another alternative that boots Linux almost immediately allowing you to do email, browse the web, and altogether 80% of what you spend most of your time doing. You can download and install Hyperspace, because it is does not require a separate processor or a special BIOS like Latitude On or Splashtop. One of the nice things about Hyperspace is that on some types of hardware you can run Hyperspace and Windows in parallel. I tried to download and install it, but it turns out that the types of machine that it will run on are very restrictive. When I tried it there was a relatively short list of machines that it supported, and my Thinkpad X60 was not on the list.
Now there is another alternative called Presto from Xandros, that appears to run on any Windows machine. I downloaded Presto - it's about half a GB - and when decompressed requires several GBs. It installs fairly quickly, and when you reboot you find tthat you now have two alternatives, you can boot Windows or you can boot Presto. If you choose Presto, it comes up in about 30 seconds, and out of the box gives you a Firefox browser, Open Office, Skype, a PDF Reader, and a few other standard applications. You have access to an on-line CNR site where you can choose to install Evolution II, Thunderbird, or another email client. To me the most important feature of Presto is that you have access to all of your Windows data files, so you really can do serious work. The disadvantage is that it does not run in parallel, so if you need Windows, you have to boot it and you can't use Presto while Windows is booting, like you can with the other alternatives. Presto shuts down in 5 seconds, so you really can turn your machine on and off frequently, because you don't have the long boot up and shut down cycles of Windows.
Of course there is the other alternative, get a second computer like an ASUS EEE running Linux or (soon) the AlwaysInnovating Touchbook with an ARM processor I blogged about recently.
Does it really take your Windows machine THAT long to boot? If so, you've got issues that you can't really blame on Microsoft. The common conception that Windows takes overlong to boot is largely Urban Folklore. A clean install of Vista (admittedly MS's slowest-starting OS) completely finishes all boot processes in less than 2 minutes. Do you REALLY need to gain 90 seconds on that? Do you actually sit there, stare at your laptop and start chanting "Come on, come on" after the first 30 seconds?
My guess would be no. That your laptop takes considerably longer than 2 minutes to boot. While this is often the case, it is rarely Microsoft's fault. If your computer is taking more than a couple of minutes to boot (completely), then you should probably be taking a close look at what, exactly, is running on your system at startup. Chances are, there's a non-MS culprit (or more than one) to blame.
Also, it doesn't hurt to take the time to carry out some system cleaning/maintenance tasks once in a while. Keeping the system clean helps keep your boot times shorter, as well as improving performance in general.
Posted by: Terry | March 19, 2009 at 10:49 AM
Terry, Thanks for the comment. Anyone who works in a large corporate environment spends a lot of time watching Windows "boot". A lot of it is not directly attributable to Microsoft but is part of the platform and cannot be avoided including security checks, virus scans, backups, etc, that can leave you with a machine that is unusable for a significant period of time. If I have a presentation or something for which I need to use my Windows machine, I have to include "boot time" as part of my preparation so that I am ready in time.
Geoff
Posted by: Geoff | March 19, 2009 at 12:21 PM
'Anyone who works in a large corporate environment spends a lot of time watching Windows "boot".'
Agreed. However (and I'm really trying not to be a pain here), how many people working in that environment are able to freely install third-party apps (like Splashtop, Hyperspace or Presto) in their company laptop? Besides, if you're running into these problems in a corporate environment, it's not your time that's being wasted, anyway. And - realistically - we're only talking about a few minutes here (unless you're starting up a cold server stack or somesuch). The slowest boot time in the world can't possibly add up to more than five minutes (unless there's something SERIOUSLY wrong with the computer in question).
Posted by: Terry | March 19, 2009 at 01:35 PM