home *** CD-ROM | disk | FTP | other *** search
- PATCH&GO v1.0 (07/17/86)
- Copyright (c) 1986 by John D. Osnes
-
-
- PATCH&GO brings the "poke & go" technique of ZCPR3 to CP/M 2.2
- users. PATCH&GO prompts the user for patches to another program,
- then saves a program which will load the other program, patch it,
- and finally execute the patched program. PATCH&GO is internally
- documented: simply execute PATCH&GO without any arguments and
- help will be displayed. A command menu is displayed before the
- user is prompted for patches.
-
-
- USAGE: PATCH&GO c:comfile d:patfile
-
- where: c:comfile = name of the program to be loaded, patched,
- and executed (c: specifies the drive where
- the program will be found when it is loaded;
- c: defaults to the drive currently selected
- AT THE TIME "comfile" IS LOADED or to drive
- A: if "comfile" is not found on the currently
- selected drive)
-
- d:patfile = name of the program created by PATCH&GO that
- will load, patch, and execute "comfile" (d:
- specifies the drive where the "patfile" is
- saved and defaults to the currently selected
- drive)
-
- Both filenames ARE REQUIRED and can not contain wildcards. The
- COM file type is implied on both files.
-
-
- The major problem with PATCH&GO is in the specification of the
- drive for "comfile" (c:). A couple of examples best illustrate
- this problem. Consider a "patfile" created using the following
- command:
-
- A>PATCH&GO COMFILE B:PATFILE
-
- where COMFILE.COM is also on the disk in drive B. An attempt to
- execute PATFILE using the following command:
-
- A>B:PATFILE (disk containing PATFILE.COM and
- COMFILE.COM is in drive B)
-
- will result in an error because COMFILE.COM can not be found on
- the currently selected drive (A, as shown by the prompt). This
- error occurs even though PATFILE.COM was explicitly specified as
- being on drive B. The following commands will all execute with-
- out error (note the currently selected drive shown by the prompt
- in each case):
-
- B>PATFILE (disk containing PATFILE.COM and
- COMFILE.COM is in drive B, the
- currently selected drive)
-
- C>A:PATFILE (disk containing PATFILE.COM and
- COMFILE.COM is in drive A)
-
- The last case is successful because like ZCPR, the disk in drive
- A is searched for COMFILE.COM if it is not found on the currently
- selected drive (C) and the drive for "comfile" was not explicitly
- specified at the time "patfile" was created. This feature of
- PATCH&GO can be disabled by setting equate DEFDRV to FALSE in the
- source for PATCH&GO and re-assembling it with ASM.
-
- Now consider a "patfile" created using the following command:
-
- A>PATCH&GO B:COMFILE B:PATFILE
-
- where once again COMFILE.COM is also on the disk in drive B. In
- this case, the following command will execute sucessfully:
-
- A>B:PATFILE (disk containing PATFILE.COM and
- COMFILE.COM is in drive B)
-
- because drive B (and only drive B) is always searched for
- COMFILE.COM. However, the following commands will result in
- errors:
-
- C>PATFILE (disk containing PATFILE.COM and
- COMFILE.COM is in drive C)
-
- B>A:PATFILE (disk containing PATFILE.COM and
- COMFILE.COM is in drive A)
-
- An error occurs in the last case because drive A is not searched
- for COMFILE.COM when the drive for "comfile" is explicitly speci-
- fied at the time "patfile" is created.
-
-
- COPYRIGHT (c) 1986 by John D. Osnes
- 1084 6th Street #41
- Albany, CA 94710
-
- PATCH&GO may be copied and distributed freely at no cost for the
- benefit and enjoyment of all registered CP/M users. It may not
- be sold or included in a package for sale without prior written
- permission of the copyright owner. The author specifically dis-
- claims any warranties, implied or otherwise, as to the perfor-
- mance and suitability of PATCH&GO.