James D. DeWitt :
>basically, it has been dead for ten days. Yes, I've rebuilt and
>reinstalled--two or three times at least.
Did you try version 2.0v1 instead of the latest 2.0v3 most of you are using?
I've had Emailer die a few times. This would mainly occur as follows:
- Emailer crashes under Classic (I don't remember when it started but schedules now
crash my Emailer if it's hidden under OS X, I stopped looking into it when I found I
could get more work done if I only checked mail manually instead of letting it disrupt
me constantly ;-)
- this sometimes brings down Classic (have to force-quit in the Classic prefpane)
- usually relaunching Emailer works fine but sometimes not (seems to launch but quits
immediately): in those cases I was only able to revive it by rebooting under OS 9 and
launching it there (and strangely nothing more, looks more like a Classic issue than
an Emailer one, maybe it's just rebooting in OS 9 that cures Classic)
- in one or two occasions it happened under OS 9 (or 8.6 or 7.5.5 I don't recall),
wouldn't relaunch there either, and this was with 2.0v3 (I mainly use french 2.0v1). I
wouldn't swear, but I think launching 2.0v1 cured the problem in those cases.
If you want to try, some tweaking is required to force 2.0v1 and 2.0v3 to live happily
together (if it's only for checking, just move the 2.0v3 files mentioned later out of
you Emailer files folder before launching 2.0v1 or it will choke on some of them).
It's been a long time, but I think here's what I did:
- put both 2.0v1 and 2.0v3 apps in the same folder to share support files (I put help
and prefs files there too to make backups easier and safer, Emailer looks in it's
folder first before checking the "Claris" folder in the active system)
- edit the apps with resedit to change the names of their prefs files to something
more useful (ressource STR# ID 501 "File names"), in my case�:
Pr�f. Emailer VRic 2.0v3 (for my emailer 2.0v3)
Pr�f. Emailer VRic 2.0v1 (for my emailer 2.0v1)
Pr�f. Emailer Poulette (for my girlfriend's app, so that we'd share support files
but still access personal databases by launching our separate Emailer apps -- even
simultaneously, and checking each one's accounts in the background)
The current database ("Emailer Files" folder) is remembered in the prefs file with
some other general settings, but everything mail-related (accounts, programs,
schedules etc.) is in the database. So it's easy to make different apps use different
databases, but it's trickier to have 2.0v1 and 2.0v3 use the same database because
2.0v3 converts some files to a newer format, specially the address book that won't
work in 2.0v1 afterwise, hence the next steps.
- if already using 2.0v3, export the addressbook to text (to import it in 2.0v1 later)
- edit the apps with resedit to give distinct names to some database files (I didn't
bother checking which could be shared, so I just renamed all of them so that each
version would have a duplicate of each file in my Emailer Files folder). Note that
mine use french names, so this list may not be accurate:
Actions 2.0v1 Actions 2.0v3
Address Book 2.0v1 Address Book 2.0v3
Connexions 2.0v1 Connexions 2.0v3
Destinations 2.0v1 Destinations 2.0v3
Locations 2.0v1 Locations 2.0v3
Transfer tools 2.0v1 Transfer tools 2.0v3
Programs 2.0v1 Programs 2.0v3
Addressbook 2.0v1 Addressbook 2.0v3
Services 2.0v1 Services 2.0v3
Signatures 2.0v1 Signatures 2.0v3
Now just use either version of Emailer at will (don't launch both versions
simultaneously using the same database, since the mail content is shared and that's
the point). Of course the files we renamed will get out of sync so one should choose a
prefered version for everyday use because things set in one won't appear in the other
(this could be reduced by verifying which files really need to be distinct, maybe only
the address book does).
I hope somebody finds that useful; it was fun remembering anyway.
----
VRic
___________________________________________________________________________
To unsubscribe send a mail message with a SUBJECT line of "unsubscribe" to
<[EMAIL PROTECTED]> or <[EMAIL PROTECTED]>
