[17] in installers

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

Let's preserve the name SETUP.EXE

daemon@ATHENA.MIT.EDU (Jim Repa)
Tue Mar 4 18:44:54 1997

Date:         Tue, 04 Mar 97 18:27:56 EST
From: Jim Repa <REPA@mitvma.mit.edu>
To: Jerry Isaacson <GII@MIT.EDU>, Lee <RIDGWAY@MIT.EDU>
Cc: INSTALLERS@MIT.EDU

Jerry,

In light of John Saylor's comments (e.g., "Installers are always named
SETUP.EXE..."), I think we should avoid diverging from standard Windows
practice.  Let's continue to call the Ksign installer SETUP.EXE.

Lee, on the Web page for the Windows Ksign installation, you might
say something like:
"Create a temporary directory where you'd like to temporarily save
the installer file SETUP.EXE.  Click on 'Install Ksign', and the
file SETUP.EXE, and you will be prompted to choose a directory to which
SETUP.EXE will be downloaded...  To install Ksign and its related files,
launch SETUP.EXE.  Make sure you launch the one that was just downloaded;
most Windows installers are called SETUP.EXE."
I don't think we have to tell the user whether or not to overwrite
a pre-existing SETUP.EXE file in his chosen directory; armed with the
knowledge that most Windows installers are called SETUP.EXE, he should
be able to make his own decision.

                                    Jim

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