On Thu, 03 Jul 2003 08:45:31 -0400, Tim Slattery <Slattery_T@bls.gov>

Copy doesn't exist as a stand-alone file; it's an internal command
coded within Command.com (or the engine files called by Command.com)

That's why you can't find it as an .exe, .com, .bat, .pif, .scr etc.!

Unless you are running NT or WinME (which may skip or don't process
such commands in Autoexec.bat, respectively), Copy should work in
Autoexec.bat, or any other .bat file - but there are limits to what
Copy can do (hidden files, directories); XCopy may be what you need.

Make sure also that it's C:\Autoexec.bat you are editing, and not a
file of a different name or an Autoexec.bat in a different directory.
Unless it's a WinStart.bat in the Windows base directory, no other
.bat are run automatically when Windows starts unless they are
specifically called from the startup axis or Tasks.

Also, follow the login in your Autoexec.bat to make sure the line you
are adding actually gets interpreted (i.e. isn't stepped-around by a
GoTo, or is missed because a preceding line runs a .bat without using
the Call command, so that it never returns)

Finally, bear in mind that many places where commands can be entered
and run (e.g. Start, Run, or Tasks, or file associations) will not use
Command.com and thus not support Command.com's internal commands.

In such cases, use Command.com /C Copy... to have Command.com raun the
command and then exit, or Command.com /K Copy... to have Command.com
run the command and then stick around.

  I'm baaaack!