6.2.4 Panther 'Couldn't Read YourSettings' random error.
wookiee
Now, on occasion, I still get ...
'Couldn't Read Your Settings'
65962468+ 227(-39); The end of file has been unexpectedly reached.
{90:914}
Then
'Eudora could not check mail in the background.
Try closing some windows or switch background threading off.
-39 (90:435)'
background is off, this will sometimes pop up with no windows open.
The pain is that Eudora won't do anything until the error dialogs are
closed.
--
Wookiee
Steve W. Jackson
wookiee <wooki...@gmail.com> wrote:
I don't recall ever seeing this before Leopard, but I've experienced it
a handful of times.
My immediate response is to quit Eudora, trash the settings file and
then remove the ".bkup" from the name of the other one that's created
every time Eudora runs. This has always worked.
I've yet to see any particular pattern behind this occurrence, and it
last happened to me some weeks ago.
= Steve =
--
Steve W. Jackson
Montgomery, Alabama
wookiee
It was occurring at least once a day.
I started looking at all Eudora files and noticed they were owned by me
as well as unknown.
I remember reading that unknown is a remnant from the leopard upgrade.
Since this was the only anomaly I could find, I tried removing this
unknown user. But Nooooo, osx wouldn't allow a simple removal. So I
had to try to remember what other user names/groups that I used before
the upgrade. After trail and error, it was a group that had the same
name that I use for my username.
So, once that group was created, all references to group unknown were
changed by osx to my old group name.
The result being that Eudora has run without a hitch for 3 days! Which
is a first since the Leopard upgrade.
Kathy Morgan
> I started looking at all Eudora files and noticed they were owned by me
> as well as unknown.
> I remember reading that unknown is a remnant from the leopard upgrade.
> Since this was the only anomaly I could find, I tried removing this
> unknown user. But Nooooo, osx wouldn't allow a simple removal. So I
> had to try to remember what other user names/groups that I used before
> the upgrade. After trail and error, it was a group that had the same
> name that I use for my username.
>
> So, once that group was created, all references to group unknown were
> changed by osx to my old group name.
>
> The result being that Eudora has run without a hitch for 3 days! Which
> is a first since the Leopard upgrade.
Thanks for the update; it will be nice having an answer for the next
person who encounters the same problem.
I, too, had problems with my last upgrade, but it wasn't with Eudora; it
was the System. It turns out that my 8 character system password
carried forward from OS 10.1 was a problem, and I was unable to access
anything. :-( I finally had to erase the volume and reinstall, then
restore all my files as best I could. (Word to the wise: Never, ever do
an upgrade without first making a fresh backup.)
--
Kathy
Peter Ceresole
> I, too, had problems with my last upgrade, but it wasn't with Eudora; it
> was the System. It turns out that my 8 character system password
> carried forward from OS 10.1 was a problem, and I was unable to access
> anything.
Gulp. I have one of those (8 character pqssword that's carried forward
from 10.2). This sounds like potentially bad news. What was wrong with
yours?
--
Peter
Kathy Morgan
> Gulp. I have one of those (8 character pqssword that's carried forward
> from 10.2). This sounds like potentially bad news. What was wrong with
> yours?
Mine was actually 9 characters, and apparently there's a bug that
affects users with a login password of 8 characters or more that's been
carried forward from 10.2.8 or earlier to 10.5.
<http://support.apple.com/kb/TS1543> I see on the Apple website today
that they recommend applying the Login & Keychain Update 1.0 for Mac OS
X 10.5 Leopard to avoid the issue--not that such a thing is possible if
you're on a single-user box affected by the bug, since you can't log in
to be able to download and apply an update. They had a couple of other
work-around and fix suggestions on the website, but none of them worked
for me. I ended up having to use the installation disk as the startup
drive and do an erase/install.
--
Kathy
Peter Ceresole
> Mine was actually 9 characters, and apparently there's a bug that
> affects users with a login password of 8 characters or more that's been
> carried forward from 10.2.8 or earlier to 10.5.
Damn. Mine is exactly 8 characters, dating back to 10.2.0. Does that
mean that *before* going to 10.5, I could avoid this trap by changing my
password to one of 7 characters or less? That doesn't seem clear from
the knowledgebase article you mention...
--
Peter
Kathy Morgan
I'd definitely do a backup before doing the upgrade. That's always
sound advice, and I usually do backup first, but this once I didn't, and
it was the time I should have. I got careless after so many
trouble-free upgrades.
I think changing the password to anything different would prevent the
problem. My old 9 character password works fine, after the erase and
install. 8 or 9 or presumably even longer passwords are fine, as long
as they haven't been carried forward from 10.2.8 or earlier.
--
Kathy
Steve W. Jackson
kmo...@spamcop.net (Kathy Morgan) wrote:
> wookiee <wooki...@gmail.com> wrote:
>
> > I started looking at all Eudora files and noticed they were owned by me
> > as well as unknown.
> > I remember reading that unknown is a remnant from the leopard upgrade.
> > Since this was the only anomaly I could find, I tried removing this
> > unknown user. But Nooooo, osx wouldn't allow a simple removal. So I
> > had to try to remember what other user names/groups that I used before
> > the upgrade. After trail and error, it was a group that had the same
> > name that I use for my username.
> >
> > So, once that group was created, all references to group unknown were
> > changed by osx to my old group name.
> >
> > The result being that Eudora has run without a hitch for 3 days! Which
> > is a first since the Leopard upgrade.
>
> Thanks for the update; it will be nice having an answer for the next
> person who encounters the same problem.
It might be useful info, but it's not a fix. I do *not* have the
ownership settings that the OP described -- never did have. And yet
I've occasionally encountered this very issue. In fact, it happened to
me a day or two after I first read this.