[62] in installers
Re: Kclient in the extensions folder
daemon@ATHENA.MIT.EDU (Marshall Vale)
Tue May 6 09:48:52 1997
In-Reply-To: <v03020900af93bfabf334@[18.81.0.181]>
Resent-From: mjv@MIT.EDU
Date: Tue, 6 May 1997 09:49:04 -0400
To: Computing Help Desk <mac-help@MIT.EDU>
From: Marshall Vale <mjv@MIT.EDU>
Cc: installers@MIT.EDU
>Log Number:
>76064 (Pending) Summary: Eudora 3.0.2 didn't seem to work.
>
>Msg From: Jenny Ayla Phone: 3-4926 Email: jenny@mit.edu
>juan carlos becerra computing helpdesk
>A client installed Eudora 3.0.2 today, but she could not get Eudora to work.
>She mentioned that after installing and restarting the machine, it would
>complain about extensions conflicts, kclient.
This is a sign that a former version of KClient still resides in the
Extensions folder. If a user reports this symptom, you should immediately
look in the Extensions folder for any file with KClient or "Kerberos Client"
in its name and disable it (note that the Kerberos Telnet plugin is ok
and does not cause the conflict). After rebooting, try the KClient control
panel and verify that things are working.
> After some fiddling she put the
>Kclient control panel in the extensions folder and it all worked. Feature or
>bug?
The current Eudora installer (r2.6) has a minor blindspot with regards to
certain earlier KClients. Check http://web.mit.edu/installers/www/
for a version history of the Eudora 3 Mac installer that lists these
situations.
>about it. In the mean time, client took out Kclient from the control panel and
>put it in the extensions folder, and restarted computer. When i got back to
>her, Eudora was already checking her email fine. Needless to say i was
>baffled. Kclient (control panel) was in extensions folder. If she clicked on
>it, it would come up as it normally does when you select it from the control
>panel.
The control panel works as expected since control panels are typically
just extensions with a user interface. This person's Mac is working like
this probably because extensions are loaded before control panels. By
moving the KClient control panel into the extensions folder, it is being
loaded before the older version. With it in the control panels folder,
it loads after the older version in the extensions folder whereupon the
newer KClient fails.
I would take a guess and say that there is still and older KClient
in the extensions folder, perhaps with the name Kerberos Client. Try
looking for, and removing such, afterwards moving KClient 1.6.2 back
to the control panels folder. The Kerberos Telnet Plug-in would not
cause this behaviour.
And as a quick note:
>So we
>enabled MacLeland and restarted computer. It upset computer, gave us a bomb
>and a message saying there was an extension conflict with Kclient.
If MacLeland really caused the Mac to crash with a bomb dialog (thus
forcing a restart), that might be an indication that something else is
seriously wrong with the computer (most likely extensions conflict,
corrupted system file, munged file system).
Marshall
Marshall Vale | mjv@mit.edu | "Das Schicksal des Mannes ist knusprig
Mac Dev Tinkerer, IS | Massachusetts Institute of Technology | und lecker."
