Help [Eudora]

Prev: LinkHistory.dat problem
Next: Eudora 7.1 and XP 64-bit

From: $Dan, danl, Redbeard uh Greybeard now on 14 Aug 2006 09:18

Hi all,
When I tried to check my mail this morning I got a message that the
inbox was, I did not write this down so it may not be exact, damaged
and did I want to rebuild it? I clicked yes and now all I get is this
message that says Eudora must close with the following info.

The instruction at "ox73dd11c7" referrenced memory at "0.00000004".
The momory could not be "read".
Click OK to terminate program.

I have my virus scan set to scan incoming mail and I have run my up to
date Trend virus scan on Eudora with no virus detected.

I am running a Dell E1505 with Intel Core Duo, 1meg and Eudora Ver.
4.2.2

I know I should update and will as soon as this problem is settled.

Any advice will be appreciated.

Thanks

I've learned that I don't suffer from insanity, I enjoy it!
danl4x(a)charter.net
Remove the x for e-mail reply
Amateur radio enthusiast, N9JBF
Bass fishing Aficionado!
www.outdoorfrontiers.com
www.SecretWeaponLures.com
A proud charter member of "PETAF", People for Eating Tasty Animals and Fish!!!

From: $Dan, danl, Redbeard uh Greybeard now on 14 Aug 2006 10:44

On Mon, 14 Aug 2006 08:18:49 -0500, "Dan, danl, Redbeard uh Greybeard
now" <danl4X(a)charter.net> wrote:

>Hi all,
>When I tried to check my mail this morning I got a message that the
>inbox was, I did not write this down so it may not be exact, damaged
>and did I want to rebuild it? I clicked yes and now all I get is this
>message that says Eudora must close with the following info.
>
>The instruction at "ox73dd11c7" referrenced memory at "0.00000004".
>The momory could not be "read".
>Click OK to terminate program.
>
>I have my virus scan set to scan incoming mail and I have run my up to
>date Trend virus scan on Eudora with no virus detected.
>
>I am running a Dell E1505 with Intel Core Duo, 1meg and Eudora Ver.
>4.2.2
>
>I know I should update and will as soon as this problem is settled.
>
>Any advice will be appreciated.
>
>Thanks
>
>
>
I tried renaming the in mbx and toc to oldin and oldtoc but it did not
appear to help.

Here is what I think are the log files from this morning. Don't know
if that will help.

Mon Aug 14 07:49:09 2006
Version 4.2.2
3068 8:0.0 Dialog: "Mailbox In has a damaged table of contents. Shall
I build a new one for you?"
3068 8:0.14 Dialog: "Dismissed with 1"
3068 8:0.15 Dialog: "602 of the 606 summaries in the old table of
contents used; 491 new summaries were created."
3068 8:0.26 Dialog: "Dismissed with 1"
Mon Aug 14 07:50:19 2006
Version 4.2.2
4072 8:0.0 Dialog: "Mailbox In has a damaged table of contents. Shall
I build a new one for you?"
4072 8:0.6 Dialog: "Dismissed with 1"
4072 8:0.6 Dialog: "1094 of the 1095 summaries in the old table of
contents used; 1 new summaries were created."
4072 8:0.10 Dialog: "Dismissed with 1"
Mon Aug 14 07:59:58 2006
Version 4.2.2
820 8:0.0 Dialog: "Mailbox In has been changed since its table of
contents was created. Do you wish to use the old table of contents,
or create a new one?"
820 8:0.8 Dialog: "Dismissed with 1155"
Mon Aug 14 09:34:40 2006
Version 4.2.2
2752 8:0.0 Dialog: "Mailbox In has been changed since its table of
contents was created. Do you wish to use the old table of contents,
or create a new one?"
2752 8:0.19 Dialog: "Dismissed with 1155"
Mon Aug 14 09:37:14 2006
Version 4.2.2
1492 8:0.0 Dialog: "Mailbox In has been changed since its table of
contents was created. Do you wish to use the old table of contents,
or create a new one?"
1492 8:0.5 Dialog: "Dismissed with 1"
1492 8:0.5 Dialog: "0 of the 0 summaries in the old table of contents
used; 0 new summaries were created."
1492 8:0.9 Dialog: "Dismissed with 1"

