Avoiding Update Perils

Updates are great, right? You get new features and fixes, often for free. But unlike updating a computer OS (see last month’s “21st Century Recording” column), updating a product can contain some pitfalls that at worst, could leave you with a non-functioning device. As you probably don’t want that, let’s cover how to avoid the various issues that could cause problems during the update process.


There are three main types of updates:

-Chip updates. This is a physical process, where you remove one or more chips and replace them with updated chips.

-Firmware update. You don’t need to take off the cover for this one; you may need to run a program while the device is connected to a computer (e.g., via USB), or load firmware in from a CD if the device has a CD drive. In this case, you’re generally rearranging the memory of a chip deep within your product’s innards.

-Software revision update. With this type of update, you upgrade an existing version of a software application with new features or bug fixes by running an executable program.

For each of these types, the first and most important rule is to read any documentation that came with the update (piece of paper, “read me” file, whatever). One wrong move during an update could lead to real problems. If there’s something you don’t understand in the instructions, contact the company’s tech support and make sure you know what you’re doing before you proceed.


-Chips are sensitive to static electricity. Wear a grounding strap (available at electronic supply stores) and connect it to a metal part of the device being updated.

-Make a special 3-conductor IEC line cord that has the hot and neutral prongs cut off, but the ground prong intact. With AC-powered gear, use this so that the unit is grounded to the wall socket ground but doesn’t have power going to it.

-The chip will likely come in a protective package. Leave it in there until the very last moment. When you pull out the old chip, rest its pins on a metal surface (e.g., a piece of aluminum foil), then after removing the new chip from its packaging, put the old chip in it. You may need to reinstall the old chip at some point, so keep it protected.

-Line up the pins on the chip before inserting it into its associated socket. One of the biggest problems with chip updates occurs when a pin gets folded under the chip instead of getting into the socket.

-If the chip doesn’t show update information, put a removable label either on the chip or in the unit itself. Write the update revision and date of installation on the label.

-When inserting a chip, apply even pressure all the way around as you work the chip into its socket. Make sure that the pins remain straight at all times.


Of the various update options, this one is by far the most dangerous. If the chip update fails, you can just put the old one back in, and if a software revision update fails, you can re-install the program. But if a firmware update fails, the device may be left in a state where it is not only non-functional, but can’t even “boot” to attempt another update or reinstall the old firmware.

Reading any instructions is, once again, crucial. But re-read them as well. Then, make sure that the device being updated and whatever is doing the updating (e.g., your computer running a program) are both running from an uninterruptible power supply. The most common causes of a firmware update failing are not reading the instructions, or having a power failure occur in the middle of the updating process. Also make sure that if a cable is involved (like a USB cable that shuttles date to the unit), it’s not intermittent and is plugged in firmly.

If the firmware update involves loading data from a CD, do not use a rewritable one, and burn at a relatively slow speed.


-Do “due diligence”: Check the company’s forums for discussions about updates. Sometimes there will be incompatibility issues that mostly likely won’t affect you . . . but they might.

-It’s prudent to wait a week or two before installing an update just to make sure no important issues arise; you then need to judge whether the updated features are worth the potential pitfalls. However, bear in mind that some Internet forums do not always have accurate information — the problem might be that someone didn’t read the instructions.

-If you are updating a Windows program, most updates set a system restore point “just in case.” But not all do, so before making any changes, set a system restore point (Start > Programs > Accessories > System Tools > System Restore).

-It may be necessary to uninstall the previous version of a program for the update to “stick.” The documentation should tell you whether this is necessary.

-When updating a software program, always copy any custom patches, files, etc. to a separate location. Usually you’ll be warned if an update will modify these, but it doesn’t hurt to make sure.

-With downloadable updates, create a folder that contains all updates. If you later need to reinstall a program from scratch (e.g., hard drive crash), you may need to install the original program then follow the “update path” through the various revisions — you can’t always update a version 1.0 to a version 1.2 without going through version 1.1 first. In that same folder, keep any serial number or activation info.

Okay . . . now you’ll have a successful update. Enjoy the new features!