DP Tool Club 19

home *** CD-ROM | disk | FTP | other *** search

/ DP Tool Club 19 / CD_ASCQ_19_010295.iso / vrac / pscn113e.zip / PALMSCAN.DOC < prev next >

Wrap

Text File | 1994-12-04 | 124KB | 3,428 lines

PalmScan v1.13 The Ultimate Archive Conversion Utility User guide PalmScan v1.13 The Ultimate Archive Conversion Utility December 4, 1994 Software and documentation written by Steven Hendriks Copyright (C) 1993,94 by Steven Hendriks All rights reserved. All information in this documentation is subject to change without prior notice PalmScan v1.13 User guide ----------------------------------------------------------------------- Table of Contents 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1.1 Copyright and License Agreement . . . . . . . . . . . . . . . 5 1.2 Contacting the author . . . . . . . . . . . . . . . . . . . . 6 1.3 What is PalmScan . . . . . . . . . . . . . . . . . . . . . . 6 1.4 Features . . . . . . . . . . . . . . . . . . . . . . . . . . 7 1.5 System requirements . . . . . . . . . . . . . . . . . . . . . 8 1.6 Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 1.7 Included files . . . . . . . . . . . . . . . . . . . . . . . 9 1.8 Runtime . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 2 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . 10 2.1 First time installation . . . . . . . . . . . . . . . . . . 10 2.2 Installing PalmScan in FileDoor . . . . . . . . . . . . . . 10 2.3 Installing PalmScan in SuperBBS . . . . . . . . . . . . . . 10 2.4 Installing PalmScan in Allfix . . . . . . . . . . . . . . . 11 2.5 Installing PalmScan in RemoteAccess 2.0x . . . . . . . . . 11 2.6 Installing PalmScan in The Remote Access Filearea Tools . . 11 2.7 Installing PalmScan in Maximus . . . . . . . . . . . . . . 12 2.8 Installing PalmScan in Ezycom . . . . . . . . . . . . . . . 13 2.9 Commandline . . . . . . . . . . . . . . . . . . . . . . . . 14 2.10 Watchdog, CTTY, ANSI.SYS . . . . . . . . . . . . . . . . . 19 2.11 Errorlevels . . . . . . . . . . . . . . . . . . . . . . . . 19 3 The configuration . . . . . . . . . . . . . . . . . . . . . . . 20 3.1 PALMSCAN.CFG . . . . . . . . . . . . . . . . . . . . . . . 20 3.2 PSetup . . . . . . . . . . . . . . . . . . . . . . . . . . 21 3.2.1 Commandline . . . . . . . . . . . . . . . . . . . . 21 3.2.2 Starting PSetup . . . . . . . . . . . . . . . . . . 21 3.2.3 Keys . . . . . . . . . . . . . . . . . . . . . . . . 21 3.2.4 System data . . . . . . . . . . . . . . . . . . . . 22 BBS name . . . . . . . . . . . . . . . . . . . . . . 22 Key number . . . . . . . . . . . . . . . . . . . . . 22 SysOp name . . . . . . . . . . . . . . . . . . . . . 22 Net address . . . . . . . . . . . . . . . . . . . . 23 Uploader name . . . . . . . . . . . . . . . . . . . 23 3.2.5 Screen settings . . . . . . . . . . . . . . . . . . 24 Redirect screen output of external programs . . . . 24 Normal color . . . . . . . . . . . . . . . . . . . . 24 Highlighted color . . . . . . . . . . . . . . . . . 24 Background color . . . . . . . . . . . . . . . . . . 24 3.2.6 General settings . . . . . . . . . . . . . . . . . . 25 Running under FileDoor . . . . . . . . . . . . . . . 25 Update FILES.BBS / Extended descriptions character . 25 Spaces to indent . . . . . . . . . . . . . . . . . . 25 Download counters . . . . . . . . . . . . . . . . . 26 File-DataBase . . . . . . . . . . . . . . . . . . . 27 Import FILE_ID description . . . . . . . . . . . . . 28 Import FILE_ID description to Ezycom 1.10 . . . . . 29 Describe MOD's . . . . . . . . . . . . . . . . . . . 29 3.2.7 Archive Conversion settings . . . . . . . . . . . . 30 Only process new files . . . . . . . . . . . . . . . 30 Only process listed files . . . . . . . . . . . . . 31 Put FILE_ID description in archive header . . . . . 31 Archive conversion . . . . . . . . . . . . . . . . . 31 Convert ALL archives . . . . . . . . . . . . . . . . 33 Process Self-Extracting archives . . . . . . . . . . 33 Process embedded archives . . . . . . . . . . . . . 33 PalmScan v1.13 User guide ----------------------------------------------------------------------- Add CRC file list . . . . . . . . . . . . . . . . . 34 No title in headers . . . . . . . . . . . . . . . . 34 New archive date . . . . . . . . . . . . . . . . . . 35 3.2.8 Paths / filenames . . . . . . . . . . . . . . . . . 36 Temporary directory . . . . . . . . . . . . . . . . 36 Bad files directory . . . . . . . . . . . . . . . . 36 Infected files directory . . . . . . . . . . . . . . 36 Hacked files directory . . . . . . . . . . . . . . . 37 Old files directory . . . . . . . . . . . . . . . . 37 Bad GIF files directory . . . . . . . . . . . . . . 37 Messagebase path . . . . . . . . . . . . . . . . . . 38 BBS system directory . . . . . . . . . . . . . . . . 38 Files.bbs filename . . . . . . . . . . . . . . . . . 39 Log file / log style . . . . . . . . . . . . . . . . 39 Archive header file . . . . . . . . . . . . . . . . 40 Substitute drive . . . . . . . . . . . . . . . . . . 40 3.2.9 Archivers . . . . . . . . . . . . . . . . . . . . . 41 3.2.10 Archivers - Archive protection . . . . . . . . . . . 42 UC2 protection . . . . . . . . . . . . . . . . . . . 42 RAR lock . . . . . . . . . . . . . . . . . . . . . . 42 3.2.11 Virus scan . . . . . . . . . . . . . . . . . . . . . 43 Files to scan . . . . . . . . . . . . . . . . . . . 43 Virus scanners . . . . . . . . . . . . . . . . . . . 43 Complete scan . . . . . . . . . . . . . . . . . . . 45 3.2.12 HackList . . . . . . . . . . . . . . . . . . . . . . 46 3.2.13 Skip files . . . . . . . . . . . . . . . . . . . . . 46 3.2.14 Pack unpacked . . . . . . . . . . . . . . . . . . . 47 Minimum size . . . . . . . . . . . . . . . . . . . . 47 3.2.15 Remove files . . . . . . . . . . . . . . . . . . . . 47 3.2.16 Add files . . . . . . . . . . . . . . . . . . . . . 48 3.2.17 GIF settings . . . . . . . . . . . . . . . . . . . . 48 Add GIF specifications to descriptions . . . . . . . 48 GIF pack . . . . . . . . . . . . . . . . . . . . . . 49 JFIF unpack . . . . . . . . . . . . . . . . . . . . 49 JPEG unpack . . . . . . . . . . . . . . . . . . . . 50 GIFblast unpack . . . . . . . . . . . . . . . . . . 50 Repack JFIF files . . . . . . . . . . . . . . . . . 50 Repack JPEG files . . . . . . . . . . . . . . . . . 50 Repack GIFblast files . . . . . . . . . . . . . . . 51 Minimum resolution . . . . . . . . . . . . . . . . . 51 GIF test command / failures . . . . . . . . . . . . 51 3.2.18 Old files . . . . . . . . . . . . . . . . . . . . . 52 3.2.19 Information . . . . . . . . . . . . . . . . . . . . 52 3.2.20 Exit to dos . . . . . . . . . . . . . . . . . . . . 52 4 Registration . . . . . . . . . . . . . . . . . . . . . . . . . . 53 5 Credits . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 I Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 PalmScan v1.13 User guide ----------------------------------------------------------------------- 1 Introduction 1.1 Copyright and License Agreement 'PalmScan' refers to all executables and documentation as distributed in the compressed file in which the package was released. Users of PalmScan must accept this disclaimer of warranty: - PalmScan is copyrighted material by Steven Hendriks. It may only be used in agreement with the conditions set out in this license agreement. - PalmScan is released as shareware. - You may use PalmScan for an evaluation period of one month. After this period you MUST either register PalmScan or stop using it. - Registration is REQUIRED for commercial usage (in a commercial environment, such as business, governmental organization, association, school, foundation, or any other form of juridical person, or any system where PalmScan is directly or indirectly used to make profit). - PalmScan may be distributed freely provided no money or any other compensation is asked or accepted without prior written permission from the author. - PalmScan is supplied as is, without warranty or guarantee of any kind, either expressed or implied, as to the fitness for a particular purpose or quality or performance of this program, except that PalmScan will occupy some disk space. - In no event shall Steven Hendriks be liable to you or anyone else for any damages or cost, including, but not limited to, any lost profits, lost savings or lost income which may result from the use or inability to use PalmScan. - In no way is Steven Hendriks obligated to you or anyone else to provide future versions of, or support for PalmScan. - Steven Hendriks reserves the right not to release future shareware versions of PalmScan, but switch to a commercial marketing concept instead. - It is forbidden to modify, adapt, translate, reverse engineer, decompile and/or disassemble the software in this package. Patching the medium at places that carry the software (including, but not limited to, RAM memory and physical media) is seen as a program change and is also forbidden. - Your use of PalmScan constitutes your agreement to this license and disclaimer and your release of the author from any form of liability or litigation. - 5 - PalmScan v1.13 User guide ----------------------------------------------------------------------- 1.2 Contacting the author If you have any problems with PalmScan, or if you wish to contact the author for suggestions etc., you can: - Call Oasis BBS (300 - 28800 bps) at +31-1881-3132 - Send a NetMail message to Steven Hendriks at: Fidonet 2:2802/140 VirNet 9:310/0 DigitalNet 15:1100/300 SIGnet 27:1331/40 OasisNet 52:52/0 AlarmNet 64:300/0 OASE 200:3110/0 - Send E-Mail to: stv_hendriks@hrovx1.hro.nl steven.hendriks@f140.n2802.z2.fidonet.org (preferred) - Send an echomail message in the OASISSOFT support echo. - Send an echomail message in an appropriate area in one of the above networks (I can't read _all_ areas, especially not all Fidonet areas, use netmail if you are not sure whether I'm reading an area or not). - Send a letter to this address: Steven Hendriks Hoofd 22 3214AH Zuidland Netherlands 1.3 What is PalmScan PalmScan is the conversion utility to convert almost any archive to another format. It can check for viruses inside the archives while converting (with up to 20 virus scanners), get file descriptions, process embedded archives, remove/add files from/to archives, full support for GIF packing, and lots more! PalmScan has full FileDoor, FILES.BBS and Remote- Access 2.0x and Ezycom 1.02 and 1.10 file- database support, works with any door.sys or dorinfo supporting bbs program, works great in Allfix and many other programs, or stand-alone! - 6 - PalmScan v1.13 User guide ----------------------------------------------------------------------- 1.4 Features - A very flexible configuration. You can configure almost anything the way you want it. - Detects these archive types: - ARC - PAK * - ZIP * ~ - LHA * - ZOO - SQZ * - HYP - ARJ * ~ @ - HAP - UC2 ~ - RAR * ~ @ * Self-extracting archives are detected. ~ Security envelopes / authenticity validations / seals are detected. @ Multi-volume archives are supported. PalmScan can detect other archives by looking at the archive extension. Other archivers could be added, just send the archiving program to the author and support will be added, if possible. - Supports up to 30 different archive types. - Supports GIF packing. - Full FileDoor support (for FileDoor's ExitAfterUpload). - Special FILES.BBS support. - Full support for the RemoteAccess 2.0x, Ezycom 1.02 and Ezycom 1.10 file-databases, including an advanced maintenance feature. - Virus scanning with up to 20 virus scanners. - Checking files in a hacklist. - Reject files which are too old. - Compress un-archived files with your favourite archiver. - Get file descriptions from FILE_ID.DIZ and DESC.SDI. - Describes music files, like MOD, ScreamTracker, organ files, etc. - Describes Compuserve GIF pictures. - Tests GIF pictures. - 7 - PalmScan v1.13 User guide ----------------------------------------------------------------------- - Ability to notify the SysOp about infected, bad, hacked and old archives and bad GIF files. PalmScan supports Fido (*.msg), Hudson, Squish, Ezycom (both 1.02 and 1.10) and JAM messagebases. - Add and remove files to/from archives. - Add file list with CRC-32's. - Writes a complete log file. - Runs under any BBS system which supports the DOOR.SYS or DORINFO.DEF dropfile format. Without one of these dropfiles, PalmScan can be run in local-only mode. - Supports both ANSI and ASCII when running in online mode. - Built-in Fossil support and carrier detection. - Very user-friendly; virtually anything can be configured. - A very easy-to-use setup program is included. - High quality performance, very low registration fee. 1.5 System requirements - IBM PC, XT, AT or compatible. - IBM PC-DOS or Microsoft MS-DOS 3.0 (or compatible) or higher. - At least 20 file handles ('FILES=20' in your CONFIG.SYS). A lower value can cause 'Out of file handles' errors. - At least 350 KB conventional memory available. - At least one of the following compression utilities: PKARC, PKZIP, LHA, ZOO, SQZ, Hyper, ARJ, HAP, PAK, UC2. - A disk cache can improve performance, but is not required. If you are not using a disk cache, make sure that the number of DOS buffers is at least 30 ('BUFFERS=30' in your CONFIG.SYS) to improve performance. - 8 - PalmScan v1.13 User guide ----------------------------------------------------------------------- 1.6 Logging PalmScan can keep track of its activity in a log file. When no filename is given in the configuration, logging is turned off. The following characters are used in the log, to make things a bit clearer: ! : Fatal error ? : Other (non-fatal) error or an infected/hacked/bad archive has been found $ : User information # : Other information + : Statistics · : Debug information ■ : Debug information, external programs execution 1.7 Included files This package includes: PALMSCAN.EXE The main program PALMSCAN.OVR Overlay file for the message system PALMSCAN.DOC This documentation PSETUP.EXE PalmScan SETUP program PSREG.EXE Self-extracting archive containing the registration forms PALMSCAN.CFG Sample configuration file PALMSCAN.ANS Ansi advertisement FILE_ID.DIZ Package description UPDATE.LOG Update log FILEINFO.INC Technical information about the PalmScan FileInfo system 1.8 Runtime While PalmScan is running, no user input is required. To abort processing of files, you can press escape. PalmScan will then finish the file which is currently being processed, and after that ask whether you wish to continue processing or not. - 9 - PalmScan v1.13 User guide ----------------------------------------------------------------------- 2 Installation 2.1 First time installation PalmScan and all files included can be placed either in a separate directory, or in the BBS directory. the most common way is creating a sub-directory under the BBS directory, and place the files there. After placing all files in a directory, edit PALMSCAN.CFG. 2.2 Installing PalmScan in FileDoor The most common way for installing PalmScan in FileDoor is the following: ExitAfterUpload1 C:\PALMSCAN\PALMSCAN.EXE $U\*.* $N $M $U\*.* tells PalmScan which files to process. $N tells FileDoor to execute PalmScan only when files are received. $M tells FileDoor to swap to disk/EMS before executing PalmScan. I recommend using the 'FileDoor' keyword in the configuration, PalmScan will then tell FileDoor the new filename when a file has been converted, and the original size of the archive. By using 'FileID' also, PalmScan will also tell FileDoor the description (when found in FILE_ID.DIZ or DESC.SDI). You should never use 'FilesBBS' when running under FileDoor. 2.3 Installing PalmScan in SuperBBS The most common way for installing PalmScan in SuperBBS is the following: Virus scanner: c:\xfd\palmscan\palmscan.exe %1 *S %1 tells PalmScan which file to process. *S tells SuperBBS to swap to disk/EMS before executing PalmScan. You should not use archive conversion when PalmScan is used as virus scanner in SuperBBS. After uploads, SuperBBS would not be able to find the file back when it's got another filename. For using archive conversion, you should run PalmScan in an event, with 'FilesBBS' and 'OnlyNewFiles' switched on. - 10 - PalmScan v1.13 User guide ----------------------------------------------------------------------- 2.4 Installing PalmScan in Allfix Allfix version 4.21 (and later) has the option to use an external archive conversion utility. The most common way for installing PalmScan in Allfix at this option is the following: EAC : PALMSCAN.EXE @1 /L /L tells PalmScan to run in local-only mode (Allfix doesn't have a user online anyway...) . @1 tells PalmScan which file to process. The errorlevels should be configured like this: (EAC) virus errorlevel 198 (EAC) error errorlevel 1 PalmScan returns errorlevel 203 for bad archives (archives which can't be unpacked), errorlevel 212 for hacked files and errorlevel 213 for virus-infected archives. With these errorlevel settings in Allfix, it will move the file to the bad directory if one of these occur. You should not configure a 'BadPath' and 'InfectedPath' in the PalmScan configuration, Allfix will move bad or infected archives to the BadTick directory (when the errorlevels are configured as above). Also, 'FilesBBS', 'FDB' and 'FileDoor' should not be used, else PalmScan would create files which are of no use for Allfix. 2.5 Installing PalmScan in RemoteAccess 2.0x The commandline for using PalmScan in the upload scan option in RemoteAccess 2.0x should be: PALMSCAN.EXE @ *M If you are using the file-database in RemoteAccess 2.0x, you should also enable this option ('FDB RA') in the PalmScan configuration. 2.6 Installing PalmScan in The Remote Access Filearea Tools The commandline for using PalmScan in the ARCCONV option in The Remote Access Filearea Tools should be: PALMSCAN.EXE %F @1 /L - 11 - PalmScan v1.13 User guide ----------------------------------------------------------------------- 2.7 Installing PalmScan in Maximus If you don't already use the VirusCheck option in Maximus, you should first uncomment the following line in MAX.CTL: Upload Check Virus Vircheck.Bat If you want to use the DORINFOx.DEF support of PalmScan, you should also make a few changes to the MENUS.CTL file. Usually the upload command is looking like this: Upload Limited "Upload (send)" Maximus includes a mecca script called DORINFO.MEC, which produces a DORINFO1.DEF. The new structure of the upload command should be as follows: Display_File C:\Max\Dorinfo Limited "Upload (send)" NoDsp Upload Limited "U" This way whenever a user begins the upload procedure, a DORINFO1.DEF file is created. You can now edit the VIRCHECK.BAT to include the following: PalmScan %1%2%3 /NoConversion /D[path to DORINFOx.DEF] If you don't want to use the DORINFOx.DEF support, it should be this way: PalmScan %1%2%3 /NoConversion /L Warning! Do not use spaces between the commandline variables (%1,%2 and %3) or nothing will work properly. You can find the location where the DORINFOx.DEF file will be created by viewing the DORINFO.MEC file, located in the Misc directory. You must not forget to SILT (compile) the configuration after changing the .CTL files. When PalmScan finds the archive to be bad or infected, it will remove it from the upload directory. After returning to the BBS, Maximus will then not find the file present and it won't credit the user for it, and the file won't be placed in the FILES.BBS. The 'ArchiveConversion' keyword should not be used in the PalmScan configuration for running PalmScan inside Maximus, while Maximus would think the file is missing when the filename is changed. You can also use the /NOCONVERSION commandline option for PalmScan instead of disabling the ArchiveConversion keyword (this can be especially useful when using PalmScan to convert the archives in an event, and using only one configuration for PalmScan). For doing archive conversions, FileID insertion and FILES.BBS update options, run PalmScan in an event or just after exiting Maximus, with the 'OnlyNewFiles', 'FileID' and 'FilesBBS' keywords turned on. - 12 - PalmScan v1.13 User guide ----------------------------------------------------------------------- 2.8 Installing PalmScan in Ezycom There are various ways of using PalmScan with Ezycom. When using PalmScan in one of the conversion batch-files used by Ezycom, PalmScan will not update the Ezycom file-database. Ezycom will handle this itself, so you should disable 'FDB Ezycom' when PalmScan is started from one of those batch-files. When using PalmScan with UPCONV.BAT, the commandline should be as follows for Ezycom 1.02: PalmScan.Exe %1%4.%6 /NoFDB /NoFilesBBS For Ezycom 1.10, the commandline should be: PalmScan.Exe %2%5.%7 /N%1 /T%6 /NoFDB /NoFilesBBS When used in DOCONV.BAT, /L should be added to that. The best way to use PalmScan with Ezycom is by not using it in these batch-files, but running it in an event with the FDB maintenance feature (/FDBMAINT commandline option). You could also run PalmScan after every caller, processing only the upload directory (/FDBMAINT<areanr>). - 13 - PalmScan v1.13 User guide ----------------------------------------------------------------------- 2.9 Commandline The PalmScan commandline consists of: PALMSCAN.EXE [FileSpecs|@ListFile|Command] <Options> [..] is mandatory <..> is optional [FileSpecs] must be valid DOS file-specifications. At least one should be given, up to 30 can be given. File-specifications can be either filenames or directories. In the last case, all files in that directory will be processed. Example : PalmScan *.ZIP [@ListFile] Instead of (a) file-specification(s), you can also use a listfile. This listfile should contain valid file-specifications (see above). PalmScan will process all file-specifications in the listfile (there is no maximum size for the listfile!). The file-specifications should be placed on the first part of each line, 2everything behind it will be ignored. Example listfile: d:\files\upload This is the upload directory d:\files\incoming This is the incoming files directory In this example, all files in the directory's d:\files\upload and d:\files\incoming, will be processed (except for those files configured with the SkipFile keyword in the PalmScan configuration). The comments behind the directory's will be ignored. You can also use FLSEARCH.CTL (QuickBBS format) with this option. Example : PalmScan @C:\BBS\FLSEARCH.CTL - 14 - PalmScan v1.13 User guide ----------------------------------------------------------------------- [Command] : /FDBmaint<areanr<-areanr>> Usage : Run Ezycom/RemoteAccess file-database maintenance. PalmScan will first search the file-database for files which have not been processed, and place them in a file called FILEINFO.FIX. After that, the PalmScan FileInfo system will take over and those files will be processed. Files will be converted to the archiver configured in the Ezycom/RemoteAccess file-area configuration. When no archiver is configured for an area, PalmScan will not process files in that area. When running with Ezycom, PalmScan will use the checked bit in the file-database to determine wether a file has been processed or not. When running with RemoteAccess, PalmScan uses LASTSCAN.PS in the file-database directory to store the last time when the FDB maintenance has been run. All files which have an upload date after the date of that file will be processed. <areanr-<areanr>> The area numbers which should be processed. A range of areas can be given here (eg. 10-20) or just one area can be given. When no area number is specified, PalmScan will process all areas which have a destination archiver configured. Any file specifications given on the commandline will be used to determine wether a file should be processed or not. Option : /All Process all files in the specified area's, even if they have already been processed. Example : PalmScan.Exe /L /FDBMAINT50-99 /ALL *.ARJ - This will process all *.ARJ files which are in the file-database in areas in the range 50 to 99 which have a destination archiver configured in the Ezycom/RemoteAccess file-area configuration. - 15 - PalmScan v1.13 User guide ----------------------------------------------------------------------- /Fix<+> Usage : Use the PalmScan FileInfo system. This system accomplishes an enhanced communication between PalmScan and programs using PalmScan. When using /FIX, PalmScan will use the FileInfo system in Read-Only mode, the FileInfo file (FILEINFO.FIX) will be deleted when all files have been processed. When using /FIX+, PalmScan will use the FileInfo system in Read/Write mode. PalmScan will update the FileInfo file with some information that can be used by the program which is calling PalmScan. Technical information about the FileInfo system can be found in FILEINFO.INC, which is included in the PalmScan package. <options> : /L Usage : Local operation. When this switch is NOT used, PalmScan will search for DOOR.SYS and/or DORINFO?.DEF to get the user information from. /C[configuration-filename] Usage : By default, PalmScan will search for it's configuration file in the same directory where PALMSCAN.EXE is placed, with the filename PALMSCAN.CFG. With this commandline option, you can tell PalmScan to use an alternate configuration file. Example : /Cc:\palmscan\afixpalm.cfg /D[dorinfo-filename] Usage : When your BBS-package creates a DORINFO file with a filename that can't be found by searching for DORINFO?.DEF (ie. Ezycom can create DORINF85.DEF for line 85), you can specify this filename here. Example : /Ddorinf85.def /N[node] Usage : When the node number is specified with this commandline option, PalmScan's multi-line support is enabled. This makes sure that PalmScan will run without problems when running on more nodes at the same time on multi-node systems. This commandline option is required when using the EzyFileID configuration keyword. - 16 - PalmScan v1.13 User guide ----------------------------------------------------------------------- /NoConversion Usage : When this option is used, no archiving will be done at all. This means that no archive will be converted, there won't be any file removal or file adding, no music modules will be described, and the archive header will not be updated. This can be especially useful for running PalmScan as online virus scanner (when the archive conversion is done in an event), or for just updating file descriptions in FILES.BBS with the 'FileID' keyword used. /T[archiver] Usage : Override the configured destination archiver. When no archiver is configured in the PalmScan configuration, PalmScan will only convert the main archives, no embedded archives. When there is an archiver configured in the PalmScan configuration, those settings will be used for SFX/Secure/Embedded archives. When used when running the file-database maintenance, PalmScan will still only process those areas which have a destination archiver configured (in the Ezycom/RemoteAccess file-area configuration). This commandline option does override that configured archiver, though. Example : /TARJ Note : This option is available in the registered version only. /NoFDB Usage : Temporary disable the file-database support. Note : This option is available in the registered version only. /NoFilesbbs Usage : Temporary disable the files.bbs support. Note : This option is available in the registered version only. /S Usage : When this option is used, PalmScan will search all sub- directory's of the given file-specifications for files to be processed. Together with the ProcessListedOnly configuration keyword, this option can very well be used to process all files on a bulletin board. - 17 - PalmScan v1.13 User guide ----------------------------------------------------------------------- /Unlisted Usage : When this option is used, PalmScan will only process files which are not listed in FILES.BBS and/or the RemoteAccess / Ezycom file-database. This commandline option overrides the ProcessListedOnly configuration keyword. /Move[Path] Usage : When a file has been processed and is ok, it can be moved to another directory. [Path] The directory where good files will be moved to. /NoMove Usage : Temporary disable the moving of files to the BadPath, InfectedPath, HackPath, OldPath and BadGifPath. When needed, PalmScan will exit with an errorlevel instead of moving any files. /Mono Usage : Forces monochrome mode. /NoCls Usage : Do not clear the screen at startup. /NoReg Usage : Do not display 'Registered to ...' at startup. Note : This option is available in the registered version only. /Debug Usage : This will log some more information on the execution of external programs (such as virus scanners, archivers, etc.) and virtually anything which is displayed on the screen. - 18 - PalmScan v1.13 User guide ----------------------------------------------------------------------- 2.10 Watchdog, CTTY, ANSI.SYS CTTY and WATCHDOG, or similar utilities, are not required and should not be used with this program. PalmScan has its own communication routines which monitor the COM port. ANSI.SYS is not required for this program. When running under DESQview, DVANSI is not required either. It won't do any harm if either one is loaded however. 2.11 Errorlevels PalmScan returns the following errorlevels: 1 - Error 203 - Bad archive found 204 - Old file found 205 - Bad GIF file found 212 - Hacked archive found 213 - Infected file found The errorlevels 203, 212 and 213 will only be returned when no directory is configured to move those files to. - 19 - PalmScan v1.13 User guide ----------------------------------------------------------------------- 3 The configuration 3.1 PALMSCAN.CFG The PALMSCAN.CFG file is a normal (ASCII) text-file. You can create this file with any ASCII-editor. PalmScan will search for its configuration file in the directory containing PALMSCAN.EXE, or the configuration file specified on the commandline (see chapter 2.7). If no configuration file is found, PalmScan will terminate abnormally. PALMSCAN.CFG contains many options. Some of them are optional, others are not. The general format for the PALMSCAN.CFG file is: {statement} [mandatory parameter] <optional parameter> There are no restrictions to the position you start the parameters, but the parameters have to be separated with one or more spaces. The {statement} must start on position 1 of each line. When there should be spaces in a parameter (like in the archiver commands), you can use underscores ('_') for that, PalmScan will translate those in spaces. You can insert comment-lines into PALMSCAN.CFG by putting a '%' or a ';' character on position 1 of the desired line(s). Also empty lines are considered as comment. - 20 - PalmScan v1.13 User guide ----------------------------------------------------------------------- 3.2 PSetup Besides editing the configuration file with an ASCII editor, you can also configure PalmScan with PSetup. PSetup uses the same ASCII text-file as PalmScan. 3.2.1 Commandline The PSetup commandline consists of: PSETUP [configuration-filename] </A|-A> [configuration-filename] Usage : By default, PSetup will search for it's configuration file in the same directory where PSETUP.EXE is placed, with the filename PALMSCAN.CFG. With this commandline option, you can tell PSetup to use an alternate configuration file. </A|-A> Usage : When PSetup is started with /A or -A on the commandline, it will use an alternate colorset. Example : PSETUP c:\palmscan\afixpalm.cfg /A 3.2.2 Starting PSetup When you run PSetup, it will look for the configuration file as stated in paragraph 3.2.1. When no configuration file is found, it will inform you of this. The configuration file will then be created when you exit PSetup. 3.2.3 Keys PSetup uses pop-up menus. You can use the cursor up and down keys to move through the menus, and select an option by pressing Enter. The Escape key will take you back to a previous level. In all edit fields, Escape aborts and F10 keeps changes immediately (if you didn't select the 'Cancel' button). Cursor-Down and Tab moves the cursor to the next field, Cursor-Up and Shift-Tab moves the cursor to the previous field. Enter will move the cursor to the next field when on an edit field, and press a button when that button is currently selected. The space bar toggles on/off settings, Cursor-Left/Right will move through selection fields. F1 will display the relevant part of the PalmScan documentation when the cursor is located on a data entry. PalmScan.Doc must be located in the same directory where PSetup.Exe is located for this function to work. - 21 - PalmScan v1.13 User guide ----------------------------------------------------------------------- 3.2.4 System data Here you can enter some information about your system. BBS name Keyword : BBSname [BBS_name] Usage : This option informs PalmScan of your BBS name. This option is only of use when you registered PalmScan and also use the RegKey statement. [BBS_name] This is your BBS name. Example : BBSname Oasis_BBS Key number Keyword : RegKey [nnnnn] Usage : When you registered PalmScan, you received a key for use with PalmScan. Enter this key with this keyword in the configuration so that PalmScan will display 'Registered to ...' instead of 'Unregistered evaluation copy', and all bonus features will be enabled. If you have not already registered PalmScan, please see the registration form for details on how to register. [nnnnn] This is your key number as you receive it after registering PalmScan. Example : RegKey 123456 SysOp name Keyword : SysopName [Sysop_Name] Usage : When writing messages in a Fido-style message board, PalmScan will write those messages to 'SysOp', unless your name is specified here, then it will write to your name. [Sysop_Name] Your name. Example : SysopName Steven_Hendriks - 22 - PalmScan v1.13 User guide ----------------------------------------------------------------------- Net address Keyword : NetAddress [Zone:Net/Node<.Point>] Usage : Here you can specify you main network address, as installed in your mailer configuration. This is only used for messages created when bad or infected archives are found. If you don't have any network address, you don't have to enter anything here either. [Zone:Net/Node<.Point>] Your network address. <.Point> is optional. Example : NetAddress 2:2802/140 Uploader name Keyword : UploaderName [Name] Usage : By default, PalmScan uses 'PalmScan' and the version number as uploader name for files added to the RemoteAccess / Ezycom file-database. With this configuration keyword, you can specify an other name to use as uploader name. [Name] The name to be used as uploader name. Note : This option is available in the registered version only. - 23 - PalmScan v1.13 User guide ----------------------------------------------------------------------- 3.2.5 Screen settings Redirect screen output of external programs Keyword : RedirectOutput Usage : PalmScan can redirect output of external programs (archivers and virus-scanners) to NUL. This means that those programs will display nothing to the local screen. Some programs, however, will still get output on the screen (like TBScan and F-Prot). When that happens, PalmScan will restore the screen to it's original looks after the external program has been executed. Enabling this option will cause the display on the local (SysOp) screen to be exactly the same as the display on the user screen. Example : RedirectOutput Normal color Keyword : ColorNormal [c] Usage : With this keyword, you can configure the color of normal text in PalmScan. [c] This is the color number. This can be any value from 0 to 15. Example : ColorNormal 3 Highlighted color Keyword : ColorHighlight [c] Usage : With this keyword, you can configure the color of highlighted text in PalmScan. [c] This is the color number. This can be any value from 0 to 15. Example : ColorHighlight 11 Background color Keyword : ColorBackground [c] Usage : With this keyword, you can configure the background color in PalmScan. [c] This is the color number. This can be any value from 0 to 7. Example : ColorBackground 0 - 24 - PalmScan v1.13 User guide ----------------------------------------------------------------------- 3.2.6 General settings Running under FileDoor Keyword : FileDoor Usage : PalmScan has full FileDoor support. When this option is used, and archives are converted, PalmScan will inform FileDoor of the change in filesize and change of filenames. In cooperation with FileID, PalmScan will also give FileDoor the description of the file (when a FILE_ID.DIZ or DESC.SDI file was found inside the archive). When running in local-only mode (/L commandline option), PalmScan will not update any FileDoor files. Example : FileDoor Note : PalmScan assumes you are using FileDoor version 3.10ΓP or higher. If you are using an older version, you should not use the FileDoor parameter in cooperation with the FileID parameter, while the way FileDoor handles these descriptions has been changed in version 3.10ΓP. Update FILES.BBS / Extended descriptions character Keyword : FilesBBS [c] Usage : When this option is set, PalmScan will update the filename in the FILES.BBS file list when archive conversion is done, and, in cooperation with FileID, put the description of the file in this file list. [c] For using extended descriptions (descriptions consisting of multiple lines), PalmScan should know the character which is used by you BBS system for this option. SuperBBS uses '>', RemoteAccess uses '+'. By default, no extended descriptions character is used. Example : FilesBBS > Note : When no extended descriptions character is used, PalmScan cannot remove extended descriptions when adding a new description. Spaces to indent KeyWord : IndentSpaces [nn] Usage : With this option, you can set the number of spaces that should be indented in the FILES.BBS, before extended descriptions. Example : IndentSpaces 27 - 25 - PalmScan v1.13 User guide ----------------------------------------------------------------------- Download counters Keyword : DownloadCounter [l] [r] [nnn] Usage : When a missing file has been added to the FILES.BBS files list, or when an extended description has been added, PalmScan will also update the download counter when you set this option. [l] This is the character that is being used as left bracket in the download counters. [r] This is the character that is being used as right bracket in the download counters. [nnn] This is the number of characters (numbers) that should be used in between the brackets. Example : DownloadCounter [ ] 3 - 26 - PalmScan v1.13 User guide ----------------------------------------------------------------------- File-DataBase Keyword : FDB [RA|Ezycom] Usage : PalmScan has full support for the RemoteAccess 2.0x and Ezycom 1.02 and 1.10 file-database. With this keyword, you can enable this. Filenames, sizes, dates, descriptions, etcetera are updated by PalmScan when needed. [RA] PalmScan will use the RemoteAccess 2.0x file-database. When an infected file is found, PalmScan will use the normal procedure to either move the file or exit with an errorlevel, and besides this it will also mark the file as deleted, unlisted and/or not available, according to the settings in the RemoteAccess configuration. When an archive can not be unpacked, PalmScan will also use the normal procedure, and it will mark the file as not available in the file-database. [Ezycom] PalmScan will use the Ezycom 1.02 or 1.10 file-database. PalmScan will detect the used version when reading the Ezycom configuration. When an infected file, an archive which can't be unpacked, or a file which exists in the HackList was found, PalmScan will use the normal procedure to either move the file or exit with an errorlevel, and it will mark the file as offline in the Ezycom file-database. When the FileID keyword is used with Ezycom 1.02, PalmScan will filter out all ascii control codes and all high ascii, and place the first non-empty line at the description in the Ezycom file-database. When using it with Ezycom 1.10, all description manipulation features are available. To prevent problems, here is some inside information: * When you are using on directory for different file areas in RemoteAccess/Ezycom, PalmScan will always use the FIRST area which uses the same directory as where the file which is being processed was found. * When PalmScan adds a description to the file- database, the old description will not be removed from the RemoteAccess database text. It will not be used for the file anymore, but will remain on your disk. To remove the old description, you should run RAFILE COMPRESS. * When PalmScan adds an unlisted file to the RemoteAccess file-database, it will add the default settings as configured in the RemoteAccess file- area configuration. Example : FDB RA - 27 - PalmScan v1.13 User guide ----------------------------------------------------------------------- Import FILE_ID description Keyword : FileID <OneLine> <Filter> <FiltLow> <MaxWidth=value> <MaxLines=value> Usage : When this switch is set, PalmScan will import the description from the FILE_ID.DIZ or DESC.SDI file to FileDoor, FILES.BBS or the RemoteAccess file-database. <OneLine> Instead of placing descriptions from FILE_ID.DIZ or DESC.SDI on multiple lines (with the extended descriptions character), PalmScan can put those descriptions on one long line. To use this, OneLine must be specified at the FileID keyword. <Filter> PalmScan can filter out high ASCII (characters 128 to 255) from FILE_ID.DIZ or DESC.SDI descriptions. When this switch is used, all high ASCII characters will be removed from the description, and empty lines (which can be caused by removing high ASCII characters when a line consists of only those characters) will be removed. <FiltLow> PalmScan can filter out ASCII control-codes (characters 0 to 31) in FILE_ID.DIZ or DESC.SDI descriptions before importing them. <FiltDraw> PalmScan can filter out standard ASCII drawings (for which characters within the range 32 to 126 are used) in descriptions. This works a bit different than the control codes (FiltLow) and high ASCII (Filter) filter functions, while not everything should be filtered out. Just try it to see what it can do... <MaxWidth=value> The maximum width of imported descriptions can be configured with this option. <MaxLines=value> The maximum number of lines of imported descriptions can be configured with this option. Example : FileID OneLine Filter FiltLow FiltDraw MaxWidth=50 MaxLines=25 - 28 - PalmScan v1.13 User guide ----------------------------------------------------------------------- Import FILE_ID description to Ezycom 1.10 Keyword : EzyFileID Usage : When running online under Ezycom 1.10, PalmScan can place the FILE_ID.<node> file in the temporary directory as configured in the Ezycom configuration. Ezycom will then import this description in the file-database. To use this feature, the node on which PalmScan is running must be specified on the commandline with the /N[node] commandline option. Also, the FileID keyword must be used in the PalmScan configuration. The OneLine, Filter, FiltLow and FiltDraw options also work with this function. The 'FDB Ezycom' keyword should not be used with this, or the /NOFDB commandline option should be used, the file-database support won't work when running in UPCONV.BAT anyway while Ezycom places uploaded files in a temporary upload directory. When running in local-only mode (/L commandline option) PalmScan will never create the FILE_ID.<node> file. Example : EzyFileID Describe MOD's Keyword : DescribeMod <OnlyMainArchive> Usage : PalmScan has the ability to describe MOD, NST, STM (ScreamTracker Modules), 669, JMusic and Organ music files. PalmScan will put the description of those files in a FILE_ID.DIZ descriptions file, which will be packed with the other files in the archive. This will only be done when no executables are found in the archive (ie. the archive only consists of music files), or when a FILE_ID.DIZ already exists in the archive (PalmScan will add the descriptions of the music files to this FILE_ID.DIZ in this case). With this keyword, you can enable this option. <OnlyMainArchive> When this switch is specified, only modules in the main archive will be described. When embedded archives are being processed, modules in those archives will be ignored. This is only valid when the ArchInArch keyword is used. When that keyword is not used, embedded archives would not be processed at all so modules in those archives would never be described either. Example : DescribeMod OnlyMainArchive - 29 - PalmScan v1.13 User guide ----------------------------------------------------------------------- 3.2.7 Archive Conversion settings Only process new files Keyword : OnlyNewFiles <method> Usage : For running PalmScan in a daily event, it's possible to process only new files. When this option is used, PalmScan will only process files with the archive attribute set, and remove this attribute when a file has been processed, thus processing files only once. <method> By default, PalmScan will use the archive attribute on files to determine whether a file has been processed earlier or not. There are two other methods available: FileDate In this case, PalmScan will only process files which have a file date and time later than the last time a file has been processed in that directory. PalmScan will store the date in a file called LASTSCAN.PS, in the directory where the file was found. Because LASTSCAN.PS only contains the last date and time a file has been processed, it will affect the processing of ALL files in that directory. This method will use a directory entry (0-byte file) for each processed directory. DataFile In this case, PalmScan will only process files which are not found in the data file, and files with a changed size, date or time. The file which is used to store the data is called PALMSCAN.DAT. PalmScan uses separate datafiles for separate directory's, so when a file is being moved, it will also be processed. This method uses 12 bytes of disk space for each processed file (and a directory entry in each processed directory). The DataFile method is the most secure OnlyNewFiles method; The archive attribute method fails on systems where the archive attribute is being reset by another program (some backup programs do that), and the file date method affects complete directory's, where this method affects only the file which is processed. Example : OnlyNewFiles DataFile - 30 - PalmScan v1.13 User guide ----------------------------------------------------------------------- Only process listed files Keyword : ProcessListedOnly Usage : By default, all files which comply with the given file specifications (and are not specified with the SkipFile keyword) will be processed. With this keyword, you can tell PalmScan to only process files which are listed in the FILES.BBS files list (when the FilesBBS keyword is used) and/or the RemoteAccess / Ezycom file-database (when the FDB keyword is used). Example : ProcessListedOnly Note : This feature is available in the registered version only. Put FILE_ID description in archive header Keyword : FileIDarchiveHdr Usage : When this switch is on, PalmScan will add the description from FILE_ID.DIZ or DESC.SDI to the archive header. When an archive header is already being added (ArchiveHeader keyword), the description will be appended to it. Example : FileIDarchiveHdr Archive conversion Keyword : ArchiveConversion [ttt] <OnlyMainArchive> <NoSFX> <NoSecure> <ToSFX> Usage : This option sets the target archive system. When no target archive system is set, no archive conversion will be done. [ttt] This sets the target. You can supply all values you configured with the Archiver statement. <OnlyMainArchive> When this switch is specified, only main archives will be converted to the target archive type. Embedded archives will still be processed for other options when ArchInArch is used, but those archives won't be converted. - 31 - PalmScan v1.13 User guide ----------------------------------------------------------------------- <NoSFX> When this switch is specified, self- extracting archives will not be converted to the target archive type, and no files will be removed from those archives. Also, the /NOCONVERSION commandline option will be used on archives embedded in self-extracting archives. <NoSecure> When this switch is used, secure archives (archives with a security envelope, authenticity verification or seal) will not be converted, no files will be removed or added, no music modules will be described, and an archive header will not be added to secured ARJ and UC2 archives. Also, the /NOCONVERSION commandline option will be used on archives embedded in secure archives. PalmScan can detect ARJ security envelopes, PkZIP (both 1.xx and 2.0x) and RAR authenticity verifications and UC2 seals. Note : This option is available in the registered version only. <ToSFX> When converting arcguces to self- extracting archives, this switch should be used. PalmScan will then use .EXE as the extension instead of the default extension which is configured for that archiver with the Archiver configuration keyword. Note : This option is available in the registered version only. Example : ArchiveConversion ZIP OnlyMainArchive NoSecure - 32 - PalmScan v1.13 User guide ----------------------------------------------------------------------- Convert ALL archives Keyword : ConvertAll <OnlyMainArchive> Usage : Normally, PalmScan will only convert archives of other types than the target archive system. With this option you can tell PalmScan to convert all archives, even if it's already of the target archive type. <OnlyMainArchive> When this switch is specified, only main archives which are already in the target archive type will be converted, embedded archives which are already in the target archive type won't be converted. (This is only of use when the ArchInArch keyword is used). Example : ConvertAll OnlyMainArchive Process Self-Extracting archives Keyword : ProcessSFX <OnlyMainArchive> Usage : By default, Self-Extracting (SFX) archives, are not recognised as being archives. With this switch, you can tell PalmScan to process SFX archives, just like every other archive. PalmScan can detect ZIP, LHA, SQZ, ARJ and PAK SFX archives. <OnlyMainArchive> When this switch is specified, embedded SFX archives will not be processed. Example : ProcessSFX OnlyMainArchive Process embedded archives Keyword : ArchInArch Usage : PalmScan has the ability to process embedded archives. With this statement you can enable this feature. When ArchInArch is enabled, PalmScan will swap itself to XMS, EMS or disk, and startup another copy of itself. PalmScan leaves only 1k of memory used, so it should be able to handle well over 300 levels of embedded archives. PalmScan will do some things less with those embedded archives, than with main archives. It will not add archive headers, or move infected or bad archives (instead it will tell it's parent to do so). Example : ArchInArch Note : This is the main switch for embedded archive processing. When this is not used, all OnlyMainArchive switches will have no meaning. - 33 - PalmScan v1.13 User guide ----------------------------------------------------------------------- Add CRC file list Keyword : AddCRCfile <OnlyMainArchive> Usage : PalmScan can create a list with all filenames, sizes, dates and CRC-32's of all files in the archive. This file will look like this: CRC-32 files list for : ARCHIVE.EXT Created by PalmScan 1.12 on BBS name File Size Date Time CRC-32 ----------------------------------------------- FILENAME.EXT XXXXXXXX XX-XX-XXXX XX:XX XXXXXXXX ----------------------------------------------- The filename of the list will be the same as the archive filename, with extension .CRC. <OnlyMainArchive> When this switch is specified, PalmScan will only create a CRC-32 list in the main archive. Embedded archives will not get a CRC-32 list. Example : AddCRCfile OnlyMainArchive Note : The BBS name will only be added for registered users. No title in headers Keyword : NoTitleInHdr Usage : By default, PalmScan will add it's title to archive headers, when an archive header is added (with the keywords ArchiveHeader and FileIDarchiveHdr). With this option, you can disable it. Example : NoTitleInHdr Note : This option is available in the registered version only. - 34 - PalmScan v1.13 User guide ----------------------------------------------------------------------- New archive date Keyword : Touch <Original|Today|Latest|Oldest|ResetFuture> Usage : When an archive has been processed, PalmScan can touch the file date and time on the archive. There are four possible ways: <Original> The processed archive will get the same date and time as the original archive. This is the default setting. <Today> The processed archive will get the current date and time. <Latest> The processed archive will get the date and time of the latest (newest) file in the archive. <Oldest> The processed archive will get the date and time of the oldest file in the archive. <ResetFuture> The processed archive will get today's date only when the original archive's date is a future date. When the original archive's date is a correct (older) date, the new archive will get the same date as the original archive. Note : This feature is available in the registered version only. - 35 - PalmScan v1.13 User guide ----------------------------------------------------------------------- 3.2.8 Paths / filenames Temporary directory Keyword : TempPath [d:\path] Usage : TempPath should point to a directory where PalmScan will store temporary files. This directory is necessary for running PalmScan. [d:\path] This is the directory where the temporary files will be stored. When no temporary directory is configured, PalmScan will use the TEMP environment variable (when available). For more information about environment variables, consult your DOS documentation. Example : TempPath C:\TEMP Bad files directory Keyword : BadPath [d:\path] Usage : When a bad file has been encountered (ie. the file cannot be unpacked although it is an archive), PalmScan can move it to this directory. When this option is not used, PalmScan will exit with errorlevel 203 instead of moving the bad archive. [d:\path] This is the directory where PalmScan will move bad files to. Example : BadPath C:\FILES\BAD Infected files directory Keyword : InfectedPath [d:\path] Usage : When a virus has been found, PalmScan will move the file so you can investigate it further. When this keyword is not used, PalmScan will exit with errorlevel 213 instead of moving the infected file. [d:\path] This is the directory where PalmScan will move infected files to. Example : InfectedPath C:\FILES\INFECTED - 36 - PalmScan v1.13 User guide ----------------------------------------------------------------------- Hacked files directory Keyword : HackPath [d:\path] Usage : When a file has been found in the hacklist, PalmScan will move this file so you can investigate it further. When this keyword is not used, PalmScan will exit with errorlevel 212 instead of moving the hacked file. Example : HackPath C:\FILES\HACKED Old files directory Keyword : OldPath [d:\path] Usage : PalmScan can check for files which are too old. When this check is configured (with the OldFiles configuration keyword), old files will be moved to the path configured with OldPath. When no OldPath is configured, PalmScan will exit with errorlevel 204 when encountering files which are too old. Example : OldPath C:\FILES\OLD Bad GIF files directory Keyword : BadGifPath [d:\path] Usage : When a bad GIF file (a GIF file with a resolution which is too low (MinimumResolution configuration keyword) or which failed the GIF test (GIFtest configuration keyword), the file will be moved to the path configured with BadGifPath. When no BadGifPath is configured, PalmScan will exit with errorlevel 205 on bad GIF files. Example : BadGifPath C:\FILES\BADGIF - 37 - PalmScan v1.13 User guide ----------------------------------------------------------------------- Messagebase path Keyword : MessageArea [Type]<Number>[Path] Usage : When an infected file or a bad archive has been found, PalmScan can post a message to you, describing which archive contains infected file(s), which scanner(s) reported this, what action has been taken and which user was online at the time (when running in online mode). In addition to this, reports created by the virus scanner(s) which detected one or more virus(es) can be added to the message (for more information about this, read ******). By specifying a message area, this feature is enabled. PalmScan supports these messagebase types: Fido : F followed by the message path. Example : FC:\FD\NETMAIL Hudson : H followed by a 3 digit area number followed by the messagebase path. Example : H001C:\SBBS\MSGBASE Squish : S followed by the full path and filename of the message area. Example : SC:\MAX\MSG\PALMSCAN Ezycom 1.02 : E followed by the 4 digit area number followed by the messagebase path. Example : E0001C:\EZY\MSGBASE Ezycom 1.10 : Z followed by the 4 digit area number followed by the messagebase path. Example : Z0001C:\EZY\MSGBASE JAM : J followed by the full path and filename of the message area. Example : JC:\RA\MSG\PALMSCAN Because of the large code size consumption, the message system has been placed in an overlay file (PALMSCAN.OVR). If you do not use the message system, the overlay file can be removed. BBS system directory Keyword : BBSpath [d:\path] Usage : When using the RemoteAccess/Ezycom file-database ('FDB' keyword), PalmScan has to read some information from the RemoteAccess/Ezycom configuration. Either the RA/EZY environment variable or this keyword must be configured to be able to use the file-database. Example : BBSpath C:\RA - 38 - PalmScan v1.13 User guide ----------------------------------------------------------------------- Files.bbs filename Keyword : FilesBBSname [filename] Usage : By default, PalmScan will use the file FILES.BBS in the same directory as the processed files, when the FilesBBS keyword is used. With this option, you can configure the filename for this files list. When it is configured to another name than FILES.BBS, PalmScan will first try this file, and if that fails it will still use the normal FILES.BBS. This option can be used for 4DOS DESCRIPT.ION files, or when you have your files list in a sub-directory of the directory where the files are located. When the latter is used, PalmScan will use this sub-directory for the files list, and when the sub-directory does not exist, the normal FILES.BBS will be used. Example : FilesBBSname LIST\FILES.BBS Log file / log style Keyword : LogFile [d:\path\filename.ext] <Compact|Expanded> Usage : PalmScan can keep track of its activity in a logfile. When this option is not used, no logging will be done. [d:\path\filename.ext] This is the full path and filename of the logfile PalmScan should maintain. When running on a multi-node system, PalmScan can use different log files for different nodes. %N in the log filename will be replaced by the node number on which PalmScan is running (this node number must be specified with the /N commandline option). When only a filename (no path) is configured, PalmScan will put the log file in the same directory as where PalmScan.Exe is located. <Compact> This is the default log style : ---------- Sat 01 Jan 94, PalmScan ... $ 12:34:56 Local operation <Expanded> This is an alternate log style : $ 01-Jan 12:34:56 PSCN PalmScan ... $ 01-Jan 12:34:56 PSCN Local operation Example : LogFile C:\LOG\PSCAN%N.LOG Expanded - 39 - PalmScan v1.13 User guide ----------------------------------------------------------------------- Archive header file Keyword : ArchiveHeader [d:\path\filename.ext] Usage : PalmScan can add a header to your archives. When this parameter points to a valid ASCII textfile, this file will be used as header for the archive. [d:\path\filename.ext] This is the full path and filename to the header text file. When using UC2 as archiver, PalmScan can also add multimedia banners. The file configured with the ArchiveHeader keyword will be added as TXT banner, for multimedia banners, you should put the GIF/JPG/MOD/ASK files in the same directory and filename as the configured archive header, and with extension GIF/JPG/MOD/ASK. If you don't want to use the TXT banner, but do want to use other banners, you should put the filename of the other banners at the ArchiveHeader keyword without extension or with an extension of a non- existing file (never put GIF/JPG/MOD extensions there, PalmScan will then add these files as archive banner as if they were normal text files). Example : ArchiveHeader C:\PALMSCAN\HEADER.ASC Substitute drive Keyword : SubstDrive [Drive letter] Usage : When archiving files with sub-directory's, some archivers add complete path names instead of only the sub-directory's names to the archives. PalmScan can use a substituted drive for the archive conversion to make sure the correct directory names are in the archives. PalmScan will then call SUBST before every pack/unpack command. [Drive letter] The drive letter must be an unused drive and should be available when PalmScan is running (please test it with the SUBST command before using it in PalmScan). When an error occurs while SUBST is being called, PalmScan will use the normal pathname. Example : SubstDrive F - 40 - PalmScan v1.13 User guide ----------------------------------------------------------------------- 3.2.9 Archivers Here you can define the name and commandline options for compression and decompression programs. Please make sure that the programs can be found in your path, or include a full path before the commands. Keyword : Archiver [ext] [compression] [decompression] <[addheader] <multi-volume switch>> Usage : This option can be used to tell PalmScan the archiver commands. [ext] This is the normal extension of archives created by this archiver. This will also be used as the name of the archiver within PalmScan. [compression] This is the full command for this archiver to compress files. [decompression] This is the full command for this archiver to extract archives. <addheader> This is the full command for this archiver to add a header to an archive (if available for this archiver). <multi-volume switch> The commandline option that should be added to the decompression command, to enable multi-volume support. (RAR doesn't need any switch, ARJ uses -v). Example : Archiver ARC pkarc_a pkxarc_-r_-e pkarc_x< Archiver PAK pak_a_/i pak_e_/wa pak_h< Archiver ZIP pkzip_-ex_-r_-p pkunzip_-o_-d pkzip_-z< Archiver LHA lha_a_/rxpatm lha_x_/c Archiver ZOO zoo_aPh zoo_eO// zoo_cA< Archiver ARJ arj_a_-r arj_x_-y arj_c_-z -v Archiver SQZ sqz_a_/p3_/s sqz_x_-o1 Archiver HAP hap_a pah_e Archiver UC2 uc_a_-s_-tt_-f_-b uc_e_-s_-f_!ban=off uc_a_-tt_-f_-b Archiver RAR rar_a_-r_-y_-o-_-std_-m5 rar_x_-r_-y_-o-_-std_-c- rar_c_-y_-std_-av Note : You can use up to 30 archivers in PalmScan. However, the first 11 are reserved for ARC, PAK ZIP, LHA, ZOO, SQZ, HYP, ARJ, HAP, UC2 and RAR (which PalmScan can automatically detect), so that leaves 19 others. PalmScan will look at the extensions of those 19 other archive types to determine what type it is. - 41 - PalmScan v1.13 User guide ----------------------------------------------------------------------- 3.2.10 Archivers - Archive protection UC2 protection Keyword : UC2protection <BasicUpdates> <Delete> <Add> <Optimize> <Unprotect> <ReviseComment> Usage : When an archive has been converted to UC2, PalmScan can add all available UC2 protections to it. By default, no protection will be added. <BasicUpdates> Disable basic updates on processed archives. <Delete> Disable deleting files in processed archives. <Add> Disable adding files to processed archives. <Optimize> Disable optimize on processed archives. <Unprotect> Disable unprotect on processed archives. <ReviseComment> Disable comment revising on processed archives. Example : UC2protection Add Unprotect ReviseComment RAR lock Keyword : RARlock [command] Usage : When an archive has been converted to RAR, PalmScan can add a lock to it. By default, RAR archives will not be locked. [command] To enable RAR archive locking, the command to lock a RAR archive must be configured here. When you are a registered RAR user, an authenticity validation can also be added here. Example : RARlock RAR_k_-av - 42 - PalmScan v1.13 User guide ----------------------------------------------------------------------- 3.2.11 Virus scan Files to scan Keyword : VirusScan <filespec> <filespecs> Usage : When this switched is used, PalmScan will scan for viruses inside all files with the scanners configured with the Scanner parameter. When this switch is not set, no virus scanning will be done. <filespec> This can be any valid DOS file specification. When you give any filespec (you may use up to 50 of them here), PalmScan will only execute the virus scanner(s) when one or more file(s) have been found that meet the requirements of these file specifications. When no file specifications are given, PalmScan will always execute the virus scanner(s). (In PSetup, there must always be at least one file specification, ie. *.*). Example : VirusScan *.EXE *.COM *.OVR *.OVL Virus scanners Keyword : Scanner [name] [command] [lll] <[hhh] <[nnn] <filespecs>>> Usage : This is one of the most important options in PalmScan. The files inside archives will be scanned with all configured virus scanners. [name] This is the name of the virus scanner. [command] This is the command for the virus scanner to be executed. The path/filename(s) of the file(s) to be scanned will NOT be automatically added to the commandline. There are some meta-commands which will be replaced with the correct string by PalmScan: @PATH The directory that should be scanned (without trailing backslash). @FILENAME The filename of the file(s) to be scanned. @FULL The path and filename of the file(s) to be scanned. (@FULL = @PATH\@FILENAME) - 43 - PalmScan v1.13 User guide ----------------------------------------------------------------------- @SPECIAL This meta-command is a special one; it will act like @FULL when a specific file should be scanned, and like @PATH when all files in a directory should be scanned. @REPORT When a virus has been found, PalmScan will include the report created by the virus scanner(s) which found one or more virus(es) in the message which is posted to the system operator. To use this feature, @REPORT must be included on the virus scanner commandline, along with the appropriate command for that program to create the report. PalmScan will replace @REPORT with a filename for the report. [lll] This is the lowest errorlevel the virus scanner will return when a virus has been found. <hhh> This is the highest errorlevel the virus scanner will return when a virus has been found. When it is not set, PalmScan assumes the virus scanner will only return errorlevel [lll] <nnn> This is the errorlevel that the virus scanner will return when nothing is wrong. Most virus scanners return errorlevel 0 when there are no problems, but there are some scanner which return another errorlevel just because there are no executables found. With this option you can make PalmScan simply ignore that errorlevel. <filespecs> Up to 5 file specifications can optionally be given. First, PalmScan will check the global file specifications (on the VirusScan keyword). When there are files which comply with those, the virus scanning will start. Before executing each virus scanner, PalmScan will check the file specifications for those virus scanners, and only execute them when there are no file specifications configured at that virus scanner or when there are files which comply with those specifications. - 44 - PalmScan v1.13 User guide ----------------------------------------------------------------------- Examples : Scanner McAfee_Scan SCAN_/NOMEM_/A_/NOPAUSE_/SUB_/REPORT_@REPORT_@FULL 1 1 0 *.exe *.com *.ov? Scanner ThunderByte_Scan TBSCAN_AF_NB_NM_BA_IN_NA_OLD_LOG_LOGNAME=@REPORT_@SPECIAL 2 127 1 Scanner F-Prot F-PROT_/ALL_/COMMAND_/NOMEM_/OLD_/NOBOOT_/REPORT=@REPORT_ @FULL 3 3 0 Scanner AVScan AVSCAN_/NM_/NC_/Q_/R_/S_@FULL 100 255 0 *.exe *.com Scanner McAfee_Scan_2.0.x SCAN_/NOMEM_/SUB_@FULL 13 13 14 Note : You can use up to 20 virus scanners in PalmScan. They will be executed in the order they were found in the configuration. Complete scan Keyword : CompleteScan Usage : Normally, PalmScan will not process embedded archives when a virus has already been found. This feature enables the processing of those embedded archives, which is especially useful when using the message system. PalmScan will then create a complete overview of the infected files. Example : CompleteScan - 45 - PalmScan v1.13 User guide ----------------------------------------------------------------------- 3.2.12 HackList Keyword : HackList [d:\path\filename.ext] <triggers> Usage : PalmScan can check a HackList (eg. 'The Hack Report' by Bill Lambdin) for dangerous files. [d:\path\filename.ext] This is the full path and filename of the .COL or .IDX file to use. If you want to use more than one of those (eg. reports of previous years and this year), you should copy those files to one file. Wildcards are not allowed for this option. <triggers> These are the sections (eg. HAK HOX TRO) which should trigger PalmScan to move the file to the hacked files directory or, when no hacked files directory is configured, exit with errorlevel 212. Up to 10 sections can be given. When no section is specified, or when you are using a .COL list (sections are not included in .COL lists), PalmScan will always be triggered. Example : HackList C:\PALMSCAN\HACK9401.IDX HAK HOX TRO PIR Note : The used format for the HackList is: FILENAME,year,section 3.2.13 Skip files Keyword : SkipFile [filespec] <filespecs> Usage : There are some files that should not be processed by PalmScan, for instance FILES.BBS or BIMODEM.LOG. With this parameter you can specify up to 50 valid DOS file specifications that should be skipped by PalmScan. Full path names can also be included in these file specifications. [filespec] This must be a valid DOS file specification. Example : SkipFile FILES.BBS BIMODEM.* SkipFile D:\FILES\SECURE\*.* - 46 - PalmScan v1.13 User guide ----------------------------------------------------------------------- 3.2.14 Pack unpacked Keyword : PackUnpacked [filespec] <filespecs> Usage : With this option, you can tell PalmScan to archive un-archived files. All files which comply to one or more of the given file-specifications and are not archives, will be archived with the archiver configured with the ArchiveConversion keyword. [filespec] This must be a valid DOS file-specification. Example : PackUnpacked *.MOD *.STM *.ANS Note : Up to 50 file-specifications can be given. Minimum size Keyword : PackUnpackedSize [size] Usage : The minimum size for unpacked files which should be packed can be configured with this option. [size] This is the minimum size in bytes. Example : PackUnpackedSize 2048 3.2.15 Remove files Keyword : RemoveFile [filespec] <filespecs> Usage : Many archives contain some files which have no relation with the actual archive, like advertisements added by BBS SysOp's. This can eventually take up a great part of your available disk space. PalmScan can now remove these files from the archives. [filespec] This must be a valid DOS file-specification. Example : RemoveFile OASISBBS.ADV OASIS.BBS Note : Up to 50 file-specifications can be given. - 47 - PalmScan v1.13 User guide ----------------------------------------------------------------------- 3.2.16 Add files Keyword : AddFile [filespec] Usage : Just like PalmScan can remove files from archives, it can also add files to them. You can use this to add an advertisement for your BBS, or whatever you want added to the archives. [filespec] This must be a valid DOS file-specification. Example : AddFile C:\TEXT\OASIS.BBS Note : Up to 10 AddFile keywords can be used. 3.2.17 GIF settings Add GIF specifications to descriptions Keyword : GIFspecs <[left bracket] ['by' character] [right bracket]> Usage : PalmScan will add GIF specifications (resolution and colors) to descriptions when this keyword is used. Optional are the characters that are used in the descriptions, but when specifying one of them, both others must be specified too. By default, these characters are used : ( x ) When used with FILES.BBS or the RemoteAccess file- database, PalmScan will first check if the specifications already exist in the description, and only add them when they do not already exist. Example : GIFspecs < * > - 48 - PalmScan v1.13 User guide ----------------------------------------------------------------------- GIF pack Keyword : GIFpack [title] [command] Usage : To convert GIF pictures to another format, this feature can be used. [title] This is only used to display to what format the file is being converted, but must be configured when using this feature. [command] This is the command that should be executed to convert the GIF picture. PalmScan will by default add the original filename and extension to the GIFpack commandline. This is configurable with these options: @FILENAME Will be replaced by the original filename. @EXT Will be replaced by the original extension. When the 'packed' file is larger than the original file, PalmScan will use the original file. Also, programs which replace the original file (eg. GIFlite) can be used with this feature. Example : GIFpack JFIF CJPEG.EXE @FILENAME.@EXT @FILENAME.JPG JFIF unpack Keyword : JFIFunpack [command] Usage : PalmScan will use this setting to convert JFIF files to GIF. JFIF files are standard JFIF/JPEG files, which can be created by CJPEG and some other graphics conversion utilities. [command] This is the command that should be executed to convert the JFIF file. Example : JFIFunpack DJPEG.EXE - 49 - PalmScan v1.13 User guide ----------------------------------------------------------------------- JPEG unpack Keyword : JPEGunpack [command] Usage : This is actually the same as JFIF unpack, with the difference that JPEG files are files which are incompatible with standard JFIF/JPEG files. Files created by (older versions of) GIF2JPG are such JPEG files. When this command is not configured, and JFIF unpack is configured, PalmScan will try to convert JPEG files to GIF using the command configured at JFIF unpack. [command] This is the command that should be executed to convert the JPEG file. Example : JPEGunpack JPG2GIF.EXE GIFblast unpack Keyword : GIFBLASTunpack [command] Usage : PalmScan will use this setting to convert GIFblast files to GIF. [command] This is the command that should be executed to convert the GIFblast file. Example : GIFBLASTunpack GFIBLAST.EXE_-D Repack JFIF files Keyword : JFIFrepack Usage : When this keyword is used, JFIF files will first be converted to GIF, and then converted using the command configured with the GIFpack keyword. Example : JFIFrepack Repack JPEG files Keyword : JPEGrepack Usage : When this keyword is used, JPEG files will first be converted to GIF, and then converted using the command configured with the GIFpack keyword. Example : JPEGrepack - 50 - PalmScan v1.13 User guide ----------------------------------------------------------------------- Repack GIFblast files Keyword : GIFBLASTrepack Usage : When this keyword is used, GIFblast files will first be converted to GIF, and then converted using the command configured with the GIFpack keyword. Minimum resolution Keyword : MinimumResolution [horizontal]x[vertical]x[colors] Usage : PalmScan can reject GIF, JFIF, JPEG and GIFblast files which have a resolution which is too low. When either one of the resolution values is lower than the configured value, PalmScan will move the file to the directory configured with the BadGifPath configuration keyword. When no BadGifPath is configured, PalmScan will exit with errorlevel 205. When a message area is configured, a message to the system operator will also be posted. [horizontal] The minimum horizontal resolution (width). [vertical] The minimum vertical resolution (height). [colors] The minumum number of colors. Example : MinimumResolution 320x200x256 GIF test command / failures Keyword : GIFtest [command] <errorlevels> Usage : PalmScan can use an external GIF testing program to test all GIF files. [command] The command to execute to test GIF files. <errorlevels> Up to 10 errorlevels can be configured. When the result from [command] is one of the configured errorlevels, PalmScan will move the file to the BadGifPath, or exit with errorlevel 205 when no BadGifPath is configured. When a message area is configured, a message to the system operator will also be posted. Example : GIFtest GIFTEST.EXE_/M:320x200x256 1 20 25 - 51 - PalmScan v1.13 User guide ----------------------------------------------------------------------- 3.2.18 Old files Keyword : OldFiles [[-days]|[dd-mm-yyyy]] <Original|Latest|Oldest> Usage : PalmScan can check for files which are too old. Either the maximum age in days or a date can be used for this check. PalmScan will check for old files right after embedded archives have been processed. When an old file has been encountered, it will be moved to the directory configured with the OldPath configuration keyword. When no OldPath is configured, PalmScan will exit with errorlevel 204. When a message area is configured, a message to the system operator will also be posted. [-days] The maximum age of a file, in days. [dd-mm-yyy] The oldest allowed date of a file, in date-month-year format. <Original> PalmScan will use the original archive's date. <Latest> Use the latest date of the files inside the archive. <Oldest> Use the oldest date of the files inside the archive. Example : OldFiles -90 Latest 3.2.19 Information This is a small information window about PalmScan and PSetup. 3.2.20 Exit to dos This option will take you out of PSetup. If you have made any changes to the configuration, you will be asked if you want to save them before you exit. You also have the option to cancel and return back to PSetup. - 52 - PalmScan v1.13 User guide ----------------------------------------------------------------------- 4 Registration After you have evaluated PalmScan for the period of one month, you must either register or discontinue using PalmScan. PalmScan is released as 'try before you buy', so please buy it if you like it. As long as you don't register, PalmScan will remind you that you have not registered when PalmScan is started up. To register, fill out the registration form and send it to the registration site. For information about prices and registration sites, see the registration forms included in this package. - 53 - PalmScan v1.13 User guide ----------------------------------------------------------------------- 5 Credits Thanks to all registered users and beta testers, for registering and testing this software, and for all suggestions I got from you. All brand and product names are copyrighted (C) by and/or trademarks (TM) or registered trademarks (R) of their respective holders: 4DOS JP Software Inc. Allfix Harald Harms ARJ Robert K. Jung AVScan H+BEDV Datentechnik GmbH CJPEG, DJPEG Thomas G. Lane Ezycom Peter Davies F-Prot Frisk Software International Fido Tom Jennings and Fido Software FileDoor Robert W. van Hoeven GIF CompuServe Incorporated GIF2JPG, JPG2GIF Handmade Software, Inc. GIFblast Isaac Dimitrovsky GIFtest Max Bernard and Dave Navarro, Jr. HAP, PAH Harald Feldmann Hudson messagebase Adam Hudson Hyper P. Sawatzki and K.P. Nischke IBM, PC-DOS International Business Machines Corp. LHA Haruyasu Yoskizaki Microsoft, MS-DOS Microsoft Corporation PAK NoGate Consulting PKARC, PKZIP PKWARE, Inc. QuickBBS Pegasus Software RAFT Chris Buijs RAR Eugene Roshal RemoteAccess, JAM Wantree Development and Andrew Milner SQZ J.I. Hammarsberg SuperBBS Aki Antman and Risto Virkkala TBScan Thunderbyte BV UltraCompressor II, UC2 Ad Infinitum Programs ViruScan McAfee Associates ZOO Rahul Dhesi - 54 - PalmScan v1.13 User guide ----------------------------------------------------------------------- I Index /All . . . . . . . . . . . . 15 JPEGunpack . . . . . . . . . 50 /C[configuration-filename] . 16 LogFile . . . . . . . . . . . 39 /Debug . . . . . . . . . . . 18 MessageArea . . . . . . . . . 38 /D[dorinfo-filename] . . . . 16 MinimumResolution . . . . . . 51 /FDBmaint<areanr<-areanr>> . 15 NetAddress . . . . . . . . . 23 /Fix<+> . . . . . . . . . . . 16 NoTitleInHdr . . . . . . . . 34 /L . . . . . . . . . . . . . 16 OldFiles . . . . . . . . . . 52 /Mono . . . . . . . . . . . . 18 OldPath . . . . . . . . . . . 37 /Move[Path] . . . . . . . . . 18 OnlyNewFiles . . . . . . . . 30 /NoCls . . . . . . . . . . . 18 PackUnpacked . . . . . . . . 47 /NoConversion . . . . . . . . 17 PackUnpackedSize . . . . . . 47 /NoFDB . . . . . . . . . . . 17 ProcessListedOnly . . . . . . 31 /NoFilesbbs . . . . . . . . . 17 ProcessSFX . . . . . . . . . 33 /NoMove . . . . . . . . . . . 18 RARlock . . . . . . . . . . . 42 /NoReg . . . . . . . . . . . 18 RedirectOutput . . . . . . . 24 /N[node] . . . . . . . . . . 16 RegKey . . . . . . . . . . . 22 /S . . . . . . . . . . . . . 17 RemoveFile . . . . . . . . . 47 /T[archiver] . . . . . . . . 17 Scanner . . . . . . . . . . . 43 /Unlisted . . . . . . . . . . 18 SkipFile . . . . . . . . . . 46 AddCRCfile . . . . . . . . . 34 SubstDrive . . . . . . . . . 40 AddFile . . . . . . . . . . . 48 SysopName . . . . . . . . . . 22 ArchInArch . . . . . . . . . 33 TempPath . . . . . . . . . . 36 ArchiveConversion . . . . . . 31 Touch . . . . . . . . . . . . 35 ArchiveHeader . . . . . . . . 40 UC2protection . . . . . . . . 42 Archiver . . . . . . . . . . 41 UploaderName . . . . . . . . 23 BadGifPath . . . . . . . . . 37 VirusScan . . . . . . . . . . 43 BadPath . . . . . . . . . . . 36 BBSname . . . . . . . . . . . 22 BBSpath . . . . . . . . . . . 38 ColorBackground . . . . . . . 24 ColorHighlight . . . . . . . 24 ColorNormal . . . . . . . . . 24 CompleteScan . . . . . . . . 45 ConvertAll . . . . . . . . . 33 DescribeMod . . . . . . . . . 29 DownloadCounter . . . . . . . 26 EzyFileID . . . . . . . . . . 29 FDB . . . . . . . . . . . . . 27 FileDoor . . . . . . . . . . 25 FileID . . . . . . . . . . . 28 FileIDarchiveHdr . . . . . . 31 FilesBBS . . . . . . . . . . 25 FilesBBSname . . . . . . . . 39 GIFBLASTrepack . . . . . . . 51 GIFBLASTunpack . . . . . . . 50 GIFpack . . . . . . . . . . . 49 GIFspecs . . . . . . . . . . 48 GIFtest . . . . . . . . . . . 51 HackList . . . . . . . . . . 46 HackPath . . . . . . . . . . 37 IndentSpaces . . . . . . . . 25 InfectedPath . . . . . . . . 36 JFIFrepack . . . . . . . . . 50 JFIFunpack . . . . . . . . . 49 JPEGrepack . . . . . . . . . 50 - 55 -