I've learned that I don't suffer from insanity, I enjoy it!
danl4x(a)charter.net
Remove the x for e-mail reply
Amateur radio enthusiast, N9JBF
Bass fishing Aficionado!
www.outdoorfrontiers.com
www.SecretWeaponLures.com
A proud charter member of "PETAF", People for Eating Tasty Animals and Fish!!!

From: Katrina Knight on 14 Aug 2006 11:44

Dan, danl, Redbeard uh Greybeard now <danl4X(a)charter.net> wrote:
> When I tried to check my mail this morning I got a message that the
> inbox was, I did not write this down so it may not be exact, damaged
> and did I want to rebuild it? I clicked yes and now all I get is this
> message that says Eudora must close with the following info.

At what point did you get that error message? After you tell Eudora to
rebuild a mailbox, you should get an dialog box that tells you how many
old message summaries were used and how many new ones were created. Did
you see that? Or did Eudora crash before getting that far? If you saw
that, what did you do afterward? Is the inbox open, or trying to open
when you get the error?

> The instruction at "ox73dd11c7" referrenced memory at "0.00000004".
> The momory could not be "read".
> Click OK to terminate program.

Messages about memory not being able to be read *can* be an indication of
bad memory. Or they can be an indication that a program is screwed up and
trying to read a piece of the memory that doesn't belong to it. The latter
is probably more likely in this case.

> I am running a Dell E1505 with Intel Core Duo, 1meg and Eudora Ver.
> 4.2.2

> I know I should update and will as soon as this problem is settled.

That is a really old version, and it is possible that upgrading might be
all you need to do to fix the problem. (Usually, I don't recommend
upgrading when Eudora isn't working to start with, but in this case, it
might be helpful. If you try it, install the new version in its own
program directory but instruct it to use your existing data directory for
data.)

It is unclear to me whether needing to rebuild the inbox toc file and the
error message are directly or indirectly related. When you restart Eudora,
do you see the message about rebuilding the toc file each time? If you do,
the problem is most likely that you received a message that can't be
processed properly. The solution for that is to close Eudora then look for
..rcv files in the "spool" subdirectory of your Eudora data directory. If
you find any, sort them by date. The oldest one is almost certainly the
problem one. Open it with a text editor and see if it is something you
want to keep. If it is, move the file out of "spool" temporarily. If it is
not something you want, just delete the file. Restart Eudora and see if it
works. (Eudora may want to rebuild the toc file one more time when you
start it again, but it shouldn't crash if you've dealt with the right
spool file.) Even if you aren't having to rebuild the toc file each time,
making this check would be a good idea.

Another possibility is that the problem is that you got a message that was
properly processed, but that can't be displayed, either because it is
damaged or because it contains html that is a problem for the version of
Eudora you're using. If that's the case, you need to delete the message
without displaying it. To do that, turn off the preview pane before
opening the mailbox. If Eudora is opening with the mailbox open, you'll
have to turn off the preview pane by editing eudora.ini. The needed
setting is MailboxPreviewPane=0 and it goes in the [settings] section of
eudora.ini. (Be sure Eudora is closed when you edit the file.)

--
Katrina

From: $Dan, danl, Redbeard uh Greybeard now on 14 Aug 2006 12:21

On Mon, 14 Aug 2006 15:44:05 GMT, Katrina Knight <kknight(a)epix.net>
wrote:

