Hi there,
Jerome's suggestions appear to have fixed my major problems with
PowerMail stability under 10.2.8. However, one remains. My system, for
some unknown reason, occasionally crashes and shuts down when left
unattended. It doesn't happen very often, but when it does PowerMail
almost alway
>The suggestion
>to remove or at least temporarily and partially disable something which
>can do things with directories, file structures and whatnot _systemwide_
>is a very logical suggestion. - Why? - Because just because program "A"
>crashes it's not necessary its fault.
True, but pointing
From Steve Grammont <[EMAIL PROTECTED]> on Sun, 14 Nov 2004 01:27:38
-0500 [7.27 CET]
>>That's not what we have been saying. We have been saying we believe
>>removing Norton is the first thing to try. If you don't feel that way,
>>and are not willing to try our suggestion, our hands are up in t
>I probably should stop responding to this thread since we are not going
>anywhere with this. Yes, I am a musician since I was 10. My master's
>degree is in music composition, but I was a real QA since 1995 till 9-11
>happened. Micro$haft NetMeeting, Lycos parsing engine, and Amazon order
>pa
Steve Grammont / 04.11.13 / 2:28PM wrote:
>With all due respects, sounds like you've never run a testing department
>or, probably, even been in QA for a commercial product.
I probably should stop responding to this thread since we are not going
anywhere with this. Yes, I am a musician since I wa
Hiro,
>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
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
>I have the same reaction as Hiro: turn off any low-level system
>utilities you have installed. Run Disk First Aid. Ensure journaling is
>turned on for the filesystem. See if things run any differently with the
>low-level tools disabled.
See my response to Hiro. I think this is chasing my
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 pr
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 iss
On 13 11 2004 at 12:35 am -0500, A-NO-NE Music wrote:
>This well may be the heart of your problem.
>Norton corrupts OSX file directories, and this is why Symantec
>discontinued Norton for Mac. If I were you, I'd rebuild your machine
>from scratch. It is not unreasonable to doubt Norton damaged
Steve Grammont / 04.11.13 / 0:13AM wrote:
>I stated quite clearly that PM is in an idle state. That means it is not
>periodically checking email automatically (I've hated this feature since
>email was invented ).
My sincere apology. I missed that.
Then PM cannot corrupt file unless file is not
>How do you know that PowerMail is idle (i.e., not writing to the
>database) at the time your system is going down?
Because there is no activity. It is not tasked with receiving email or
sending it out, and therefore shouldn't be doing anything with the index
files. Also as you might know, th
Hiro,
>Yes, if crash happened during file write, B-Tree needs to be rebuilt.
Yes, but you are comparing incorrect things. I am talking about an idle
state. The example you gave is an active state. I can understand file
corruption with PM if it is actively doing something when a crash occurs.
Steve Grammont / 04.11.12 / 5:16PM wrote:
>Think about it this way... each time your System crashes does it tell you
>upon reboot that it needs to rebuild the harddrive? Does it tell you
>that all your System preferences are now all corrupt, even for things
>that you were not using at the time o
On 12 11 2004 at 5:16 pm -0500, Steve Grammont wrote:
>From my earlier stability problems Jerome said "When a crash occurs on
>IDLE, there is no rebuild." That is the correct answer. Unfortunately,
>that isn't my experience. And since this is happening regularly, that
>indicates to me that som
Hello Ben,
>:) It's not PowerMail's responsibility that your system is shutting
>down.
Correct. PowerMail is likely not responsible for causing my system to
crash. But that isn't the point. The point is that when a program has
an open file, and is not currently manipulating it, there should
On 12 11 2004 at 4:22 pm -0500, Steve Grammont wrote:
> So why do I have PowerMail corruption problems so consistently?
I think you answer your own question:
> My system, for
>some unknown reason, occasionally crashes and shuts down when left
>unattended.
:) It's not PowerMail's responsibili
On 13/11/2004 at 12:21 AM I saw Steve Grammont type:
>on 13/11/2004 at 2:31 AM I saw Ben Kennedy type:
>>How do you know that PowerMail is idle (i.e., not writing to the
>>database) at the time your system is going down?
>
>Because there is no activity. It is not tasked with receiving email or
>
19 matches
Mail list logo
