Hi

14 Sep 2001, "Samuel W. Heywood" <[EMAIL PROTECTED]> wrote:

 SH> It appears that command.com tried three times to execute
 SH> the program.
Haven't you read my previous message ?!?

batch files are interpreted, like basic, perl, php whatever.

This means that an interpreter (command.com) reads a line, echos it to
the screen and interprets the commands in it.
then it takes the next line, as long as it reaches the end of file, or non
ascii characters.

 SH> Each time an error message was returned by
 SH> command.com.  The first two lines of DR.BAT were output to
 SH> the screen, not just the first line.  So, it appears to me
 SH> that some parts of the program actually ran.  They did run,
 SH> although with some problems and difficulty.
no

example: ricsi.com
richards programm
richard menedetter
<gibberish machine code starts here>

if you rename it to .bat command.com thinks that it is a batch file, and
interprets the text.

It reads the first line.
echos "richards programm"
looks at the command (everything before whitespaces or end of lines)
in this case richards.
This is no valid command - issue an error
continue in the next line

echo "richard menedetter" to screen
richard again is no valid command -> error

in the next line long gibberish starts -> command.com aborts

that is it ... really not sooooooo hard to understand is it ???

To put in in simple words:
In batch files *NO* machine code from .bat files is executed !!!
Instead the file is interpreted line by line.

if you put a @ in front of a line, than it is NOT echoed to screen.
If you put @echo off in the first line, no command will be echoed to
screen.

 SH> When the file is renamed to DR.COM, and the "@" in the first
 SH> character is removed, the program output looks like this:
This is absolutely irrelevant.

 SH> Sam Heywood

CU, Ricsi

-- 
|~)o _ _o  Richard Menedetter <[EMAIL PROTECTED]> {ICQ: 7659421} (PGP)
|~\|(__\|  -=> All gamblers die broke! <=-

Reply via email to