Cheers Bob - just disabled Microsoft .NET Framework Assistant 1.1, and all now seems to work fine. I haven't the faintest idea what it did (apart from apparently causing the above problem...)