Message-Id: <199706012140.XAA20510@magigimmix.xs4all.nl>
From: "yeep" <yeep AT xs4all DOT nl>
To: "Mike A. Harris" <mharris AT blackwidow DOT saultc DOT on DOT ca>,
        "Steven Ehrbar" <ehrbar AT oeonline DOT com>
Cc: <opendos AT delorie DOT com>
Subject: Re: cAsE sensitivity
Date: Sat, 31 May 1997 10:13:22 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Precedence: bulk

> If you throw a confirm into it, you could still accidentally hit
> enter and toast something, only then realizing and being unable
> to stop it.  Also, what happens in a batch file?  For example:
> 
> @ECHO OFF
> DELTREE \ASDF

Echo off doesn't prevent deltree from asking for confirmation.
Nor does ik prevent any other "dangerous" command from asking for
confirmation.
At least in M$-DOS/. 
 
> In this case, the batch file may need to be ran unattended, such
> as on a BBS, or something.  A batchfile that hangs expecting user
> input could bring down the BBS, or cause countless other
> problems.

Okay, Mike..
Go to C:\ and type "echo y | deltree *.*"
And just sit back and relax :-))
 
> > And people who edit a config.sys file without knowing what they're
doing
> > deserve trouble, while people who do know there might be filename
conflicts
> > when they switch from sensitive to an insensitive option and will be
> > prepared to deal with it.
> 
> My proposed IQ test would circumvent someone from choosing
> options that could cause problems.  :o)

I don't think the test is such a good idea..
I failed it :-(, at least I knew the last question :-)) 
We should keep asking for confirmation, endlessly, so the only way to get
past the confirmation screen is a special keycombo which is supplied in the
textfile: "technical.doc", which should start with the asm-source of dir or
something, so it scares off lusers.
	
	Yeep