Path: utzoo!attcan!uunet!spool2.mu.edu!sdd.hp.com!usc!snorkelwacker.mit.edu!bloom-beacon!eru!hagbard!sunic!news.funet.fi!funic!santra!santra!iisakkil
From: iisakkil@niksula.hut.fi (Mika R Iisakkila)
Newsgroups: comp.sys.ibm.pc.misc
Subject: Re: Disabling DOS internal commands ?
Message-ID: <IISAKKIL.91Jan24124743@colossus.hut.fi>
Date: 24 Jan 91 11:47:42 GMT
References: <1991Jan23.120842.3032@newcastle.ac.uk>
Sender: news@santra.uucp (Cnews - USENET news system)
Organization: Otaniemi Underground Broadcasting System
Lines: 12
In-Reply-To: A.C.G.Saunders@newcastle.ac.uk's message of 23 Jan 91 12:08:42 GMT

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 ?

	Use a binary editor and patch the command names in command.com
into something else. You can't change the lenght of the command names,
but changing 'copy' into 'ypoc' or something should fool the users for
a while... The command name string arrays are near the end of
command.com and easily found. You might probably want to patch a
renamed copy of command.com and use the config.sys's SHELL command.