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