Mr. Slarty,

You make two good points there, but this seems to be more a "computer efficiency" kind of question, than computer security.

I find those databases reasonably useful, if used with caution...........at least they tell you if the proggy is a valid Microsoft name.............you have then got to check if it is in the right place, if there is a known "spoof" and so on................

Spyder............

As I load a lot of test/beta whatever stuff, I am used to problems, and do not like things running unless I say so...............in a commercial environment we load updates onto a "reference" machine/machines and test before we do the roll out, which you are obviously aware of After all, autoupdate is never turned on for users.

In a SOHO (small office/home office/domestic) environment, I will tend to set up a stable system and allow autoupdate, telling the owner to let it happen BEFORE they try to use the machine. It is a sort of compromise solution, but seems to work.

It has ocurred to me that I have a number of test boxes running various versions of Windows (98/98SE/ME/2K/XP) so if anyone wants something testing, please let me know. As these are non-critical boxes, I don't mind what happens, I will just re-instate

Cheers