[251] in installers
Re: Log 155083
daemon@ATHENA.MIT.EDU (Bryant C. Vernon)
Mon Oct 11 15:33:05 1999
Message-Id: <199910111932.PAA29402@melbourne-city-street.MIT.EDU>
Date: Mon, 11 Oct 1999 15:32:42 -0400
To: "Stephen D. Dowdy" <sdowdy@mit.edu>,
Jonathan McIndoe Hunt <jmhunt@mit.edu>,
MIT Computing Helpdesk <computing-help@mit.edu>, installers@mit.edu,
sendpubs@mit.edu
From: "Bryant C. Vernon" <bcvernon@MIT.EDU>
Cc: helpsuper@mit.edu
In-Reply-To: <199910082156.RAA12043@melbourne-city-street.MIT.EDU>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Hi,
Just so you know, the reason that you receive the message stating that you
have a second instance of eudora running is that the owner.lok file in your
eudora settings folder still exists. Because Eudora crashed, it did not
have a chance to delete that file--a standard cleanup process eudora
executes when it exits gracefully. To fix the problem, you can either
delete that file manually and start Eudora 4.02 or you can surprisingly
click the "x" (i.e. close window) in the top right hand corner of the
warning message, and Eudora will start normally. This problem has existed,
as far as I can tell, since the release of 4.0. I do not know whether
Eudora knows about (hahaha) or plans to correct this problem.
Bryant
P.S. If the OS will not let you delete the owner.lok file--i.e. gives you a
sharing violation error-- launch the task manager (NT), click the processes
tab, and kill the "hidden" instance of Eudora.
P.P.S. Does anyone know how to automate these processes so that the end
user does not have to do them? What I am thinking of is a way to check for
the existence of the owner.lok file, attempt to delete it, catch the
sharing violation error if necessary, and finally, prompt the user for
authorization to kill the current (or hidden) session of eudora.
At 05:56 PM 10/8/99 -0400, Stephen D. Dowdy wrote:
>Just as an aside on Eudora 4.0.2. I installed the software after Theresa
>Regan asked several folks to test the installer. I've been using Eudora
>4.0.2 for a couple of weeks now. Just so the help desk can prepare since I
>haven't found a solution.... there are two issues that I've found with this
>version.
>
>1. At times, the software has frozen and the application simply
>disappears. That is, I get no GPF or any warning... it simply vanishes
>after I've hit the "send" button. When I relaunch the application, I get
>the message asking if I want to terminate the remote instance. Every time
>I say to close the remote instance, I get Dr. Watson. If I say "i'll take
>the consequences" to the prompt, I get Dr. Watson. The only way I've ever
>got around this... is to launch my version 3.0.5... it connects with no
>problem. Then I close v 3 and relaunch version 4 and it connects just
>fine. I installed the software on another persons machine in this office.
>He has had the same problem.
>
>2. When using the Directory service and I locate the individual... the
>"To:", "bcc:", and "cc:" buttons are dimmed. In prior version, you could
>click on the "To:" button after performing a directory search and the
>e-mail address would move into a new message.
>
>Don't need to start a case... just a bit of ovservation and perhaps someone
>might want to look into these before the official roll-out begins. I'm
>using NT, SP3.
>
>
>At 05:25 PM 10/08/1999 , Jonathan McIndoe Hunt wrote:
>>Eudora 2.2 is still the latest released and supported version of Eudora for
>>Windows. The documentation will be updated when we release 4.0.2.
>>Tentative plans are to release Eudora 4.0.2 next Friday.
>>
>>I just retrieved the 2.2 installer from net-dist just fine from the win9x
>>tree. I noticed that the current winNT tree is missing it.
>>
>>ftp://net-dist/mit/win9x/email/eudora/current/
>>
>>-Jonathan
>>
>>At 05:04 PM 10/8/1999 -0400, MIT Computing Helpdesk wrote:
>>
>>>hi,
>>>
>>> we received a call from a client about no longer being able to
>>> get Eudora
>>>2.2 from net-dist and that the Eudora webpage was not updated correctly to
>>>reflect that Eudora 2.2 is no longer available. Only Eudora 4.02 was
>>>available under the 'test' directory. Explained that we are probably
>>>through a transition stage of launching Eudora 4.02, but she was not
>>>pleased with the confusing instructions and missing files, and would like
>>>to make her comments known. As per client's request, I am forwarding this
>>>to both installers@mit.edu and sendpubs@mit.edu so that you might be aware
>>>of the problem. Attached is a copy of the log with more details. Thank you,
>>>
>>>Jessica Tan
>>>jesstan@mit.edu
>>>Student Consultant
>>>Computing Helpdesk.
>>>
>>>-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>>> Helpdesk Log #155083 (NEW)
>>>-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>>> Client: RACHEL MORTON
>>> Phone: 3-5612
>>> Email: RACHEL@MIT.EDU
>>> Dept: NUCLEAR ENGINEERING, DEPARTMENT OF
>>> Address: NW12 232
>>> Title: MANAGER, COMPUTER FACILITIES
>>>
>>> Summary: installing eudora and mink - confusing webpage.
>>>
>>> Hardware: PC
>>> OS: WindowsNT
>>> Software: Eudora
>>>
>>> Method: Voice
>>> Created: By jesstan on 10/08/99 16:25
>>> Modified: By jesstan on 10/08/99 16:25
>>>
>>>-----------------CASE HISTORY-----------------
>>>
>>>
>>>--- Entry: 10/08/99 @ 4:33 PM - jesstan ---
>>>Client is trying to install eudora and mink on a new winnt machine.
>>>
>>>She has the following complaints about our eudora webpage:
>>>
>>>- no eudora 2.2 in the 'current' net-dist directory when she tries to
>>>download it from the webpage http://web.mit.edu/is/help/eudora
>>>- eudora 3.0 in the 'old' net-dist folder is non-existent
>>>- only downloadable version was eudora 4.02 in the 'test' directory
>>>
>>>Suggested that perhaps we are in the process of transitioning and updating
>>>our webpages but client feels strongly that we should update the webpage in
>>>one go. there should not be outdated links or information on the webpage -
>>>confused her and wasted her time chasing for the right software.
>>>
>>>anyway, she installed eudora 4.02, didn't work. i found out that it's
>>>because she has specified to use binary 16 libraries in the kerberos
>>>installation. told client to unmink and reinstall mink again, this time
>>>using 32-bit binaries instead.
>>>
>>>also sending email to installers about the comment on the eudora webpage.
>>>-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>>>Log info extracted on 10/08/1999 16:40
>>
>
