That is some difference!   Ok, so we all use CALL from now on, Right?

Incidentally, CALL can be used to invoke PROGRAMS (.COM .EXE) just as
well as BATCH files, and we never have to worry weather the thing we
are CALLing is a .BAT, .COM or .EXE!

I have not seen just how far down the tree you can go with CALL, but I
guarantee its further than with COMMAND/C due to the low memory overhead.

Incidentally, someone should explore (after class) whether you can in
fact install TSR programs this way, without leaving great gaps in memory!

It would also seem that we could use CALL to ensure that BATCH files get
the SAME copy of the environment, allowing us to return values from the
called module to the caller via SET statements.  This just does not
work with COMMAND /C since the called module gets a COPY of the environment
which is discarded on return!