Hello Peter,
 \|/  Subject:  Question #1!
 /|\  On Thursday April 16 1998 at 13:44, 
      you wrote to Gerald Miller saying:
I think Barry Block "munged" the Subject sometime back, but no matter... :-))
 GM>> provide more accurate detail of what the problems are, one must
 GM>> live with the fact that all errors are lumped into errorlevel
 GM>> 255.
 PH> Maybe CHKDSK does that (I don't use the DOS-one), lumping _all_ errors
 PH> into 255, but with other programs you should be carefull. ERRORLEVEL
 PH> without any operator checks to "greater equal"!
 PH>   ERRORLEVEL [operator] n
 PH>        This test retrieves the exit code of the preceding external
 PH>        program.  By convention, programs return an exit code of 0 when
 PH>        they are successful and a number between 1 and 255 to indicate
 PH>        an error.  The condition can be any of the operators listed
 PH>        above (EQ, !=, GT, etc.).  If no operator is specified, the
 PH>        default is GE.  The comparison is done numerically.
Peter, my friend, I assume that you are trying to tell me something with this 
little tidbit of information, but your meaning must have gotten lost in the 
mail...  :-)))
Please expand your message using a CHKDSK example to determine "Lost chain", 
"... clusters", or any of the other CHKDSK errorlevel condtions.
If CHKDSK produces errorlevel "0" for success and errorlevel "255" for all 
other conditions, I fail to see how I can tell my batch file to perform a 
specific task if it detected a "Lost chain" error, for example...
On the other hand, 4DOS may be able to "read" the messages displayed on the 
monitor and gosub to certain routines if/when it detects such conditions, 
rather than having to rely on errorlevels...
              G'Day ... Gerald
--- GoldED/386 3.00.Beta2 UNREG
---------------