Dev error bricked 600 PCs, caused $1M CD-ROM write-off
Welcome to Monday, the day upon which The Register offers a new instalment of " Who, Me? " – our reader-contributed column that shares your stories of messing up, ‘fessing up, and somehow finding redress. This week, meet a reader we’ll Regomize as "Oriel" who told us he once worked for a vendor of small business accounting software. This story comes from a time when software shipped on CD-ROMs and users bought it off the shelf in actual shops. The vendor released a new version each year and always shipped it before a major holiday that’s celebrated with a giant meal. Oriel was part of the team whose job it was to get the package ready on time. In the previous year, they flubbed the job because the program didn’t always install itself on some PCs running Windows 95 or Windows ME machines system due to registry corruption. "We wanted to increase our successful installation metrics, so in conjunction with the installation team, a key decision was made – by me – to force the updating of registry keys to enable the install," Oriel admitted. In his email to The Register , he asked the portentous question: "What could possibly go wrong?" What went wrong was that not long after the software was shipped, the vendor’s support lines started getting calls from customers who complained that after installing the accounting package none of their other software would work. "Installing a new version of our application had borked the customer’s machine completely," Oriel wrote. The company decided the best thing to do was to tell affected customers they should go and buy a new PC – and that it would pick up the bill, no questions asked…