
;***********************************************************************
;
;			    "CRUN-OVL.ASM"
;		  CRUNCH and UNCRunch v2.4 Overlay File
;			(For user configuration)
;
;***********************************************************************
;
;  Requires:	ASM.COM    (standard CP/M assembler) or equivalent
;		MLOAD.COM  (p/d file merging utility, NightOwl Software)
;
;
; To use this overlay, simply edit in the YES and NO answers as required.
; Then assemble and merge using the following 2 steps (or equiv):
;
;      ASM CRUN-OVL
;      MLOAD CRUNCH.COM=CRUNCH.COM,CRUN-OVL.HEX
;
; If "uncrunch" is to be configured the same way, simply follow that
; with:
;
;      MLOAD UNCR.COM=UNCR.COM,CRUN-OVL.HEX
;
;***********************************************************************


	ORG	100H

NO	EQU	0		; First, some definitions.
YES	EQU	0FFH		;


JMPINS: DS	11		; Do not touch. Room for jump instruct-
				;   ion and Z3 environment descriptor.
Z3FLAG: DB	NO		; "Z3 Flag".  YES configures program for
				;   use on the ZCPR33 operating system.
				;   NO for normal CP/M or CP/M+.  No
				;   need to set this flag if file has
				;   been installed with Z3INS.
AMFLAG: DB	NO		; "Archive Mode Flag".	YES will cause
				;   the program to normally run in the
				;   "archive" backup mode, unless it is
				;   toggled back off by the /A	command
				;   line option.  Since this is sort of
				;   a specialty mode, this byte should
				;   probably be left NO.
INSREV: DB	23H		; DO NOT CHANGE.  This allows the v2.3
				;   INSTALL program to know that it can
				;   install this program (even though
				;   this is actually v2.4)
QMFLAG: DB	NO		; "Quiet  Mode Flag".  YES to have the
				;   program default to "quiet" mode, NO
				;   for normal "verbose"  mode.  In the
				;   quiet mode, the program will not
				;   display lots of churning numbers on
				;   the screen during operation.  It
				;   corresponds to the /Q command line
				;   option which will toggle the default
				;   mode defined here.
OVFLAG: DB	NO		; "Overwrite Without Prompt Flag".  If
				;   YES, existing files will be over-
				;   written without a prompt, NO to have
				;   the program always ask for confir-
				;   mation before doing this.  The
				;   default mode defined here can be
				;   toggled  here by the /O command line
				;   option.
TDFLAG: DB	NO		; "Turbo-DOS  Flag".  YES if running
				;   Turbo-DOS or other operating system
				;   which claims CP/M Plus compatibility
				;   but does not actually implement
				;   multisector I/O properly.  Otherwise
				;   use NO here.
TMFLAG: DB	NO		; "Confirm (tag) Mode Flag". YES to have
				;   the program default to the "tag"
				;   mode of operation everytime it is
				;   invoked.  Normally this should be
				;   NO and the mode can be invoked with
				;   the /C (alternate: /T) command line
				;   option.
WBFLAG: DB	NO		; "Warm Boot Flag".  YES if if you want
				;   the program to perform a "warm boot"
				;   as opposed to a return to the CCP
				;   each time it is run.  Normally NO
				;   but included for people running
				;   systems who have reason to believe
				;   that the CCP will not remain resi-
				;   dent.  (Note: 2k CCP size assumed).
BFFLAG: DB	NO		; "Bigger File Flag".  YES means the
				;   program will NOT ask the question
				;   "Result file larger than original,
				;   keep it anyway?"  (The file will
				;   always be kept).  Normally NO.  In
				;   v2.4 this question is only asked
				;   when the destination drive and user
				;   areas are identical. See NOTES24.DOC
				;   for more information.
MAXDRV: DB	0FFH		; "Maximum Drive allowed, plus one".
				;   The default value here is "FF",
				;   effectively  disabling  the feature.
				;   If you so desire, you may enter a
				;   value here ("A" = 2, "B" = 3, etc.),
				;   in which case the program will in-
				;   tercept any references to higher
				;   drives (giving an "Invalid Drive"
				;   error).  This feature has very
				;   little usefulness in practice.  If
				;   you leave this feature deactivated,
				;   your operating system will gladly
				;   tell you about the invalid drive
				;   specification when it gets it.
MAXUSR: DB	0FFH		; "Maximum User Code Allowed, plus one".
				;    Similar to above.	Note however
				;    that the command line parser will
				;    reject all references to values
				;    above 15 no matter what.  In this
				;    case, you don't get the "Invalid
				;    User Area" message, you will get
				;    "Invalid Argument".  31 user areas
				;    are NOT currently supported - about
				;    as useless as the above patch.

SPARE:	DB	0		; Spare for future use.

;-----------------------------------------------------------------------
;
; Filetype Exclusion List (used by CRUNCH only)
;
; The next 30 bytes may contain up to 10 three-letter filename suffixes.
; When encountered, no attempt will be made to compress these files un-
; less explicitly specified.  They
; NOTES24.DOC).  The defaults are .ARC, .ARK, and .LBR.  The first two
; are always compressed already.  Any attempt at recompression will al-
; most certainly be a  waste of time.  While a .LBR file may or may not
; contain files that have already been compressed, usually they are.
;
; Notes:  Some users may prefer to add .COM as object code files often
; do not compress well, sometimes not at all.  On the other hand, some
; amount of compression  will usually occur in cases where there is em-
; bedded text or other patterns, they may compress quite nicely.  Micro-
; soft .REL files, which are bitwise encoded, are even less likely to
; compress.  If they contains some embedded text, they likewise often do
; compress somewhat.  SLR .REL files are not bit encoded and are more
; likely to show modest compression.  Since the v2.4 program will now
; replace compression failures with straight copies automatically, the
; default configuration here leaves it to the program to try these files
; out.
;
; Note it is NOT necessary to add ?Z? and ?Q? to the list as CRUNCH v2.4
; will recognize squeezed and crunched files directly by reading their
; headers.  Including these filetypes may save some time as by elimina-
; ting the necessity of even opening the files.  On the other hand, it
; may prevent the compression of certain compressible files (notably
; assembly source with the .AZM suffix, which is unique to the public
; domain Z80 assembled named Z80MR.COM.  In any event, final decisions
; are left to the the user.
;
;-----------------------------------------------------------------------
;
; File type exclusion list. Leave zeroes in unused locations!!
;
;	       |  1  |	2  |  3  |  4  |  5  |
EXTBL:	DB	'ARC','ARK','LBR',0,0,0,0,0,0
;
;	       |  6  |	7  |  8  |  9  |  10 |
	DB	0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
;
	DB	0		; This last zero MUST end up at location
				; 135H
;
;		  end of user configuration area
;-----------------------------------------------------------------------
;
	END
