  

  DBGS2BAT.BAT  is  used  to quickly incorporate DEBUG scripts
  into batch files, or to make a library of DEBUG scripts that
  are   utilized  by  a  batch  file;  that  way,  instead  of
  distributing, say, 12 DEBUG scripts with a batch  file,  you
  can  instead  distribute one help file -- a batch file where
  the DEBUG scripts are packed, which your batch file can then
  call  to  jettison  the  DEBUG scripts as need be, run them,
  then delete them from disk. This makes the batch  code  more
  independent,   rhobust,   and   more   likely   to  work  as
  anticipated, because the help files you need are  packed  in
  the  batch code itself, thus making it less likely that they
  will be misplaced, misidentified, or  otherwise  unavailable
  to the batch code that requires them.
  
  However,  there are some things you may want to keep in mind
  before you pack DEBUG scripts into a library; first, if  the
  DEBUG  script's  comments  contain pipes, redirectors (i.e.,
  the less-than and greater-than symbols)  or  the  ampersands
  (&),  it  will  cause  an  error  message and the jettisoned
  script may not  work,  so  you  need  to  remmove  any  such
  characters  from  the  DEBUG script(s) before you pack them,
  or, to make things  easier,  you  can  use  the  batch  file
  XSCRCMTS.BAT  to  remmove  semicolon  remmarks  from a DEBUG
  script before you  pack  it  into  batch  code,  which  will
  effectively  remmove  any special symbols that may be in the
  DEBUG script's comments.

  Second, when you pack a DEBUG script into a batch file using
  DBGS2BAT, the resulting batch code simply re-creates the or-
  iginal .DBG script, saving it to disk in the current folder,
  so the batch code that uses it must of course pass the DEBUG
  script through DEBUG.EXE to generate an executable file, run
  it, then delete it.


  
