Path: utzoo!utgpu!watserv1!watmath!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!think.com!mintaka!bloom-beacon!eru!hagbard!sunic!mcsun!cernvax!chx400!ugun2b!ugsc2a!fisher
From: fisher@sc2a.unige.ch
Newsgroups: comp.sys.ibm.pc.misc
Subject: Re: Disabling DOS internal commands ?
Message-ID: <1991Jan25.103718.366@sc2a.unige.ch>
Date: 25 Jan 91 08:37:18 GMT
References: <1991Jan23.120842.3032@newcastle.ac.uk>
Organization: University of Geneva, Switzerland
Lines: 17

In article <1991Jan23.120842.3032@newcastle.ac.uk>, A.C.G.Saunders@newcastle.ac.uk (Aidan Saunders) writes:
> Is there any way of disabling DOS internal commands ?  Alternatively
> can DOS be persuaded to execute a program of the same name as a DOS
> internal command without explicitly specifying a path ?

Several people replied:
"Run a patched version of COMMAND.COM, in which the "COPY" string has been
changed."

If you use some COMMAND-enhancer (I'm thinking of ANARKEY), or a COMMAND
replacement (4DOS comes to mind), the easiest solution is to work with
aliases:  transparent, easy to understand and to maintain (and no worries
whether binary patches of COMMAND.COM violate it's copyright :-)

Just an opinion...

Markus Fischer, Dpt of Anthropology, Geneva CH