For a desktop/server, uptime/stability is definitely more useful. You can use ACPI etc to send the machine to sleep (there are various states either saving to RAM i.e. S3/standby or to the HDD i.e. S4/hibernate), and that way you're 'up & running' ASAP without incurring an adverse electricity bill! MS's XP goals were 30sec boot, 20secs hibernate, 5secs standby. They are trying to reduce it further in Vista & by using flash-based SSD/HDD combination devices .. but the latter was also meant for mobiles to reduce power consumption of mechanical rotating HDDs.
It's also a bit misleading in the sense that, in my case, with minimal params, the BIOS checks take about 5secs (mostly on the RAM, netboot, etc), XP takes another 10secs to get to the login screen, and then it takes a further 5-10secs to actual get to a usable desktop with around 30 processes running in the background! Basically, things are still loading when XP shows users the login screen! Not that important though.
For mobiles, though, it is important. MS focused on fast booting for Win XP, so I've never seen a machine take longer than 40secs once this came out (obviously I've not tried installing it on a 286 or something!).
1. disable things that you don't need in the BIOS (e.g. some disk controllers take an age to check through each ID).
2. You should minimise the services that start on bootup .. some of the ones I've seen on friends machines were only used rarely so I changed these to manual startup (though often you'd need admin rights to restart those AFAIK).
3. defrag, use bootviz (I agree with the earlier poster .. it's very very useful to help you focus on the slowest problem areas .. e.g. drivers that take a long time to load, dumb services that retry several times to find something on the network that's no longer there, etc). A person on another forum notices a Nero service added about 15secs to their boot time!!
4. upgrade the RAM, and/or HDD. The former is obvious, it reduces the need to access the HDD all the time. For the latter, there are two issues here: access times (the latency time for the head to get around to the correct position to get the data) and bandwidth (the amount of data per sec the interface can transfer). To reduce the former you need faster rotation speeds or more RAM/cache/etc. To increase the latter you need more modern interfaces, and a RAID array to max out that interface. SATA/NCQ & SCSI drives have intelligent queues to handle multiple requests, so that's another option. Another thing that's sometimes discusses are the various SSDs that are available at horrendous costs! They're not that useful, as Anand found out .. the BIOS ends up being the main factor in the boot time. Now, you could install a thin BIOS (if your board was supported by it), but then you'd be limited in which OS's you could run (2k not XP) .. still you could move to an embedded Linux and have a much faster boot up .. but I presume you want Windows XP & to be able to run normal apps like games, so this option is probably out!!
http://www.anandtech.com/printarticle.aspx?i=2480 is the Anand's review of the Gigabyte SSD. Notice the single SATA Raptor booted Windows in 14s, and the (admittedly limited) 4GB SSD did it in 9s. It takes power from the PCI, data is over a SATA connector.
Personally I don't see the point. Ideally, I'd much rather just avoid booting up altogether (by making sure I keep my main OS stable, secure etc), and then use that RAM in their native sockets (unless I had some old RAM that wouldn't go in the board & wouldn't sell for much!) as a RAM drive to use them at full speed (rather than SATA speeds) for caching apps or large files so they'd load quicker & would be faster to work with. Linux has some really good RAM caching algorithms built in ... I'm not sure about Windows but there are tons of soft-ramdrive vendors' ads that's I've seen.
Comment/Reply (w/o sign-up)