Hello Barry,
 \|/  Subject:  Question #1!
 /|\  On Sunday April 12 1998 at 13:50, 
      you wrote to Gerald Miller saying:
 BB>>> Find the beginning of the string you want to remove and
 BB>>> overwrite a char0 there. not an ascii 0. Understand?
 GM>> NO
 BB>      Read a little about how to use a hex editor.
 BB>      There are many free ones available thru Fido.
I must have three or more hex editors...  ,-))
 GM>> Would it be possible for you to create a little
 GM>> debug script file that would make the modifications to CHKDSK.EXE
 GM>> and post it here?
 BB>      No. I don't have msdos v6.22. That is what you use.
 BB>      ms would not like me to post one of their progs. certainly not a
 BB>      modified version :-)
I think you misunderstood my request.  I don't want you to post a modified 
CHKDSK.EXE in a public echo, just post a SCRIPT that would permit someone to 
use it as an input file to DEBUG, so they could modify their own copy of 
CHKDSK if they wished to...
Oh, now I see it.  You don't have MS-DOS v6.22, so I guess the debug script 
is out.  I'll go back to your original posted suggestion for the modification 
using the hex editor.
 GM>> CHKDSK %drive%:|find /v "Serial"|find /v "Instead"|find /v
 GM>> "range"|find /v "SCANDISK"
 BB>      I guess this is incomplete. I don't see what it does.
The FIND command is searching the screen for occurrences of the keywords that 
are within the quotation marks and throwing the entire line to "nul"...
 BB>      BTW, more than once I have experienced ScanDisk and Norton's DD
 BB>      get things wrong and ChkDsk get it right.
I think I've hit on a "semi" solution.  After CHKDSK runs, I'll append two 
lines:
      If errorlevel 255 goto fix_it
      If errorlevel 0 goto run
Not exactly what I was wanting, but since CHKDSK is unable to provide more 
accurate detail of what the problems are, one must live with the fact that 
all errors are lumped into errorlevel 255.
              G'Day ... Gerald
--- GoldED/386 3.00.Beta2 UNREG
---------------