; ; ; ┌───────────────────┐ ; │ │ ║ UpLoadProcessor Configuration File ; │ ╥ ╥ ╥ │ ║ ; │ ║ ║ ║ ╓──╖ │ ║ Version 0.99ß ; │ ║ ║ ║ ║ ║ │ ║ ; │ ╙───╜ ╨ ║──╜ │ ║ (c) Copyright 1992-1993 - Stacy Smith ; │ ╨ │ ║ ; └───────────────────┘ ║ ; ════════════════════╝ ; ; The latest version of ULP can always be obtained from my BBS: ; ; The Bloom Beacon-Picayune BBS ; Node 1: (804) 525-9760 (USRobotics Courier Dual Standard) ; Node 2: (804) 525-5372 (USRobotics Courier V.32bis) ; FidoNet 1:276/112 (magic tags ULP, ULP286 and ULP386) ; ; NOTE: I have tried to make this configuration file as flexible as possible, ; but it would probably be a good idea to not rearrange it too much if ; it can be avoided... ; ; ; ╔════════════════════════════════════╗ ; ║ General Options And Parameters ║ ; ╚════════════════════════════════════╝ ; ; The registration code, BBS name and sysop name EXACTLY as provided to you on ; your registration letter. If this is an unregistered version, comment out ; these lines, or don't change them. Note that these are case-sensitive! REG_CODE 0000000000 BBS_NAME UNREGISTERED SYSOP_NAME SYSOP ; If you wish the ULP programs to swap themselves out of memory prior to ; executing external programs, set this parameter to YES. The ULP programs ; will attempt to swap to EMS, XMS and lastly, the hard disk. If you do not ; want this feature, enter NO or comment the line out. Use this feature ONLY ; if you have memory problems! SWAP no ; If you wish the ULP programs to delete the extracted files themselves, ; versus using DOS, set this parameter to YES. If not, enter NO or comment ; the line out. In some cases, letting DOS do the work is faster, but foreign ; language implementations of DOS may prevent this ability. INTERNAL_DEL no ; The size of the disk I/O buffers you wish to allocate in bytes (valid values ; are between 2048 bytes and 16384 bytes). Optimal performance is obtained with ; a value that is a multiple of 2048 (a typical hard disk cluster size). DISK_BUFFER 4096 ; The path/filename of the log file for ULP to record its activities. Comment ; out if you don't want disk logging. LOG_FILE c:\ulp\ulp.log ; If you want ULP and ULPTEST to record their statistics on each archive ; processed to the log file, add the VERBOSE keyword. If you only want errors ; and summary statistics, use the TERSE keyword or comment the line out. LOG_MODE verbose ; The path/filename of the ULP process data file. This file contains ; information on previous ULP processing and is maintained automatically ; by ULP. PROC_DAT_FILE c:\ulp\process.dat ; If you want ULP, ULPTEST or ULPDB to use a specific directory for storage ; while processing, enter the full pathname (including the trailing ; backslash). The drive letter MUST be included. If this directory does not ; exist at runtime, the ULP programs will attempt to create it. This can be ; set to a RAM disk for greater speed. If you do not desire to use a specific ; directory, comment it out (ULPDB will extract at its current location on ; disk). WORK_DIR c:\temp\ ; This defines how ULP dispositions archives found to have an error other than ; a file check failure (such as ZIP CRC). If you want ULP to delete the archive ; and description, type DELETE; if you want ULP to rename the archive to a .ERR ; extension, type RENAME or comment the line out. ERR_DISP rename ; This defines how ULP dispositions archives that fail a file check, such as a ; virus scan. If you want ULP to delete the archive and description, type ; DELETE; if you want ULP to rename the archive to a .VRS extension, type ; RENAME or comment the line out. VIRUS_DISP delete ; The command line for an ASCII file viewing (or editing) utility. This will ; be called by ULPDB in order to view an archive information file generated ; for the purposes of archive review. Place the @FILES@ variable where the ; filename is to be entered on the utility's command line. VIEWER list @FILES@ ; ; ; ╔════════════════════════╗ ; ║ Upload Directories ║ ; ╚════════════════════════╝ ; ; The path/filename of the upload directory configuration file for ULP. This ; file is automatically created by ULPCFG from data contained within this ; file. DIR_CFG_FILE c:\ulp\ulpdir.bin ; Each pair of upload directories (one private, and one public), is denoted by ; UL_DIR x, where x is a sequential number. An unlimited number of directory ; pairs can be processed by ULP. The next 5 keywords are required after the ; UL_DIR statement, do not comment any of them out or insert other parameters ; or comments in between them: ; UL_DIR = denotes a new directory pair. ; SOURCE_PATH = the directory where the private uploads are placed by the BBS. ; Note: this must include the trailing backslash! ; SOURCE_LIST = the private upload directory list file that contains the archive ; descriptions, including the path. ; SOURCE_HDR = the number of lines to ignore at the beginning of the private ; upload directory list file (for headers, detachable header ; filespecs, etc.) ; DEST_PATH = the directory where the public uploads are placed by ULP after ; successful processing. Note: this must include the trailing ; backslash! (Leave blank if all uploads are public). ; DEST_LIST = the public upload directory list file that contains the archive ; descriptions, including the path. ULP will append this file ; with the descriptions of successfully processed files. (Leave ; blank if all uploads are public). ; * IF ALL UPLOADS ARE PRIVATE: * IF ALL UPLOADS ARE PUBLIC: ; UL_DIR 1 UL_DIR 1 ; SOURCE_PATH c:\privul\ SOURCE_PATH c:\public\ ; SOURCE_LIST c:\pcb\gen\prvuldir SOURCE_LIST c:\pcb\gen\newuldir ; SOURCE_HDR 1 SOURCE_HDR 1 ; DEST_PATH c:\publul\ DEST_PATH ; DEST_LIST c:\pcb\gen\newuldir DEST_LIST UL_DIR 1 SOURCE_PATH c:\privul\ SOURCE_LIST c:\pcb\gen\prvuldir SOURCE_HDR 1 DEST_PATH c:\publul\ DEST_LIST c:\pcb\gen\newuldir ; ; ; ╔════════════════════════╗ ; ║ Age Limit Checking ║ ; ╚════════════════════════╝ ; ; If you want ULP to fail an archive based on the average age of the files ; contained within, enter YES; otherwise, enter NO or comment out the line. AGE_CHK yes ; The maximum average age in months, that you will accept as an upload. AGE_LIMIT 48 ; ; ; ╔═════════════════════════════╗ ; ║ Archiving Control Flags ║ ; ╚═════════════════════════════╝ ; ; If you want ULP to convert the archive to a default archiving format of your ; choice, type YES; if not, type NO or comment the line out. ARC_CVT yes ; If you want ULP to convert any internal archives within the archive to your ; default archiving format, type YES; if not, type NO or comment the line out. ; This may save some disk space, but will potentially mess up any automatic ; installation programs/batch files contained within the archive. ARC_NEST_CVT no ; If you want ULP to convert a self-extracting (SFX) archive to your default ; archiving format, type YES; if not, type NO or comment the line out. This ; also may save some disk space, but can cause problems. For example, if you ; don't have PKZ110.EXE on your BBS, a novice user has no way of obtaining the ; PKZIP/PKUNZIP utilities from your BBS. SFX_CVT no ; If you want ULP to keep ZIP archives with authenticity verification stamps ; (-AV) regardless of the other archiving control flags, then set this to 'yes' ; or comment it out. If you set this flag to 'no', then the archive will be ; recompressed per the other control flags. KEEP_AV yes ; If you want ULP to keep ARJ archives with security envelopes (similar to a ; ZIP -AV) regardless of the other archiving control flags, then set this ; to 'yes' or comment it out. If you set this flag to 'no', then the archive ; will be recompressed per the other control flags. KEEP_ENV yes ; ; ; ╔══════════════════════════╗ ; ║ Archiver Definitions ║ ; ╚══════════════════════════╝ ; ; Each archiver, is denoted by ARCHIVER x, where x is a sequential number. Up ; to 9 archivers can be executed by ULP. ULP is capable of automatically ; detecting ARC, ARJ, HYP, LZH, PAK, SQZ, ZIP and ZOO archives. The next 7 ; keywords are required after the ARCHIVER statement; do not comment any of ; them out or insert other parameters or comments between them. I would ; also advise against changing the command options I have set, unless you ; have need to do so. Most are to ensure uninterrupted processing (such ; as '/m1' in LHA). ; ARCHIVER = denotes a new archiver definition. ; ARC_EXT = the extension for this particular archiving format. ; ARC_PRIMARY = if this is the default archiving format you use on your BBS, ; type YES; if not, type NO. ; ARC_PACK = the command line to pack archives, including all command-line ; switches desired. Place the variable @ARCHIVE@ where the ; filename is to be inserted in the command line and @FILES@ ; where the filespec is to be inserted. ; ARC_COMMENT = the command line to comment archives. Place the variable ; @ARCHIVE@ where the filename is to be inserted in the command ; line. If you do not wish comments, or the archiver does not ; support comments, leave the line blank. ; ARC_UNPACK = the command line to unpack archives, including all command-line ; switches desired. Place the variable @ARCHIVE@ where the ; filename is to be inserted in the command line. ; ARC_TEST = the command line to test archives, including all command-line ; switches desired. Place the variable @ARCHIVE@ where the ; filename is to be inserted in the command line. ; ARC_ERR = the errorlevel that the archiver returns upon success. This ; information should be available in the program's documentation. ARCHIVER 1 ARC_EXT arc ARC_PRIMARY no ARC_PACK c:\util\pkpak -a @ARCHIVE@ @FILES@ ARC_COMMENT ARC_UNPACK c:\util\pkunpak -r @ARCHIVE@ ARC_TEST c:\util\pkunpak -t @ARCHIVE@ ARC_ERR 0 ; ARCHIVER 2 ARC_EXT arj ARC_PRIMARY no ARC_PACK c:\util\arj a -e -jm -m1 -x!c:\ulp\exclude.lst @ARCHIVE@ @FILES@ ARC_COMMENT c:\util\arj c -zc:\ulp\comment.txt @ARCHIVE@ ARC_UNPACK c:\util\arj e -y @ARCHIVE@ ARC_TEST c:\util\arj t @ARCHIVE@ ARC_ERR 0 ; ARCHIVER 3 ARC_EXT hyp ARC_PRIMARY no ARC_PACK c:\util\hyper -a @ARCHIVE@ @FILES@ ARC_COMMENT ARC_UNPACK c:\util\hyper -x @ARCHIVE@ ARC_TEST c:\util\hyper -v @ARCHIVE@ ARC_ERR 0 ; ARCHIVER 4 ARC_EXT lzh ARC_PRIMARY no ARC_PACK c:\util\lha a /m1 @ARCHIVE@ @FILES@ ARC_COMMENT ARC_UNPACK c:\util\lha e /m1 @ARCHIVE@ ARC_TEST c:\util\lha t /m1 @ARCHIVE@ ARC_ERR 0 ; ARCHIVER 5 ARC_EXT pak ARC_PRIMARY no ARC_PACK c:\util\pak a /wa @ARCHIVE@ @FILES@ ARC_COMMENT ARC_UNPACK c:\util\pak e /wa @ARCHIVE@ ARC_TEST c:\util\pak t /wa @ARCHIVE@ ARC_ERR 0 ; ARCHIVER 6 ARC_EXT sqz ARC_PRIMARY no ARC_PACK c:\util\sqz a -q0 -x@c:\ulp\exclude.lst @ARCHIVE@ @FILES@ ARC_COMMENT c:\util\sqz c @ARCHIVE@ c:\ulp\comment.txt ARC_UNPACK c:\util\sqz e @ARCHIVE@ ARC_TEST c:\util\sqz t @ARCHIVE@ ARC_ERR 0 ; ARCHIVER 7 ARC_EXT zip ARC_PRIMARY yes ARC_PACK c:\util\pkzip -a -ex -x@c:\ulp\exclude.lst @ARCHIVE@ @FILES@ ARC_COMMENT c:\util\pkzip -z < c:\ulp\comment.txt @ARCHIVE@ ARC_UNPACK c:\util\pkunzip -o @ARCHIVE@ ARC_TEST c:\util\pkunzip -t @ARCHIVE@ ARC_ERR 0 ; ARCHIVER 8 ARC_EXT zoo ARC_PRIMARY no ARC_PACK c:\util\zoo ahP @ARCHIVE@ @FILES@ ARC_COMMENT ARC_UNPACK c:\util\zoo e @ARCHIVE@ ARC_TEST c:\util\zoo t @ARCHIVE@ ARC_ERR 0 ; ; ; ╔═══════════════════════════════════╗ ; ║ Uncompressed Files to Process ║ ; ╚═══════════════════════════════════╝ ; ; ULP can process selected uncompressed uploads, using the PROC_EXT option. ; Up to 10 uncompressed file types can be specified by extension. DO NOT ; use any compression format extensions (ARJ, ZIP, etc.). If you do not ; want to process any uncompressed uploads, simply remove or comment out ; the lines. PROC_EXT com PROC_EXT doc PROC_EXT txt ; ; ; ╔════════════════════════════╗ ; ║ Files to Never Process ║ ; ╚════════════════════════════╝ ; ; ULP can be forced to NOT process selected uploads, using the NO_PROC_EXT ; keyword. Up to 10 file types can be specified by extension. THESE FILES ; WILL BE AUTOMATICALLY PASSED; be sure this is desired. This is intended ; for use with non-DOS uploads, such as the Unix Tar Z format, or Macintosh ; files. NO_PROC_EXT cpt NO_PROC_EXT sit ; ; ; ╔══════════════════════════════════════════╗ ; ║ File Checking (Virus Scanning, etc.) ║ ; ╚══════════════════════════════════════════╝ ; ; Each file checker is denoted by FILE_CHECKER x, where x is a sequential ; number. Up to 3 file checking programs can be executed by ULP. The next 2 ; keywords are required after the FILE_CHECKER statement; do not comment them ; out or insert other parameters or comments in between them. ; FILE_CHECKER = denotes a new file checking/virus program definition. ; FILE_CHK_CMD = the command line to execute each file checker, including all ; command-line switches. Place the variable @FILES@ where the ; filespec is to be placed on the command line. ; FILE_CHK_ERR = the errorlevel that the file checking program returns upon ; success. This information should be available in the ; program's documentation. FILE_CHECKER 1 FILE_CHK_CMD c:\util\scan /a /nomem /nopause @FILES@ FILE_CHK_ERR 0 ; ; ; ╔═══════════════════════╗ ; ║ GIF File Checking ║ ; ╚═══════════════════════╝ ; ; If ULP is to reject GIF files based upon picture width, enter the minimum ; acceptable width in pixels. If no width limit is desired, set it to zero or ; comment out the line. MIN_WIDTH 640 ; If ULP is to reject GIF files based upon picture height, enter the minimum ; acceptable height in pixels. If no height limit is desired, set it to zero ; or comment out the line. MIN_HEIGHT 480 ; If ULP is to reject GIF files based upon the number of colors in the picture, ; enter the minimum acceptable number of colors. If no color limit is desired, ; set it to zero or comment out the line. MIN_COLORS 256 ; If ULP is to keep uploaded GIF files if they have been compressed with ; GIFLITE, set this to YES. If not, set it to NO or comment it out. NOTE: ; accepting GIFLITEd GIF files can compromise the duplication system due to its ; variable compression ratio! KEEP_GIFLITE no ; A GIF file checker is denoted by GIF_CHECKER 1. Only 1 GIF file checking ; program can be executed by ULP. The next 2 keywords are required after the ; GIF_CHECKER 1 statement; do not comment them out or insert other parameters ; or comments in between them. ; GIF_CHECKER = denotes a new file checking/virus program definition. ; GIF_CHK_CMD = the command line to execute each GIF file checker, including ; all command-line switches. Place the variable @FILES@ where ; the filespec is to be placed on the command line. ; GIF_CHK_ERR = the errorlevel that the GIF file checking program returns ; upon success. This information should be available in the ; program's documentation. GIF_CHECKER 1 GIF_CHK_CMD c:\util\giftest /b:0 @FILES@ GIF_CHK_ERR 0 ; ; ; ╔═══════════════════════════════════════╗ ; ║ Description Processing Parameters ║ ; ╚═══════════════════════════════════════╝ ; ; If you want ULP to word-wrap inserted descriptions, enter YES for smart ; word-wrapping, otherwise, type NO or comment the line out. Note that ULP ; now checks for boxes, etc. before attempting a word-wrap. WORD_WRAP yes ; If you want ULP to insert internal description files (FILE_ID.DIZ or ; DESC.SDI), type YES; if not, type NO or comment the line out. INT_DESC yes ; If ULP is to insert internal description files, the following parameter ; is the maximum number of lines that ULP will insert from the description ; file (limited to 15 lines). This defaults to 10 if the line is commented out. DESC_LIMIT 10 ; If you want ULP to add a single line to the description, type YES; if not, ; type NO or comment the line out. INFO_LINE yes ; The column where the | marker goes in your directory listing setup. The ; standard PCBoard setup indents to column 32. INFO_INDENT 32 ; The format that you would like for the archive information line. The legal ; variables are: ; @#@ Number of files in the archive (and nested archives) ; @NEWEST@ Date of the newest file in the archive ; @OLDEST@ Date of the oldest file in the archive ; @BYTES@ The total number of bytes (uncompressed) in the archive ; @DATE@ Today's date ; @CR@ Inserts a line break for multiline capability ARC_INFO_FMT (Files: @#@ Newest: @NEWEST@ Oldest: @OLDEST@) ; The format that you would like for the GIF information line. The legal ; variables are: ; @WIDTH@ Horizontal resolution (number of columns) ; @HEIGHT@ Vertical resolution (number of rows) ; @COLORS@ Number of colors ; @COMPRESS@ Inserts "GIFLITE" or "None", depending upon compression ; @DATE@ Today's date ; @CR@ Inserts a line break for multiline capability GIF_INFO_FMT (Resolution: @WIDTH@x@HEIGHT@x@COLORS@ Comp: @COMPRESS@) ; ; ; ╔══════════════════════════════════════╗ ; ║ DOWNLOAD.TXT Updating Parameters ║ ; ╚══════════════════════════════════════╝ ; ; If you want ULP to scan your DOWNLOAD.TXT file and update the file extension ; of the upload to reflect the correct archiving method used, enter YES. If ; not, enter NO or comment the line out. UPDATE_DLTXT yes ; The path and name for the PCBoard DOWNLOAD.TXT file. DLTXT_FILE c:\pcb\main\download.txt ; ; ; ╔════════════════════════════════╗ ; ║ ULPTEST Testing Parameters ║ ; ╚════════════════════════════════╝ ; ; This defines how ULPTEST processes archives. NORMAL indicates a full test ; is to be performed, identical to the ULP event processing except that the ; archive formats are not converted (this is a limitation of PCBoard). ; FAST indicates a fast test in which the archive is scanned for archive ; integrity, duplicates, and age without unpacking the archive (ARJ and ZIP ; files only). If this mode is used, it should be held for later processing ; by ULP so that it can be file-checked. TEST_MODE normal ; If NORMAL mode is used, the archive's file size will first be compared ; against this limit (in kilobytes). If it is larger than this number of ; bytes (in kilobytes), it will be forced into FAST mode to speed the process ; and prevent wasting the user's online time. Entering 0, or commenting the ; line out will disable this feature. TEST_LIMIT 250 ; If you want ULPTEST to output status information to the user on-line, enter ; YES; if you do not want ULPTEST to output information, enter NO or comment ; the line out. COMM_IO yes ; If you want ULPTEST to suppress the program header output to the user ; (the program name, copyright notice, and registration information). This ; gives a seamless look for ULP into PCBoard. If this is desired, set this ; to YES; otherwise, set to NO or comment out the line. ; NOTE: This will work for registered users only! SUPPRESS_HDR no ; ; ; ╔══════════════════════╗ ; ║ BBS Ads Handling ║ ; ╚══════════════════════╝ ; ; If you want ULP to remove known BBS ads from new uploads during processing, ; type YES; if not, type NO or comment the line out. ADS_CHK yes ; The directory path and name for the BBS ads database. ADS_DB c:\ulp\ulpads.db ; The directory path and filename for your BBS ad to be added to each and every ; archive processed by ULP. Note that you must provide a path, or it will not ; be copied. Please use the ARJ and ZIP comment instead, as BBS ad files are ; the scourge of the BBS world... ;BBS_AD_FILE c:\ulp\bbs.ad ; ; ; ╔═══════════════════════════════╗ ; ║ CRC-32 Duplicate Checking ║ ; ╚═══════════════════════════════╝ ; ; If you want ULP to use its internal CRC-32 duplication checking, type YES; ; if not, type NO or comment the line out. If you want to use a third-party ; duplication checker, such as ZDCS, you can add it as a file checker (above), ; providing it returns DOS errorlevels so ULP can detect its success/failure. DUPE_CHK yes ; The minimum percentage of duplication allowed for a file to pass. Anything ; smaller will be forced to be passed. DUPE_LIMIT 50 ; The maximum percentage of duplication allowed for executable files and ; their overlays to pass. Anything larger will be failed. This number should ; be around 80. EXE_DUPE_LIMIT 80 ; The path and name for the main CRC-32 database file. DUPE_DB c:\ulp\database.db ; The path and name for the main CRC-32 database file index. DUPE_IDX c:\ulp\database.idx ; ; End of ULP configuration file... ;