Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!plx!slvblc!dick
From: dick@slvblc.UUCP (Dick Flanagan)
Newsgroups: comp.sys.ibm.pc
Subject: FOLLOW-UP: Microsoft C V5.1 Setup Warning
Message-ID: <1468@slvblc.UUCP>
Date: 27 Apr 88 23:37:27 GMT
References: <1455@slvblc.UUCP>
Sender: uupc@slvblc.UUCP
Reply-To: slvblc!dick@ucscc.UCSC.EDU (Dick Flanagan)
Organization: SLV Systems Group, Ben Lomond, California
Lines: 45
Keywords: stupid careless write-protect backup shucks darn
Summary: It uses first directory it finds in your PATH
Disclaimer: none


In article <1455@slvblc.UUCP> I wrote:
> About 30 minutes ago I destroyed several critical program files, including
> the almighty setup.exe file, itself, on the Microsoft C V5.1 installation
> diskettes.

> One of the installation directories you are prompted to enter, very
> plainly declares that its default is to install in directory '[.]'

> Well, folks, when it says it defaults to '.' it's not kidding one little
> bit!  It doesn't mean that it defaults to something reasonable like 'C:.'
> It honest-to-God means that IT DEFAULTS TO INSTALLING OVER THE INSTALLATION
> DISKETTES, THEMSELVES!

> Even though I am 100% to blame for not following the cardinal rule of
> write-protecting all original diskettes, I really do wish Microsoft
> wouldn't offer a default that, if accepted, destroys the very files you
> are trying to install.

As I re-read the setup.doc file in the glaring light of day, the following
paragraph jumped out at me with new significance:

        Note that when SETUP suggests a default response for each
        of the installation directories, it uses the first path
        defined by the PATH environment variable in your environment.

Well, well, well.  I do, indeed, begin my PATH with a directory of '.',
so at least now I know where that damned '[.]' came from.

That also means that anyone whose PATH begins with '.', 'A:', or '\',
will have those same dangerous defaults offered to them by the setup
program.  So, while I still don't blame Microsoft for my lost files,
I will modify my "wish" somewhat:  if they are going to use an unknown
directory obtained from the user's environment, I wish they would at
least check that it doesn't refer back to the installation diskettes,
themselves.

         WRITE-PROTECT THOSE ORIGINAL DISKETTES, FOLKS!

Dick

--
Dick Flanagan, W6OLD                         GEnie: FLANAGAN
UUCP: ...!ucbvax!ucscc!slvblc!dick           Voice: +1 408 336 3481
Internet: slvblc!dick@ucscc.UCSC.EDU         LORAN: N037 04.7 W122 04.6
USPS: PO Box 155, Ben Lomond, CA 95005