On Fri, 14 Sep 2001 19:03:03 +0200 (CEST), [EMAIL PROTECTED] (Richard Menedetter)
wrote:
> Hi
> 14 Sep 2001, "Samuel W. Heywood" <[EMAIL PROTECTED]> wrote:
>>> TM> but didn't really know if that extended to .BAT.
>>> it does not
>>> C:\4.BAT [1] Invalid path "MZ @k@a@- /,"
> SH> The above indicates that a part of the program actually ran,
> SH> i.e., a part of the program designed to output an error message.
> no
> the error is given by your command shell (usually command.com)
> batch files are extremely simple interpreted files.
> Every line contains a command a remark (; rem or empty line)
> the above error shows that your command shell tries to execute the command
> given in the first line. But it fails, because there's no valid command.
O.K. I can agree with this argument because in this case you are
using 4.COM as your command shell.
<snip>
>>> com and exe are executed.
>>> bat is INTERPRETED !!!
> SH> As an experiment I re-named DR.COM to DR.BAT and found that part of
> SH> the program would still run!
> How did you find that ??
> SH> It ran the part of the program that identifies itself to the user.
> copy the output here ...
Here is a screen capture:
-----------------------------------
C:\UTIL>ren dr.com dr.bat
C:\UTIL>dr
C:\UTIL>�
DIRMAGIC (C) Copr. 1988 ZD Co
Command or filename not recognized
C:\UTIL>Michael J. Mefford
Command or filename not recognized
C:\UTIL>
-----------------------------------
BTW, Michael J. Mefford is the program author, and his name appears
in the program output when the program is run normally and named as
DR.COM
> I'm sure that it did *NOT* run, but that your command.com generated some
> error.
> (command.com WILL echo the first line to screen, but this does not indicate
> that the program itself run ! this is simply part of the error message)
Part of the program ran. My command.com did generate some kind of
error, "Command or filename not recognized", but it is obvious that
the other output did not come from command.com. In this case it was
not just the first line that was echoed to the screen. After the
first error was generated, command.com tried to continue to process
the program instructions. Then the name of the program's author
was sent to the screen as another output. Next I got another error
from command.com, "Command of filename not recognized". Then it
exited from the program.
Sam Heywood
-- See our Big Gizmotimetemp at
-- http://banners.wunderground.com/banner/gizmotimetempbig/US/VA/Mt_Jackson.gif
