Hello Hiro, >My sincere apology. I missed that.
No problem. >Then PM cannot corrupt file unless file is not closed state, but I can >bet PM does open/close DB file I/O and won't leave it open. Jerome confirmed to me, again, that PM shouldn't be leaving things open. Yet it consistently has problems since 5.x with unexpected quits (either crashing or system failure). >This well may be the heart of your problem. Might be, but it is the least likely suspect at the moment. I find it very hard to believe that Norton did something that has singled out PM for repeated corruptions each and every time PM rebuilds the file. Rule out PM first, then look for other problems. >Norton corrupts OSX file directories, and this is why Symantec >discontinued Norton for Mac. Again, I think you are pointing a finger in the wrong direction. You are also not entirely correct about Norton. The compatibility issues appear to be with 10.3.x only. I am running 10.2.8. Secondly, they have decided to no longer make the product support 10.4 or later, but are planning on making it fully support 10.3. To me it appears the major reasons for abandoning one of the oldest Mac utilities was marketing driven rather than anything else. I found a good article on this here: <http://www.macfixit.com/article.php?story=20040414111904128> >If I were you, I'd rebuild your machine >from scratch. It is not unreasonable to doubt Norton damaged PM database. Even if I was using 10.3.x I don't agree. Causing a problem once, perhaps, but every time that PM crashes? Remember that PM is rebuilding this file, completely, every time it crashes (largely fixed now) or the system unexpectedly shuts down. And until it crashes there are no problems. I don't run Disk Doctor that frequently and I don't think it would be unkind enough to single out PM's index files each and every time while not corrupting anything else. Steve
