[139] in installers

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

Re: eudora 3 for PCs

daemon@ATHENA.MIT.EDU (Mark Davies)
Wed Oct 1 20:12:32 1997

Date: Wed, 01 Oct 1997 20:12:28 -0400
To: Rob Smyser <smyser@MIT.EDU>, Alicia Allen <iggy@MIT.EDU>,
        "Paul B. Hill" <pbh@MIT.EDU>, installers@MIT.EDU
From: Mark Davies <mdavies@MIT.EDU>
Cc: jjv@MIT.EDU

After trying some various configurations of this, I have found that this
seems a very reasonable explanation.  After using the installer on brand
new machines, I have encounter few problems.  However, when the machine at
one time had the old kerberos files on it, a problem sometimes occurred.  I
don't really see this as being a reason to hold up the release of Eudora 3.
 I agree with Alicia that if it comes down to it, Eudora 3 should be
released separate of the new Mink installer, as Eudora 3 is compatible with
the old Kerberos binaries.  If there are other problems, it is
understandable that the installation be delayed, but I do not believe that
the release should be delayed simply because of the Mink installer.

Mark

At 03:26 PM 10/1/97 -0400, Rob Smyser wrote:
>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
>>
>>
>>
>

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