Subj : The code
To : Sean Dennis
From : mark lewis
Date : Thu Oct 15 2009 04:12 pm
ml> that and also use list.com and even a binary comparison tool to
ml> compare the two files so that you can verify that only those two bits
ml> got changed and that they are the proper two bits :)
SD> That's an excellent idea. You have any comparison tools to
SD> recommend (DOS or OS/2, doesn't matter)?
i generally used "comp /b" (/b for binary compare instead of textual) but i
don't know what version of comp that is/was... i don't see it as a built-in in
4DOS or 4OS2... i'm lookin'...
[time passes]
i can't find it, now... the comp that i do find is comp.com and is both OS/2
and DOS flavored (one .com file for both)... maybe it was "fc"?? i just know
that i had to use the "/b" option to denote a binary comparison instead of a
textual one...
damn, that's got my goat and i'm rather frustrated that i can't locate that
tool or remember exactly which one it was :( maybe it was... hummm... :!:
[time passes]
found it!! believe it or not, on one of the win98se boxes hiding out in
\windows\command and also in \options\tools\oldmsdos... this last one is a
copy of the tools\oldmsdos folder from the win98 install cd... it is FC.EXE...
[/me quickly copies it over to this OS2 box and gives it a try]
aww... says incorrect DOS version :? now, how to setver on warp3 with 4DOS??
:( maybe that's why i still tend to do most development on that machine??
no... can't be because i've been running this one for far too long... there's
gotta be another util that i used to use that i probably lost yers back when i
had to reinstall this system :? dagnabit! it was a very very very handy tool,
too...
guess i need to figure out how to hack it and blow the dos version check out :?
:(
well, in any case, here's the /? output just so's you have an idea what it
is/was capable of and decide to go looking for a similar tool on the net
somewhere...
FC [/A] [/C] [/L] [/LBn] [/N] [/T] [/W] [/nnnn] [drive1:][path1]filename1
[drive2:][path2]filename2
FC /B [drive1:][path1]filename1 [drive2:][path2]filename2
/A Displays only first and last lines for each set of differences.
/B Performs a binary comparison.
/C Disregards the case of letters.
/L Compares files as ASCII text.
/LBn Sets the maximum consecutive mismatches to the specified number of
lines.
/N Displays the line numbers on an ASCII comparison.
/T Does not expand tabs to spaces.
/W Compresses white space (tabs and spaces) for comparison.
/nnnn Specifies the number of consecutive lines that must match after a
mismatch.
i'll keep looking, too because a good file comparison tool is a must for many
programming situations... especially if you have large (greater than 64K) files
to compare :)
