This document covers revision 1.0 of the installer.

Table of Contents

Packages

Guide To Files Table

What the Installer Does

Packages

There are four packages that the user can install.

Easy Install:

Installs NCSA Telnet 2.7b4, Telnet Preferences for MIT, KClient (Kerberos 4), and the Kerberos Telnet Plugin.

Custom Install:

* "KClient" package - installs the KClient (Kerberos 4) files.

* "NCSA Telnet 2.7b4" package - installs the NCSA Telnet app and support files, Telnet Preferences for MIT, and the Kerberos Telnet Plugin.

* "Kerberos Telnet Plugin" package - installs just the Kerberos Telnet Plugin.

[In theory there should be a "Kerberos 5" package which installs the Kerberos 5 files (GSSLib, CNSConfig, etc.). However, the Kerberos 5 package has been deleted, even though placeholder files are still in the installer - there's no way for the user to install them.]

The "Easy Install" and "KClient" packages are set to "restart after installing" to force the installer to quit any other programs that are running, and the installer is set to "Force Restart" so that a restart is required when it's done installing.

Guide to Files Table

File		Install to:	Packages	Replace	Before installing	After installing	Gestalts
Move Action Item: KClient (from Extensions to Trash) (moves all matching items)		---	Easy Install, KClient
Move Action Item: KClient (from Extensions (disabled) to Trash) (moves all matching items)		---	Easy Install, KClient
Move Action Item: Kerberos Client (from Extensions to Trash) (moves all matching items)		---	Easy Install, KClient
Move Action Item: Kerberos Client (from Extensions (disabled) to Trash) (moves all matching items)		---	Easy Install, KClient
KClient		Control Panels	Easy Install, KClient	if Newer		ftp
Rename action item: Kerberos Client Preferences (to Kerberos Client Preferences.bak)		---	Easy Install, KClient
Kerberos Client Preferences		Preferences	Easy Install,KClient	Always		ftp
GSSLib		Extensions	none	if Newer		ftp
krb5.ini		Preferences	none	if Newer		ftp
Move Action Item: GSSLibrarySAP (from Extensions to Trash)		---	none
Move Action Item: K5Logout (from anywhere to Trash)		---	none
Kerberos Utilities (folder)		Install Folder	none
CNS Config-SAP		Kerberos Utilities	none	if Newer		ftp
K5Logout		Kerberos Utilities	none	if Newer		ftp
Alias Action Item: K5Destroy		ShutDown Items	none				System 7.5 or Greater
NCSA Telnet 2.7b4 (folder)		Install Folder	Easy Install, NCSA Telnet
2.7b4Release Notes		Install Folder	Easy Install, NCSA Telnet	if Newer		ftp
NCSA Telnet 2.7b4 (fat)		Install Folder	Easy Install, NCSA Telnet	if Newer		ftp
US-EMACS		Install Folder	Easy Install, NCSA Telnet	if Newer		ftp
NCSA Telnet Readme		Install Folder	Easy Install, NCSA Telnet	if Newer		ftp
Put In Preferences (folder)		---	Easy Install, NCSA Telnet
NCSA Telnet Preferences		Preferences	Easy Install, NCSA Telnet	Never		ftp
Put in Extensions (folder)		---	Easy Install, NCSA Telnet, Kerberos Telnet Plugin
Kerberos Telnet plugin		Extensions	Easy Install, NCSA Telnet, Kerberos Telnet Plugin	if Newer		ftp

What the Installer Does

(1) For info about the KClient and Kerberos 5 files, see the Kerberos Installer Docs - no changes to behavior have been made here. KClient is part of the Easy Install.

(2) The files in the "NCSA Telnet 2.7b4" folder are installed on the volume specified by the user. There are no special cases or unusual circumstances.

(3) Put in Preferences folder - this folder itself is not installed (it's marked as a placeholder). Inside is NCSA Telnet Preferences, a version of the Telnet Preferences with MIT-specific configurations. Since the user may have their own preferences with their own list of sessions set up, and the tweaks we've made aren't critical, we won't replace an existing file.

(4) Put in Extensions folder - this folder itself is not installed (it's marked as a placeholder). The Kerberos Telnet Plugin inside it is installed to the Extensions folder. (This file can also go in the same folder as the Telnet app, but if we put it here TN3270 can share it too.)

(5) For the final build of the installer, we edited the STR# resource ID 1000, item #26 to be "NCSA Telnet Installer Log File" (couldn't include the version number because that made the name too long to be a Macintosh filename and then no log file was created at all).

All files are set to execute the FTP code resource after they're installed, since only aliases are in the installer binary.

Also see the NCSA Telnet Installer Version History for details about the changes the Telnet installer has gone through.