🚀 go-pugleaf

In article <v3gq0yl@lynx.unm.edu> moeur@chtm.eece.unm.edu (Bill Moeur) writes:
>In article <Bxn4nE.8IH@news.cso.uiuc.edu> jlamb@ux4.cso.uiuc.edu (Jeffrey Richard Lamb) writes:
>
>>to kill machines. I'm not trying to write a virus. I made a bet with
>>a friend that the copy command (or any other internal dos command)
>>could be "turned off." What I want to do is simple. I want dos to access
>>a file called "copy.bat" whenever anyone types in a copy command. The
>>problem is that dos always checks for internal commands (copy) first,
>>so dos never even looks at copy.bat, it just declares invalid number of
>>parameters. I'm sure this can be avoided, but how? Again, I know it sounds
>
>If you're using DOS 5.0, try using doskey to alias the copy command to call
>your batch file which is called something beside copy.bat.
>for example:
>     DOSKEY copy=copy2 $1 $2

My freshman year, we did something like this to a friend's computer
by using DEBUG to change the name the DIR command in COMMAND.COM to
DXR (or whatever), and then creating a hidden batch file in the
path called "DIR.BAT" that contained one line:
 
@DIR C:\

so that whenever he did a DIR, he only saw the contents of the root
directory.  It was quite funny.  Anyway, you could change the COPY
command in a similar manner, albeit this is not a general solution
to the problem.
-- 
Andrew White                  |  Dod #0584
sabre@quantum.sas.upenn.edu   |  '82 Honda Sabre v45