> And you didn't get a warning about Squeak not being able to open the
> changes file? Usually this kind of problem is reported right upon startup.
>

Squeak starts up ok.
It can read the changes file ok.
It can write to the changes file ok.
BUT,
after writing to it, and at some delayed point in the future, NOD32 detects the file change and opens the changes file to scan it.
If, while this scan is happening, another write to the changes file is attempted, then the error occurs.
 
So the error is more likely to occur during a large file-in, than with a small one.
 
Cheers,
Andy
 
 
 

---

With Live Spaces email straight to your blog. Upload jokes, photos and more. It's free! It's free!