[18] in installers

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

Re: Let's preserve the name SETUP.EXE

daemon@ATHENA.MIT.EDU (Paul B. Hill)
Tue Mar 4 19:31:39 1997

Date: Tue, 04 Mar 1997 19:30:49 -0500
To: Jim Repa <REPA@mitvma.mit.edu>, jsaylor@MIT.EDU
From: "Paul B. Hill" <pbh@MIT.EDU>
Cc: INSTALLERS@MIT.EDU

At 06:27 PM 3/4/97 EST, Jim Repa wrote:
>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.
>

John's point is valid when the product comes on its own media or comes in a
zip file which needs to be expanded before running the installer. However
this is not the common practice when the installer, as an executable, is
downloaded to a machine.

As an example the installer for Microsoft Internet Explorer 3.01 is
something like msine_301.exe.

This becomes especially important when a user may be browsing and
downloading several installers in one session and saving them all to their
default "save to disk" directory.

Paul

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