[32] in installers
Re: Eudora 3.02
daemon@ATHENA.MIT.EDU (Marshall Vale)
Mon Mar 17 01:13:17 1997
In-Reply-To: <v03020902af4d9a0d6f9d@[18.81.1.47]>
Date: Mon, 17 Mar 1997 01:03:29 -0500
To: Phyllis Galt <pgalt@MIT.EDU>
From: Marshall Vale <mjv@MIT.EDU>
Cc: installers@MIT.EDU
Hi Phyllis,
>I like the automated setup for multiple users if users choose to do
>it--that was a great idea.
Glad you like it!
>I also like the new KClient. Now, if need be, users can easily confirm
>Kerberos settings and log out. (I was never really sure if the Forget
>Password command really logged users out or not.)
Yes, Forget Password does really kill tickets if they are there.
>Some questions came to mind as I was installing that may (or may not) be
>points I should document in the Web pages:
>
>-Should we make any recommendations about when users would want to do a
>custom install? More specifically, I was wondering if there are scenarios
>where someone should do a custom install rather than the standard (maybe
>not).
Sure. The Easy Install puts the FAT version of the Eudora application
on the user's machine. If the user would like to use less disk space, they
could choose one of the machine specific full installs (PPC or 68K). In
addition, if the user wants to install just components like the manual,
KClient, Eudora settings, etc. then they can do just that via a custom install.
>-Under the Hosts category in the Settings command, the SMTP server is now
>"outgoing.mit.edu" rather than "mit.edu." Can you tell me about the
>change? I'm thinking that it might be a good idea to make note of it on
>the Web page for v2 users who will notice the difference.
The network group requested the change in order to prepare for
>I also had some general questions (not necessarily related to installers):
>
>-If a user runs the installer on a machine that has Eudora v2 and v2 is set
>up for multiple users, does the installer detect this and automatically set
>up v3 for multiple users?
The changes that are done to existing Eudora Settings files (adding @hesiod)
are also done to multiple ones. So the settings files are updated to utilize
Eudora 3's features. However, the organization of the existing mailboxes
is not affected so the user's should see no changes there. In addition,
it will not bring up the assistant dialogs if it finds existing settings
files.
[Scott McGuire answers the last question]
>-I've been reading up on the old/new table of contents situation and the
>documentation (and readme file) says that the option under
>Settings>Miscellaneous for use old-style .toc files is turned on by
>default, but I don't think that mine was. When I initially started up
>Eudora after installing it, I got the message, "Mailbox Out has been
>changed since it's table of contents was created. Do you want to use the
>old style table of contents or create a new one?" Has it been your
>experience that it's turned on by default?
Yes, if a user is *upgrading* and using their old Eudora 2 settings file
with Eudora 3, our experience has been that it's on.
If a user is upgrading from Eudora 2 to Eudora 3, that is, they already
have existing mailboxes and settings, the "Use old-style .toc files" will
be turned on when they use their old settings and mailboxes with Eudora 3.
(We've tested this.) The message you received may have been unrelated -
did you check to see what the setting actually was?
However, the settings file that is installed by the MIT Eudora 3 installer
has "Use old-style .toc files" turned off because it is a *new* settings
file. So, if a user is doing a completely new install of Eudora (because
they haven't used it previously), it will be off by default. Also, if you
start up Eudora 3 by clicking on the application, it will use the new
settings file the Installer put in the System Folder, even if you have
existing ones on your hard disk, and "Use old-style .toc files" will be off
as well.
The Eudora manual says that "use old-style .toc files" is on by default *if
you're upgrading* from Eudora 2 to 3, which is the case with our installer
as well. It's just that a *new* Settings file will have it off by default.
