Allen Walker wrote: 
 AW>>  ok... Go to http://vvv.com/~weirdal/others.htm ... I have put
 AW>> it there in all it's glory...  No UUDecoding... no nothing... (well,
 AW>> no docs either; just type "patch {path}" or "unpatch {path}" where
 AW>> path is the directory you want to check (be sure it's on the same
 AW>> drive though))
 
 KF> This ain't right! When I had a look at it, I was definitely NOT in the
 KF> root directory, yet that's where it started processing from.
 AW> Then try "patch ." ...  "." is the current path...
 KF> I deleted your program because it doesn't allow the user to know or
 KF> interact with what's going on. Sorry but without *at least* some
 KF> documentation explaining the process and what it does, I don't feel
 KF> safe with it. I would have kept it if I could have at least isolated
 KF> the processing to one directory tree rather than have it scan the entire
 KF> drive non-stop as it appeared to do. Even an output file of all files
 KF> that were changed would make me feel a little more comfortable about
 KF> using it, but not unless...
 AW> It does nothing without asking first.  *IF* it finds a program that
 AW> needs the patch, it asks you if you want to patch it.  If you say no,
 AW> it goes on searching.  Do you think *I* would feel safe testing it on
 AW> my own system if it didn't ask? 
Believe me, there was absolutely no prompting. Perhaps it wasn't your
patcher I got from here, since there were several of them posted, or
perhaps it was an earlier version of yours. I grabbed the last one I
saw posted. No docs, two executables in a uuencoded zip, one called
PATCH.EXE, the other UNPATCH.EXE. No prompts, no interaction. I typed
PATCH with no parameters and it started running through my directories,
starting at the root drive, and I had to force an abort to stop it. Does
that sound familiar?
 KF> Let us know when/if this is fixed.
 AW> If you don't like it, make one yourself. I just was *nice* enough to
 AW> try to make others lives easier.  If you like, I will make one that
 AW> you type "patch {filename}", and then you can go through all your
 AW> files and patch them one by one, if you like...  In fact, here you
 AW> go... Hot off the compiler... If you want to make it into an
 AW> un-patcher, swap SearchPattern and ReplacePattern. 
I didn't mean to insult you, but I'm telling you what I experienced.
If the program is as simple as the code you just showed in this last
message, I'll certainly have a go at making it better.
See my next message in this thread for what I consider an interactive
and safe program.
Kim Forwood
--- Blue Wave/DOS v?.??
---------------