Nov 1, 2009, 11:17 GMT
Hannover, Germany - There's a sense of exclusivity in being able to download a beta version of a new computer program and become one of the first people to test it before its official release.
And, in many ways, it is important work. Users report problems to software designers, making them vital to the creation of multiple programs, operating systems and web browsers. But there are risks. In a worst case scenario, beta testers risk crashing their whole system.
'In business jargon, we refer to them as banana products - the software has to ripen with the customer,' says Frank Felzmann of the German Federal Office for Information Security (BSI).
That means there are risks, including that 'the software doesn't yet work properly. It can also lead to security problems if the software accesses the system.' Beta versions have also been known to affect the stability of a system.
That's why experts recommend unskilled users avoid offering themselves and their computers up as test subjects. 'In general, I would only recommend beta versions to experienced users. Everyday users, who put a lot of stock in having a stable system, should wait for the final product,' recommends Martin Michl of the German computer magazine Chip.
Hajo Schluz, who writes for another German computer magazine, c't, agrees.
Nonetheless, he understands why some computer users want to test programs before their official release. Microsoft recently released an advance version of its Windows 7 operating system to registered users. Google did the same with the beta version of its Chrome browser.
Whether you're an old hand or a beginner, anyone who installs a beta version on their computer should take certain precautions.
'Our recommendation is to install a beta version, if you do it at all, on a computer where there's nothing else running,' says Felzmann. That at least minimises the fallout from any damage.
If a user insists on installing the beta version on a computer that's being used regularly, further safeguards should be taken, advises Michl.
'You should always secure the entire system,' he says. For example, with Windows, that means defining a recovery point to return to in case a disaster recovery needs to be made. It's also a good idea to create an image of the system, which can be reconstructed on a CD-ROM in a worst-case scenario.
Schulz also recommends against using not-ready-for-prime-time software for important tasks. 'Anyone who writes an academic thesis with a beta version only has himself to blame.'
If a document created with a beta version is destroyed, the user has no claim against the manufacturer, says Schulz. 'Even with regular software, claims over data loss are ruled out.' Manufacturers have an even stronger standing in cases involving beta versions.
Strictly legally, private users can use the downloaded software without ever offering feedback. But common decency demands providing the programmers with some help, says Schulz.
Your Talkback on this Story