[146] in installers

home help back first fref pref prev next nref lref last post

Re: eudora 3 for PCs

daemon@ATHENA.MIT.EDU (Alicia Allen)
Tue Oct 21 14:04:13 1997

Date: Tue, 21 Oct 1997 14:04:45 -0400
To: installers@MIT.EDU
From: Alicia Allen <iggy@MIT.EDU>
Cc: support-desktop@MIT.EDU

Hi,
The last I heard about the Eudora 3 for PCs release was that support feels
that it is ready to go, even without the MINK installer.   We were
wondering if there is anything holding it up besides the mink installer.
We are getting many requests for this and many people don't understand that
it hasn't been released yet, even within IS.

Can you please give us some sort of timeframe as to when it will be
released?  Also, are there any other issues holding it up besides MINK?

thanks,
alicia



>X-Sender: smyser@hesiod
>Date: Wed, 01 Oct 1997 15:26:48 -0400
>To: Alicia Allen <iggy@MIT.EDU>, "Paul B. Hill" <pbh@MIT.EDU>,
>        installers@MIT.EDU
>From: Rob Smyser <smyser@MIT.EDU>
>Subject: Re: eudora 3 for PCs
>Cc: jjv@MIT.EDU, mdavies@MIT.EDU
>Mime-Version: 1.0
>
>I think that Mark's experience with the mink files may have been caused by
>mixing the new mink-installed DLLs with a copy, perhaps, of kerb16 or
>kclient.dll in the eudora directory on the PC.  Eudora would need to call
>kerberos, would find the older kclient in its directory and use it, and
>then collide with incompatible DLLs in the c:\net\mit directory.
>
>   Fresh installs of Mink have not had this problem (i.e., on my machine or
>the many others I have installed).  I think Mark now agrees with me that
>this may be the root cause of these difficulties.  The installer may not do
>as good a job as it could in tracking down all the older binaries all over
>the system, but that's not its main job.
>
>   Everyone on the support side of the Eudora team think that the product
>is ready to go and has been for quite a while.
>
>   Is there a big hold-up about mink caused by ESANDI incompatibilities?
>That was what I understood to be causing whatever holdup there might now be.
>Phyllis Galt has new Eudora 3 web pages ready to go.  She had been waiting
>for Eudora to appear in net-dist, and apparently Paul was avoiding doing
>that because of the ESANDI glitch and administrivia within the installer
>that Paul asked JJV to take care of.
>
>   Is there anything else holding it up from your perspective Paul?
>
>Rob
>
>
>
>
>At 02:59 PM 10/1/97 -0400, Alicia Allen wrote:
>>I'm not clear what this has to do with releasing Eudora 3,  these binaries
>>get distributed with Eudora 2 as well, correct?   Why hold up the new version
>>of Eudora if these binaries are being distributed anyhow?
>>
>>Are these problems being worked on?  I have not heard anything about progress
>>on this front.
>>
>>Alicia
>>
>>
>>At 2:27 PM -0400 10/1/97, Paul B. Hill wrote:
>>>According to Mark Davis from the help desk there is a major problem with
>>>the Kerberos binaries installed by mink and that he recommends that users
>>>install the old binaries instead. Given that helpsuper@mit.edu was cc'd on
>>>that mail and that we heard no counter opinions from anyone on that list we
>>>had assumed that this was the help desk's opinion and that those problems
>>>needed to be fully resolved.
>>>
>>>At 01:46 PM 10/1/97 -0400, you wrote:
>>>>Hi,
>>>>What happenned with this?
>>>>I thought there were just a few minor changes to make.
>>>>We've been getting more and more requests for it.
>>>>A timeline would be great.
>>>>
>>>>Thanks,
>>>>Alicia
>>>>
>>>>
>>>>
>>>>Alicia Allen
>>>>iggy@mit.edu                                (617) 253-0191
>>>>Computing Help Desk                      MIT, 11-226
>>>>
>>>>
>>>>
>>
>>
>>
>>
>>Alicia Allen
>>iggy@mit.edu                                (617) 253-0191
>>Computing Help Desk                      MIT, 11-226
>>
>>
>>
>



Alicia Allen
iggy@mit.edu                                (617) 253-0191
Computing Help Desk                      MIT, 11-226



home help back first fref pref prev next nref lref last post