> I'll still have to put them in because I put the bat files and
 > things in various roots.

 NP> Untidy! Stick'em all in c:\BAT directory or as one comic said
 NP> "I use C:\BELFRY" 

  Then I'd need a BAT file to put c:\bat on the path... etc .

 NP> The idea of a BAT file is to remove the need to do repetitive
 NP> thinking, so i make them as intelligent as I possibly can. 

  My idea of a bat file is to save me some typing... that's all.

 > Now I'm into Pascal, it's just as easy to write a complete EXE,
 > and call *that* from a simple BAT file.

 NP> The last job I did was done like that. A BAT file and an EXE
 NP> that had at least 20 GOTOs' in it :-) It does a validation of
 NP> all the COM EXE etc files on each HD and screams if one has
 NP> altered internally. 

  That's a good idea. I never trust a burglar alarm I haven't made
myself, and the same applies to viruses. Some clever bastard can
always find a way around the well-known alarms and locks.

  How do you check the files? It would be easy enough to do your own
CRC.... just use a different seed.

Regards,
Bob


___ Blue Wave/QWK v2.12
@EOT:

---