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
_________________________________________________________________ Try Live.com - your fast, personalized homepage with all the things you care about in one place. http://www.live.com/getstarted
Generally, if you have NOD installed, any access to the squeak changes file is veeeery slow. I personally have a exception defined on my Squeak directory in Windows to avoid this problem.
Elod
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!
http://specials.uk.msn.com/spaces/default.aspx
Elod Kironsky a écrit :
Generally, if you have NOD installed, any access to the squeak changes file is veeeery slow. I personally have a exception defined on my Squeak directory in Windows to avoid this problem.
Elod
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.
on xp, it was very slow, especially the "snapshoting method" process in Monticello for instance but I had no error... on vista, I was just loading the MCRepositories.st file, which is not very long. The process starts, and then I randomly get an error...
whereas it seems specific to NOD acces protect mode, it may be good to have a specific error for this kind of problem...
each time I interrupted (on xp), I saw the write mode of the change set file set to false if i remember well...
Cédrick
Uninstall this virus guys. use squeak w/o viruses. IMHO, antiviruses is worser than viruses - they sit in your system and eat your memory/cpu resources and in 90% of cases unable to do anything when new virus intruding into your system. Living with antivirus each day is more pain than being infected with virus once in year.
On 29/05/07, Elod Kironsky kironsky@grisoft.cz wrote:
Generally, if you have NOD installed, any access to the squeak changes file is veeeery slow. I personally have a exception defined on my Squeak directory in Windows to avoid this problem.
Elod
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!
http://specials.uk.msn.com/spaces/default.aspx
sig a écrit :
Uninstall this virus guys. use squeak w/o viruses. IMHO, antiviruses is worser than viruses - they sit in your system and eat your memory/cpu resources and in 90% of cases unable to do anything when new virus intruding into your system. Living with antivirus each day is more pain than being infected with virus once in year.
yes why not (btw NOD is not NORTON ;) )... but the problem remains. We cannot convince everybody that is willing to use squeak to uninstall his anti-virus first ;) ...
Cédrick
squeak-dev@lists.squeakfoundation.org
-
Andrew Tween -
Cédrick Béler -
Elod Kironsky -
sig