The bonus was that it would also allow us to do a longer-term comparison of the retail PC option which the average user seems to prefer, with the Bleeding Edge workhorse PC alternative which, judging from our email, thousands of our readers have apparently chosen.

One of our HP purchases came with a Windows XP Pro SP2 DVD, which is what we’ve standardised on as the most reliable version of Windows. The OEM version, which we would have had to buy with our whitebox components, would have cost around $180.

The second PC shipped with a Windows Vista Business DVD. We’re not thrilled with Vista, but we gambled on being able to downgrade that to XP Pro. Since August, Microsoft has been allowing the big manufacturers to offer XP discs to their Vista Business and Vista Ultimate customers, and an HP spokesman has indicated the switch can be made for “little or no charge”.

We’ll be writing about our experience on that matter next week, but we can tell you that at the time this column was being prepared, none of the Indian gentlemen we talked to on the incredibly polite support line seemed to be aware of it. In the meantime, we will be doing our best to improve their knowledge on this, and other issues.

We don’t recommend buying PCs without an operating system CD/DVD, but a lot of people seem perfectly happy to do so. The first thing we’d do, in that case – provided the system came with Windows XP - would be to create a set-up CD using the information here.

It’s likely to prove very handy, if only for quickly removing all the pre-loaded junk on new PCs from manufacturers like HP and Dell.

Even if you do have a Windows XP installation CD, you might check out this site, which shows you how to use Bart Lagerweij’s Pre-Installed Environment (a.k.a. Bart PE) to create a live bootable CD/DVD.

It gives you a complete Win32 environment with network support, a graphical user interface (800x600) and FAT/NTFS/CDFS file system support, which is a great replacement for a boot disk if you’re burning in a system, virus scanning or rescuing files to a network share.

Our new HP environment gave us the opportunity to trial the free HP help line, when we suddenly found we couldn’t print to the LaserJet 3005D over the network. We were confronted with an error message that informed us that “the spooler subsystem app has encountered a problem and needs to close”.

Not only did it close, it seemed to take all the printer drivers in the Printers and Faxes area of the Control Panel out to lunch. We tried re-booting, then clearing the print queue for each printer, but every time we tried to print, the error message popped up, and all the print drivers disappeared again. Worse, the problem also struck the other PCs networked to the printer.

We did several Google searches and discovered that while several users had experienced the problem, none of the solutions in the Microsoft Knowledgebase and on other public forums seemed to help. Their advice to edit the Registry and/or reinstall the drivers – on each PC – didn’t appeal to us.

We rang the HP help line, and talked to an extremely helpful gentleman in Bangalore, called Mark. (It’s a good idea, in our experience, to take a note of the name of these people when you call, because you might need to refer to them when you find yourself being transferred, or ask to escalate the call. Bleeding Edge, by the way, is never shy about escalating the call.)

Unfortunately, Mark seemed to have been furnished with a list of possible solutions that took us through entering services.msc in the Start/Run dialogue box, stopping the print spooler then restarting it, then proceeded to removing the printer driver, downloading another copy, and reinstalling it, and wasn’t prepared to depart from it.

While we decided to humour Mark and go through the procedure on one PC, we were not about to replicate it throughout the network, particularly given our discovery that the uninstall option on the HP Programs menu doesn’t remove all the printer files, and you have to hunt around your drive to find other things to zap. If you’re reading this, HP, you need to do a little more work on your uninstall procedure.

Instead, we did something we should have done in the first place. We headed to the HP users forum and rummaged around the postings, which is something the HP tech support department should probably be doing too. We struck paydirt in one of the hints.

It alerted us to the possibility that what we were dealing with was more of a network error than a spooler issue.
We’d already used the printer’s console to print out a configuration page, which gave us its network address. We right-clicked on the LaserJet’s icon in the Printers and Fax area (Start/Printers and Faxes) and selected the Ports tab under Properties. While the port did have a check mark, we discovered that the DHCP server had assigned it a different address from the one it had been allocated at installation, and although the option “Always print to this device even if its IP address changes” was ticked, it clearly hadn’t worked.

We changed the IP address, and we again had a working network printer. Maybe Bleeding Edge could learn to live with these brands, after all.