Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!boyer
From: boyer@iuvax.cs.indiana.edu
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: TSR to Ignore commands
Message-ID: <120800006@iuvax>
Date: 21 Aug 89 00:31:00 GMT
References: <2841@ndsuvax.UUCP>
Organization: Indiana University CSCI, Bloomington
Lines: 21
Nf-ID: #R:ndsuvax.UUCP:-284100:iuvax:120800006:000:884
Nf-From: iuvax.cs.indiana.edu!boyer    Aug 20 19:31:00 1989


lhf@aries5.waterloo.edu writes:

>In article <120800005@iuvax> boyer@iuvax.cs.indiana.edu writes:
>>
>>Try using a TSR that gives you alias capabilities (like DOSEDIT etc.)
>>and alias the unwanted commands to something else.  Perhaps a batch
>
>This would only work if the command *begins* the input line (ie. no spaces)


Spaces are not a problem.  Dosedit can correctly alias a command with 
preceding spaces.  A way to actually get around the aliasing feature is to
include a path to the command.  For instance, /dos/format.  It depends
on the purpose the original poster had in mind.  If the system must be fail-
safe against a malicious user then a new operating system is needed.
If he just wants to prevent the casual uninformed user from doing something
to the system then this solution may work.  Of course, removing format.com
from the path would also work :-)

Dave Boyer