Steve Grammont / 04.11.13 / 5:53AM wrote: >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.
With all due respect, this is hard to believe hearing from ex-QA. In the real world, developer will not take a look at the bug if QA doesn't present the bug report with the hard fact, not just a guess. To report a bug, you often have to go back to a clean machine and make sure the bug is still reproducible, or run a debugger to gather a hard facts, if there is no reproducible steps. In the real world, you can't call it a bug until you have hard evidence to point finger with. I am not saying PM is bug clean, and I am not saying your problem is not PM related for sure. In fact, I have the same problem as you have. I get frequent indices rebuilt after PM crash, but my problem is clearly related to PM since crash happens when downloading emails, and it is easy to understand why indices corrupts during the course of the action. Back to your problem, none of us can reproduce your problem, that is, Open PM, Check no disk I/O activity present, Cold reboot, Open PM again, -- You get PM goes into 16 hours errands, but non of us does. The first thing you _have to_ do is to create new user with empty PM database then try to reproduce the problem *before* you call it a bug. It well may be your database is already corrupt, and you do know well as you used to be a QA that database could corrupt easily. If that the case, you need to rebuilt your database with other tools than PM itself if it didn't work. -- - Hiro [PROTECTED] <[PROTECTED]> <[PROTECTED]>
