Hey, How About A Text File Now and Again To Explain Those Drivers and Updates

Here’s a call I wish everyone from Microsoft to OEMs would heed. In this crazy time the world is dealing with new drivers and new updates being released on what seems like an almost too frequent occurrence. And of course many of them have such wonderfully descriptive names that they may as well be called ““anydriver.zip” or ““anyoldupdate.exe.” Would it pain anyone greatly to include a .txt or Read Me file in those zips? When they do, would it pain anyone greatly to include one that was a least updated a bit from the last release to include info on the current version? I experienced this first hand installing Vista drivers on the Asus R2H this weekend and am seeing it far too often. One example: in the VGA driver package from Asus, clearly labeled as a Vista release, the included readme contains lots of info on how to install for XP. Not one heading relating to Vista beyond the top of the page.

We all know tech support doesn’t want to be bothered about this, and often when they are, they are as clueless as the user. So, here’s suggestion (and I’ll bet is saves money in the long run.) When you release a slew of drivers and updates for a device. Include a simple Read Me that gives out the order of installing the files and what the files are intended for. If there are co-dependencies list that as well. Can it be that tough? Or do you prefer your customers, whom I assume you’d like to become repeat business, to play hunt and peek, hide and seek, restore and reboot?

C’mon guys. I know things are hectic trying to soothe the cries for drivers that make your hardware and software actually work as advertised. Geeks will figure it out. But if you want the average Joe and Jane to actually consider buying some of your product, a little thought towards the customer might be in order.