>Dan, danl, Redbeard uh Greybeard now <danl4X(a)charter.net> wrote:
>> When I tried to check my mail this morning I got a message that the
>> inbox was, I did not write this down so it may not be exact, damaged
>> and did I want to rebuild it? I clicked yes and now all I get is this
>> message that says Eudora must close with the following info.
>
>At what point did you get that error message? After you tell Eudora to
>rebuild a mailbox, you should get an dialog box that tells you how many
>old message summaries were used and how many new ones were created. Did
>you see that? Or did Eudora crash before getting that far? If you saw
>that, what did you do afterward? Is the inbox open, or trying to open
>when you get the error?
>
>> The instruction at "ox73dd11c7" referrenced memory at "0.00000004".
>> The momory could not be "read".
>> Click OK to terminate program.
>
>Messages about memory not being able to be read *can* be an indication of
>bad memory. Or they can be an indication that a program is screwed up and
>trying to read a piece of the memory that doesn't belong to it. The latter
>is probably more likely in this case.
>
>> I am running a Dell E1505 with Intel Core Duo, 1meg and Eudora Ver.
>> 4.2.2
>
>> I know I should update and will as soon as this problem is settled.
>
>That is a really old version, and it is possible that upgrading might be
>all you need to do to fix the problem. (Usually, I don't recommend
>upgrading when Eudora isn't working to start with, but in this case, it
>might be helpful. If you try it, install the new version in its own
>program directory but instruct it to use your existing data directory for
>data.)
>
>It is unclear to me whether needing to rebuild the inbox toc file and the
>error message are directly or indirectly related. When you restart Eudora,
>do you see the message about rebuilding the toc file each time? If you do,
>the problem is most likely that you received a message that can't be
>processed properly. The solution for that is to close Eudora then look for
>.rcv files in the "spool" subdirectory of your Eudora data directory. If
>you find any, sort them by date. The oldest one is almost certainly the
>problem one. Open it with a text editor and see if it is something you
>want to keep. If it is, move the file out of "spool" temporarily. If it is
>not something you want, just delete the file. Restart Eudora and see if it
>works. (Eudora may want to rebuild the toc file one more time when you
>start it again, but it shouldn't crash if you've dealt with the right
>spool file.) Even if you aren't having to rebuild the toc file each time,
>making this check would be a good idea.
>
>Another possibility is that the problem is that you got a message that was
>properly processed, but that can't be displayed, either because it is
>damaged or because it contains html that is a problem for the version of
>Eudora you're using. If that's the case, you need to delete the message
>without displaying it. To do that, turn off the preview pane before
>opening the mailbox. If Eudora is opening with the mailbox open, you'll
>have to turn off the preview pane by editing eudora.ini. The needed
>setting is MailboxPreviewPane=0 and it goes in the [settings] section of
>eudora.ini. (Be sure Eudora is closed when you edit the file.)

Thanks for the reply Katrina.

Where to start. Yes I did get the message to rebuild and I clicked
yes. It did not help.

I then posted the message you replied to and began seaching the
archives. Came across a past message of yours. Renamed the intoc and
inmbx to no avail. Researched farther back in the archive thread and
found the reference to the spool folder. Checked the contents with
notepad and found only one message in it. It was a damned spam/scam
message. I deleted this message and tried again. Viola! The program
now started and when I told it not to rebuild the damaged box it
started and sent/received mail properly. All my incoming messages
were damaged beyond repair. I deleted them all and the program now
opened properly with no rebuild box. I then upgraded and Eudora Pro
seems to be operating fine again.

Do you know of any way I can prevent this from happening again or does
everyone take their chances? What is a good way to save inbox
messages so I can have them for future reference? Is there a way to
make the saving of messages in a protected folder automatic?

Another question...

I have noticed a lot of spam/scam messages coming from certain blocks
of addresses, spoofed or not and was wondering about the feasability
of building a filter. Any hints?

Again, thank you for the reply

I've learned that I don't suffer from insanity, I enjoy it!
danl4x(a)charter.net
Remove the x for e-mail reply
Amateur radio enthusiast, N9JBF
Bass fishing Aficionado!
www.outdoorfrontiers.com
www.SecretWeaponLures.com
A proud charter member of "PETAF", People for Eating Tasty Animals and Fish!!!

From: Dan, danl, Redbeard uh Greybeard now on 14 Aug 2006 12:21

| Next | Last
Pages: 1 2
Prev: LinkHistory.dat problem
Next: Eudora 7.1 and XP 64-bit