Before I became a technology journalist I worked in high performance computing for many years. During that time I got to work with some of the most powerful and most expensive hardware on the planet â€“ Cray, Silicon Graphics, Amdahl, DEC and Convex, just to drop a few names. Part of my job back then was maintaining hardware, which included upgrading the operating systems when required. However, I tended to be pretty pragmatic as far as upgrades went, and if I didnâ€™t feel that I needed to upgrade an OS, I simply didnâ€™t do it.
You see Iâ€™m a firm believer in the old adage â€œIf it ainâ€™t broke, donâ€™t fix itâ€. Having spent years dealing with the problems that an OS upgrade would inevitably cause, I took the decision to only upgrade any OS or firmware if I absolutely had to â€“ thus limiting the potential damage, downtime and stress on my part.
I can still remember sitting in a meeting of the DEC User Group where Digital had announced that it would no longer support the X25 network protocol in the next revision of VAX VMS. The room was full of system administrators complaining that they needed X25 support, despite the fact that Digital had spent the last two years moving over to TCP/IP. I however was completely calm, since the version of VAX VMS I was running was about four generations old already and I had no intention of upgrading to the new version.
Obviously there can be benefits to upgrading your OS, firmware or drivers. The latter in particular can often reap significant performance benefits, but even something as simple as a driver update can often break as much as it fixes. The important thing is to know what youâ€™re getting, and to always read the label. Sometimes you have to install updates in a certain order and if you do them out of sync you can end up in trouble â€“ as Benny found out recently while flashing the BIOS on his motherboard.
With any kind of update you need to know what itâ€™s going to do to your hardware and ask yourself whether you need those enhancements AND whether youâ€™re going to lose any current functionality as a result. Then, and only then should you take that final step and install the update.
Unfortunately itâ€™s not always that easy and sometimes that freedom of choice is taken out of your hands. When I bought my PSP it was running firmware Version 1.0. It wasnâ€™t long before there were plenty of â€œHome Brewâ€ mods available for the PSP allowing it to emulate old consoles and run games directly from a MemoryStick. Unfortunately Sony didnâ€™t like this and made sure that it closed the door on such mods with newer firmware releases. No problem I thought, I just wonâ€™t bother to upgrade my firmware â€“ but Sony already had my number.
What Sony did and is continuing to do, is to force PSP owners to upgrade the firmware on their consoles. Basically when you buy certain new games, youâ€™re forced to upgrade the firmware before you can play them. Itâ€™s like being held to ransom â€“ do you want to play this game or not? Obviously you want to or you wouldnâ€™t have bought it in the first place, so the chances are that the vast majority of PSP owners will just go with the flow and jump to the next firmware version, keeping Sony happy in the process.