S&R Patcher v2.61  Ghiribizzo [OR&L/uCF] 1999
==============================================

Usage: SR <filename> <search string> <patch data>

Filename is the file that the generated S&R patcher will patch 

Search String is the hex representation of the bytes to search for. Patch Data 
is the hex sequence to replace the search string with.

Usage: OUT [filename]

Filename is an optional parameter and specifies the file to search. If no 
parameter is supplied, OUT.COM will use it's default filename hardwired at 
creation time.

The program will create OUT.COM overwriting any existing file with that name. 
OUT.COM will search for the file specified during it's creation for the search 
string and will replace it if found. By specifying a file as a parameter, 
OUT.COM can search other files.

Instead of using HEX values, you can use strings. To do this, prefix the search 
string ONLY with "'". 

Example: "QSR myfile 'file fail"


Notes
-----

The hex sequences should have no spaces in between bytes. The hex sequences 
should be of the same length (the patcher will check for this).

OUT.COM will search and replace only the FIRST OCCURRENCE of the search string.

The program uses very basic file handling routines so performance may not be 
optimal to say the least.

OUTSUP.COM and OUTUNSUP.COM are programs which patch OUT.COM to enable or 
disable the initial splash message. By running OUTSUP.COM or OUTUNSUP.COM with 
the parameter of SR.COM, you can patch SR.COM so that it produces patchers with 
the splash screen disabled by default.

You can use CT.COM (gpf.cjb.net) to tag your own message to the .COM files 
produced.

Also on the to do list is qsr - a quick search and replace utility similar to my 
quick patcher (qp.com).

The S&R engine is very compact. In fact, each additional byte of search/patch 
data adds only an extra byte to the filesize. So after the initial program 
overhead, size is increased by only one byte per extra byte of patch data or 
search data added.

The S&R routine used in this version is limited to 256 bytes maximum patch. This 
can be easily fixed, but I don't see a reason for doing so at the moment.

I'm quite short of time these days, so if you can help me code these things, 
please don't hesitate to contact me.


~~
Ghiribizzo

email: ghiribizzo@geocities.com
www  : ghiribizzo.cjb.net
