Hello kename, >Do you have background indexing turned off in the preferences? In >reference to the latest version, it's still on here.
Yes, it is turned off. Rather annoying when you go to do a Search after a couple of days :-) >And I think straws is what you are down to considering. Other issues have >been considered, discussed and evaluated. By your own admission something >is wrong. When you've ruled out the obvious, that leaves the obscure. Correct. But I'd say the obvious is that there is some sort of bug with PM (or in how the OS handles a PM instruction) that, for whatever reason is showing up rather than some system wide corruption conspiracy theory. The simple answer is most likely the obvious one. And since I don't have problems with any other application... the problem is most likely isolated to PM. >I have a hard time believing that PowerMail is failing to write something >out correctly or finish a critical task. If this were the case, problems >such as this would be endemic to the client and show up all across it's >user base....We've had some issues, but nothing that has resulted in >the serious problems you are facing. How may 16 hour database rebuilds did you have last week? I've had three. They were the result of PM and were fixed once Jérôme gave me some work arounds. >True, your system is unique. If for no other reason than you type >different words on your keyboard than I do. I think Ben and Hiro were >trying very hard to help isolate some of those differences. Don't dismiss >them out of hand. They did not ask questions but instead made assumptions. While I understand that their intentions were to be helpful, that sort of approach is not. Rule out PM first, because it is the most likely suspect, then look for other problems if none can be found with PM. Just as a note, I've been a software developer for 10 years and was the head of a QA department for 2. I might not be perfect at hunting down issues, but I am certainly more experienced that most. They also overlooked the fact that Jérôme said it shouldn't be happening, yet it is. >If there is indeed activity when there isn't supposed to be any, then >there is a step in the right direction. I would start looking for other >problems that may be lying under the surface. Hiro's suggestion of >system.log and the Hardware Diagnostic are good ones. To just dismiss >help or potential solutions is not a good idea. I did nothing of the sort. I said I didn't know how to do these things. I am fairly new to OS X because I had mission critical applications that could not run under OS X or 9.2. >The system log is most >easily viewed from the console. Applications->Utilities->Console and then >select File->Open System Log from the menu. I have 10.2.8 as previously stated. As far as I know this is a 10.3 feature, is it not? >The Hardware Diagnostic is on one of the CD's that came with your >machine. It will require a reboot and will check your hardware for subtle >problems that may exist. These are lower level tests that I don't think >Norton could ever hope to check, but I may be wrong. I was burned by >Norton at two times in the past and so don't recommend or use them. I am sure that Norton can't do these things, but then again I think this is chasing down the least likely possibility and therefore it isn't high on my priority list. I've emailed with Jérôme and have a better plan with him. Namely crashing PM on purpose and sending him the Index file in its corrupt state. >I hope these things can help you. I hope Ben and Hiro continue to post >helpful thoughts and helps. I understand that it can be frustrating to >keep trying to solve a problem and bang your head on the same wall. I like helpful suggestions. However, I don't think the automatic assumption should be made that PM isn't at fault here and that some much larger problem is responsible. It *might* turn out to be the case, but it isn't the right place to start. Rule out PM first, then look for other problems.
