EVALUATION
I can only reproduce the problem on solaris with the latest version of javaws
###@###.### 2002-11-08
On solaris, sometimes the cache will contains a ".nfsxxx" file, where xxx are some random characters.
After the cache is cleared, these .nfs file will regenerate right the way.
which cause the AdvancedPanle.isCacheDirValid check to fail, because the cache is not empty and it does not contain the lastAccessed file. So the invalid cache location dialog poped up.
A fix could be putting the lastAccessed file back after we clear the cache, which makes the cache a valid cache again even some file system private files (e.g .nfsxxx file in this case) cannot be removed.
###@###.### 2002-11-08
|