PalmScan v2.02
The Ultimate Archive Conversion Utility
User guide
PalmScan v2.02
The Ultimate Archive Conversion Utility
April 30, 1996
Software and documentation written by Steven Hendriks
Copyright (C) 1993,96 by Steven Hendriks
All rights reserved.
All information in this documentation is
subject to change without prior notice
PalmScan v2.02 User guide
---------------------------------------------------------------------
Table of Contents
-----------------
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.1 Copyright and License Agreement . . . . . . . . . . . . . . 6
1.2 Contacting the author . . . . . . . . . . . . . . . . . . . 7
1.3 What is PalmScan . . . . . . . . . . . . . . . . . . . . . 7
1.4 Features . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.5 System requirements . . . . . . . . . . . . . . . . . . . 10
1.6 Logging . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.7 The distribution package . . . . . . . . . . . . . . . . 11
1.8 Runtime . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.9 Extended Wildcards . . . . . . . . . . . . . . . . . . . 12
2 Installation . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.1 First time installation . . . . . . . . . . . . . . . . . 13
2.2.1 Installing PalmScan in FileDoor . . . . . . . . . 13
2.2.2 Installing PalmScan in SuperBBS . . . . . . . . . 13
2.2.3 Installing PalmScan in Allfix . . . . . . . . . . 14
2.2.4 Installing PalmScan in RemoteAccess 2.xx . . . . . 14
2.2.5 Installing PalmScan in RAFT . . . . . . . . . . . 14
2.2.6 Installing PalmScan in Maximus . . . . . . . . . . 15
2.2.7 Installing PalmScan in Ezycom . . . . . . . . . . 16
2.2.8 Installing PalmScan in Concord . . . . . . . . . . 17
2.2.9 Installing PalmScan in ProBoard . . . . . . . . . 17
2.3 Commandline . . . . . . . . . . . . . . . . . . . . . . . 18
2.4 Watchdog, CTTY, ANSI.SYS . . . . . . . . . . . . . . . . 24
2.5 Errorlevels . . . . . . . . . . . . . . . . . . . . . . . 24
3 The configuration . . . . . . . . . . . . . . . . . . . . . . 25
3.1 PALMSCAN.CFG . . . . . . . . . . . . . . . . . . . . . . 25
3.2 PSetup . . . . . . . . . . . . . . . . . . . . . . . . . 26
3.2.1 Commandline . . . . . . . . . . . . . . . . . . . 26
3.2.2 Starting PSetup . . . . . . . . . . . . . . . . . 26
3.2.3 Keys . . . . . . . . . . . . . . . . . . . . . . . 26
3.3 System data . . . . . . . . . . . . . . . . . . . . . . . 27
3.3.1 Site Information . . . . . . . . . . . . . . . . . 27
BBS name . . . . . . . . . . . . . . . . . . . . . 27
SysOp name . . . . . . . . . . . . . . . . . . . . 27
Key number . . . . . . . . . . . . . . . . . . . . 27
3.3.2 Screen settings . . . . . . . . . . . . . . . . . 28
Redirect screen output of external programs . . . 28
Normal color . . . . . . . . . . . . . . . . . . . 28
Highlighted color . . . . . . . . . . . . . . . . 28
Background color . . . . . . . . . . . . . . . . . 29
Edit color . . . . . . . . . . . . . . . . . . . . 29
Edit background . . . . . . . . . . . . . . . . . 29
3.3.3 Pathnames . . . . . . . . . . . . . . . . . . . . 30
Temporary directory . . . . . . . . . . . . . . . 30
Bad files directory . . . . . . . . . . . . . . . 30
Infected files directory . . . . . . . . . . . . . 30
Hacked files directory . . . . . . . . . . . . . . 31
Old files directory . . . . . . . . . . . . . . . 31
Bad GIF files directory . . . . . . . . . . . . . 31
Substitute drive . . . . . . . . . . . . . . . . . 32
3.3.4 Files Lists . . . . . . . . . . . . . . . . . . . 33
Hacked files list . . . . . . . . . . . . . . . . 33
Skip files list . . . . . . . . . . . . . . . . . 33
Pack Unpacked files list . . . . . . . . . . . . . 33
Remove files list . . . . . . . . . . . . . . . . 34
PalmScan v2.02 User guide
---------------------------------------------------------------------
Add files list . . . . . . . . . . . . . . . . . . 34
Password list . . . . . . . . . . . . . . . . . . 34
3.3.5 Message System . . . . . . . . . . . . . . . . . . 35
Net address . . . . . . . . . . . . . . . . . . . 35
Messagebase path . . . . . . . . . . . . . . . . . 35
Messagebase format . . . . . . . . . . . . . . . . 36
Message area number . . . . . . . . . . . . . . . 36
MessageArea configuration keyword . . . . . . . . 37
3.3.6 File-database . . . . . . . . . . . . . . . . . . 38
File-database . . . . . . . . . . . . . . . . . . 38
Uploader name . . . . . . . . . . . . . . . . . . 39
BBS system directory . . . . . . . . . . . . . . . 39
Update FILES.BBS . . . . . . . . . . . . . . . . 40
Extended descriptions character . . . . . . . . . 40
Spaces to indent . . . . . . . . . . . . . . . . . 41
Download counters . . . . . . . . . . . . . . . . 41
FILES.BBS Filename . . . . . . . . . . . . . . . . 42
Online Import . . . . . . . . . . . . . . . . . . 42
3.3.7 Miscellaneous . . . . . . . . . . . . . . . . . . 43
Log file . . . . . . . . . . . . . . . . . . . . . 43
Log style . . . . . . . . . . . . . . . . . . . . 43
No disk space check . . . . . . . . . . . . . . . 44
Exec timeout . . . . . . . . . . . . . . . . . . . 44
3.4 File Processing . . . . . . . . . . . . . . . . . . . . . 45
3.4.1 General settings . . . . . . . . . . . . . . . . . 45
Only process new files . . . . . . . . . . . . . . 45
Only process listed files . . . . . . . . . . . . 46
Process embedded archives . . . . . . . . . . . . 46
New archive date . . . . . . . . . . . . . . . . . 47
3.4.2 Archive Conversion . . . . . . . . . . . . . . . . 48
Archive conversion . . . . . . . . . . . . . . . . 48
SFX . . . . . . . . . . . . . . . . . . . . . . . 48
Only Main Archives . . . . . . . . . . . . . . . . 48
Don't convert secure archives . . . . . . . . . . 49
Only convert embedded archives with normal extensions
. . . . . . . . . . . . . . . . . . . . . . 49
ArchiveConversion configuration keyword . . . . . 50
Convert ALL archives . . . . . . . . . . . . . . . 50
3.4.3 Self-Extracting Archives . . . . . . . . . . . . . 51
Process SFX archives . . . . . . . . . . . . . . . 51
Do not convert self-extracting archives . . . . . 51
Process UC2 self-extracting archives . . . . . . . 51
UC2 SFX commandline options . . . . . . . . . . . 52
Only process sealed UC2 self-extracting archives . 52
UC2SFX configuration keyword . . . . . . . . . . . 52
UC2 SFX seal test command . . . . . . . . . . . . 53
Scan SFX archives for viruses . . . . . . . . . . 53
3.4.4 Archive Headers . . . . . . . . . . . . . . . . . 54
Archive header file . . . . . . . . . . . . . . . 54
Alternative header file . . . . . . . . . . . . . 54
Put FILE_ID description in archive header . . . . 55
No title in headers . . . . . . . . . . . . . . . 55
3.4.5 Descriptions . . . . . . . . . . . . . . . . . . . 56
Import FILE_ID description . . . . . . . . . . . . 56
One line FILE_ID . . . . . . . . . . . . . . . . . 56
Filter high ASCII . . . . . . . . . . . . . . . . 56
Filter control codes . . . . . . . . . . . . . . . 57
Filter drawings . . . . . . . . . . . . . . . . . 57
Maximum Width . . . . . . . . . . . . . . . . . . 57
Maximum Length . . . . . . . . . . . . . . . . . . 58
PalmScan v2.02 User guide
---------------------------------------------------------------------
FileID configuration keyword . . . . . . . . . . . 58
Describe MOD's . . . . . . . . . . . . . . . . . . 59
3.5 Archivers . . . . . . . . . . . . . . . . . . . . . . . . 60
3.5.1 Archiver commands . . . . . . . . . . . . . . . . 60
Compression . . . . . . . . . . . . . . . . . . . 61
Decompression . . . . . . . . . . . . . . . . . . 61
Add Header . . . . . . . . . . . . . . . . . . . . 62
Alternative header . . . . . . . . . . . . . . . . 62
Test . . . . . . . . . . . . . . . . . . . . . . . 63
Multi-Volume Compression . . . . . . . . . . . . . 63
Multi-Volume Decompression . . . . . . . . . . . . 64
Example archiver commands . . . . . . . . . . . . 64
3.5.2 Archive Protection . . . . . . . . . . . . . . . . 66
UC2 protection . . . . . . . . . . . . . . . . . . 66
RAR lock . . . . . . . . . . . . . . . . . . . . . 66
3.6 Virus scan . . . . . . . . . . . . . . . . . . . . . . . 67
3.6.1 Files to scan . . . . . . . . . . . . . . . . . . 67
3.6.2 Virus scanners . . . . . . . . . . . . . . . . . . 67
Scanner name . . . . . . . . . . . . . . . . . . . 67
Command . . . . . . . . . . . . . . . . . . . . . 68
Low Errorlevel . . . . . . . . . . . . . . . . . . 68
High Errorlevel . . . . . . . . . . . . . . . . . 69
Other Errorlevel . . . . . . . . . . . . . . . . . 69
File specifications . . . . . . . . . . . . . . . 69
Scanner configuration keyword . . . . . . . . . . 70
3.6.3 Options . . . . . . . . . . . . . . . . . . . . . 71
Complete scan . . . . . . . . . . . . . . . . . . 71
Fast scan . . . . . . . . . . . . . . . . . . . . 71
No DOS scanners . . . . . . . . . . . . . . . . . 71
3.7 Hacked Files . . . . . . . . . . . . . . . . . . . . . . 72
3.8 Skip Files . . . . . . . . . . . . . . . . . . . . . . . 72
3.9 Pack Unpacked . . . . . . . . . . . . . . . . . . . . . . 73
File specifications . . . . . . . . . . . . . . . . . . . 73
Minimum size . . . . . . . . . . . . . . . . . . . . . . 73
3.10 Remove Files . . . . . . . . . . . . . . . . . . . . . . 74
3.11 Add Files . . . . . . . . . . . . . . . . . . . . . . . . 75
Add CRC file list . . . . . . . . . . . . . . . . . . . . 75
3.12 Archive Passwords . . . . . . . . . . . . . . . . . . . . 76
3.13 GIF settings . . . . . . . . . . . . . . . . . . . . . . 77
Add GIF specifications to descriptions . . . . . . . . . 77
GIF pack . . . . . . . . . . . . . . . . . . . . . . . . 78
Do not convert embedded graphics files. . . . . . . . . . 78
JFIF unpack . . . . . . . . . . . . . . . . . . . . . . . 79
JPEG unpack . . . . . . . . . . . . . . . . . . . . . . . 79
GIFblast unpack . . . . . . . . . . . . . . . . . . . . . 79
Repack JFIF files . . . . . . . . . . . . . . . . . . . . 80
Repack JPEG files . . . . . . . . . . . . . . . . . . . . 80
Repack GIFblast files . . . . . . . . . . . . . . . . . . 80
Minimum resolution . . . . . . . . . . . . . . . . . . . 81
GIF test command / failures . . . . . . . . . . . . . . . 81
3.14 Old files . . . . . . . . . . . . . . . . . . . . . . . . 82
3.15 Include Configurations . . . . . . . . . . . . . . . . . 83
4 Registration . . . . . . . . . . . . . . . . . . . . . . . . . 84
5 Credits . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
I Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
PalmScan v2.02 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).
- The evaluation version of 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.
- 6 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
1.2 Contacting the author
--------------------------
If you have any questions about PalmScan, problems with it, or if you
wish to contact the author for suggestions etcetera, you can:
- Call Oasis BBS (300 - 28800 bps) at +31-181-453132
- Send a NetMail message to Steven Hendriks at:
Fidonet 2:2802/140
VirNet 9:310/1
SIGnet 27:1331/401
OASE 200:3110/0
- Send E-Mail to:
0340278@ptfe22.hro.nl
- Send an echomail message in the OASISSOFT support echo.
- Send an echomail message in an appropriate area in one of the
above networks (I cannot 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
3214 AH Zuidland
the 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 RemoteAccess, Ezycom and Concord file-database support,
works with any door.sys or dorinfo supporting bbs system, works great
in Allfix and many other programs, or stand-alone!
- 7 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
1.4 Features
-------------
- A very flexible configuration. You can configure almost anything
the way you want it.
- Detects these archive types:
- ARC
- ARJ SFX AV MV PW
- HAP
- HYP
- LZH SFX
- PAK SFX
- RAR SFX AV MV PW
- SQZ SFX
- UC2 SFX AV
- ZIP SFX AV PW
- ZOO
SFX Self-extracting archives are supported.
AV Security envelopes / authenticity validations / seals are
supported.
MV Multi-volume archives are supported.
PW Password-protected archives are supported.
PalmScan can detect other archives by looking at the archive
extension. Other archivers could be added when needed. To get an
archiver added, send a request for this to the author of
PalmScan, along with the archiving program and a contact address
for technical information on the archiver format.
- Supports up to 30 different archive types.
- Supports GIF, PNG, JFIF, JPEG and GIFblast graphics images.
- Full support for these file-databases:
- RemoteAccess (both 2.0x and 2.5x)
- Ezycom (both 1.02 and 1.10)
- Concord
- Full support for online features in Concord, Ezycom and
Filedoor.
- Special FILES.BBS support.
- Full support for the RemoteAccess 2.0x, RemoteAccess 2.5x,
Ezycom 1.02, Ezycom 1.10 and Concord 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.
- 8 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
- Get file descriptions from FILE_ID.DIZ and DESC.SDI.
- Describes music files, like MOD, ScreamTracker, organ files,
etc.
- Describes Compuserve GIF pictures, portable network graphics
(PNG), JFIF and JPEG graphics.
- Tests GIF pictures.
- Ability to notify the system operator 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.
- 9 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
1.5 System requirements
------------------------
DOS version:
- IBM PC, XT, AT or compatible.
- IBM PC-DOS / 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, LZH, ZOO, SQZ, Hyper, ARJ, HAP, PAK, UC2, RAR.
- 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.
OS/2 version:
- OS/2 2.1 or higher.
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
- 10 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
1.7 The distribution package
-----------------------------
PalmScan is distributed in a self-extracting RAR archive. The
original distribution archive, and all embedded archives, contain an
authenticity validation. If you obtained a version without this
authenticity validation, please check with one of the registration
sites for the original distribution archive.
When unpacking the archive, it should show:
Verifying authenticity information ... Ok
and:
modified at (time) 30 Apr 1996
by Steven Hendriks
This package includes:
PALMSCAN.EXE The main program
PALMSCAN.OVR Overlay file for the message system (DOS version only)
PALMSCAN.DOC This documentation
PALMSCAN.HLP Commandline help
PSETUP.EXE PalmScan SETUP program
PSREG.EXE Self-extracting archive containing the registration
forms
EXAMPLE.EXE Self-extracting archive containing an example
configuration file
PALMSCAN.ANS Ansi advertisement
FILE_ID.DIZ Package description
UPDATE.LOG Update log
README.1ST Last-minute information
PUPDATE.EXE Program to update PalmScan v1.xx configuration to
v2.02.
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.
PalmScan displays a spinning cursor when it's working. In the DOS
version, this will not be shown when an external program is being
executed. In the OS/2 version, it will always be shown when the
output of external programs is redirected to NUL (RedirectOutput
configuration keyword).
- 11 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
1.9 Extended Wildcards
-----------------------
PalmScan has support for extended wildcards. This means that any
number of '?' and '*' characters can be used in file-specifications
which support wildcards. For example, 'P*SCAN*' would match
'PALMSCAN.EXE'.
- 12 -
PalmScan v2.02 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.1 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 'Online 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.2.2 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 has got another filename.
For using archive conversion, you should run PalmScan in an event,
with 'FilesBBS' and 'OnlyNewFiles' switched on.
- 13 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
2.2.3 Installing PalmScan in Allfix
------------------------------------
Allfix version 4.21 (and later) and Allfix/2 version 1.00 (and later)
have 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.2.4 Installing PalmScan in RemoteAccess 2.xx
-----------------------------------------------
The commandline for using PalmScan in the upload scan option in
RemoteAccess 2.xx should be:
PALMSCAN.EXE @ *M
If you are using the file-database in RemoteAccess 2.xx, you should
also enable this option ('FDB RA') in the PalmScan configuration.
2.2.5 Installing PalmScan in RAFT (The Remote Access Filearea Tools)
---------------------------------------------------------------------
The commandline for using PalmScan in the ARCCONV option in The
Remote Access Filearea Tools is:
PALMSCAN.EXE %F @1 /L
- 14 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
2.2.6 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.
- 15 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
2.2.7 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
'Online Ezycom' can be used to make PalmScan pass on the file
description to Ezycom.
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>).
- 16 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
2.2.8 Installing PalmScan in Concord
-------------------------------------
The best way to use PalmScan with Concord is to use the file-database
maintenance feature (/FDBmaint commandline option). PalmScan will
then process all files which have not been processed yet, and update
the Concord file-database. This can also be done while the user is
still on-line, by creating a simple menu which first executes the
upload feature of Concord, and then runs the PalmScan file-database
maintenance for the specific upload area.
To install PalmScan in the upload checker feature, this has to be
configured in the Concord configuration:
- At the file-system section, the extended upload checker should
be turned ON.
- At the paths section, PalmScan should be configuration as virus
scanner. At the time this documentation is being written, it is
not yet known how Concord calls the upload checker, please
consult the Concord manual for that.
PalmScan should not update the Concord file-database when running as
upload checker, so FDB Concord should not be used, or /NoFDB should
be added to the PalmScan commandline. You should use 'Online Concord'
if you want PalmScan to pass on the file description to Concord.
2.2.9 Installing PalmScan in ProBoard
--------------------------------------
By using PalmUpload, a ProBoard extension (PEX) file, it is very easy
to use PalmScan as upload checker under ProBoard.
PalmUpload must be installed as a menu function 60 (Run ProBoard SDK
file), which should replace the regular upload feature.
Menu Data : PUPLOAD [PalmScan path]
You must specify the directory where PalmScan.EXE can be found at the
data field. Example : PUPLOAD C:\PALMSCAN
That's really all there is to it... PalmUpload will first perform the
upload as regular (it will use the default upload directory as
configured in the ProBoard configuration). After that, PalmScan will
be started, which can then do anything you want with the uploaded
files. After PalmScan has finished processing all uploaded files,
PalmUpload will check if the files have passed. If they haven't
(because of a bad archive, infected files found, etc.), the file will
be subtracted from the user's number of uploaded files and kilobytes.
- 17 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
2.3 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
- 18 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
[Command] :
/FDBmaint<areanr<-areanr>>
Usage : Run Ezycom/RemoteAccess/Concord 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 file-area
configuration. When no archiver is configured for an
area, PalmScan will not process files in that area.
(Except for Concord, at this moment no archiver can be
configured in the file-area configuration so all areas
will be processed).
When running with Ezycom or Concord, 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.
When running with Concord, PalmScan will only do
virus-scanning when that's configured in the file-area
configuration.
<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.
Options : /All Process all files in the specified areas,
even if they have already been processed.
/AnyArea Process any area, instead of only areas
which have a target archiver set.
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 file-area configuration.
- 19 -
PalmScan v2.02 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.
- 20 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
/NoChanges
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.
/NoConversion
Usage : When this option is used, archive conversion is not
done. All other function will be performed.
/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 is a bonus feature, which is available in the
registered version only.
/NoFDB
Usage : Temporary disable the file-database support.
Note : This is a bonus feature, which is available in the
registered version only.
/NoFilesbbs
Usage : Temporary disable the files.bbs support.
Note : This is a bonus feature, which is available in the
registered version only.
- 21 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
/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.
/Unlisted
Usage : When this option is used, PalmScan will only process
files which are not listed in FILES.BBS and/or the
RemoteAccess/Ezycom/Concord 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.
Note : This is a bonus feature, which is available in the
registered version only.
/V[Size]
Usage : To use the multi-volume packing (MultiVolumePack
configuration keyword), the target size must be
specified on the PalmScan commandline, using this
commandline option.
[Size] The target size of the multi-volume
archives. This parameter is passed on
directly to the archiver when PalmScan
starts packing the archives.
/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.
Note : This is a bonus feature, which is available in the
registered version only.
/NoScan
Usage : Temporary disable virus-scanning.
Note : This is a bonus feature, which is available in the
registered version only.
- 22 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
/Mono
Usage : Forces monochrome mode.
/NoCls
Usage : Do not clear the screen at startup.
/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.
/P[priority]
Usage : This option is only available in the OS/2 version of
PalmScan. The priority of the process can be set using
this commandline option.
[priority] This is a percentage of the normal
priority. It can be a value from 0 to
257. The default priority is 100.
/Interactive
Usage : When this option is used, PalmScan can ask some
questions when needed. When running in on-line mode,
the user who is on-line can also type an answer.
PalmScan will time-out when no input is given within a
minute.
Interactive mode is currently only used for obtaining
passwords for password protected archives.
- 23 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
2.4 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.5 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, 204, 205, 212 and 213 will only be returned when
no directory is configured to move those files to.
- 24 -
PalmScan v2.02 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 virus scanner
commands), you can use underscores ('_') for that, PalmScan will
translate those to 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.
PalmScan will also ignore all lines starting with 'PT'. This makes it
possible to use one configuration file for both PalmScan and PalmTick
FeatherLight.
- 25 -
PalmScan v2.02 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.
- 26 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
3.3 System data
----------------
3.3.1 Site Information
-----------------------
BBS name
--------
This option informs PalmScan of your BBS name. This option is only of
use when you registered PalmScan and also filled in the key number.
Example : Oasis BBS
Keyword : BBSname [BBS_name]
[BBS_name] This is your BBS name.
Example : BBSname Oasis_BBS
SysOp name
----------
This option informs PalmScan of the name of the system operator. When
writing a message, PalmScan will write it to this name. When no name
is configured, the message will be addressed to 'SysOp'.
Example : Steven Hendriks
Keyword : SysopName [Sysop_Name]
[Sysop_Name] The name of the system operator.
Example : SysopName Steven_Hendriks
Key number
----------
When you registered PalmScan, you received a key for use with
PalmScan. This key must be entered here, to make PalmScan work in
registered mode. You must also use the registered version for this to
work. If you don't have the registered version, please contact your
local registration site or the main registration site for more
information. If you have not already registered PalmScan, please see
the registration form for details on how to register.
Example : 12345678901234567890123456789012
Keywords : RegKey [Key number]
OS2key [Key number]
[Key number] This is your key number as you receive it
after registering PalmScan.
Examples : RegKey 12345678901234567890123456789012
OS2key 12345678901234567890123456789012
- 27 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
3.3.2 Screen settings
----------------------
Redirect screen output of external programs
-------------------------------------------
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 screen to be exactly the same as the display
on the user screen (when running in on-line mode).
Example : X
Keyword : RedirectOutput
Example : RedirectOutput
Normal color
------------
With this option, you can configure the color of normal text in
PalmScan.
Example : 3
Keyword : ColorNormal [c]
[c] This is the color number. This can be any value
from 0 to 15.
Example : ColorNormal 3
Highlighted color
-----------------
With this option, you can configure the color of highlighted text in
PalmScan.
Example : 11
Keyword : ColorHighlight [c]
[c] This is the color number. This can be any value
from 0 to 15.
Example : ColorHighlight 11
- 28 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
Background color
----------------
With this option, you can configure the background color in PalmScan.
Example : 0
Keyword : ColorBackground [c]
[c] This is the color number. This can be any value
from 0 to 7.
Example : ColorBackground 0
Edit color
----------
With this option, you can configure the color of edit fields which
are used in interactive mode.
Example : 15
Keyword : ColorEdit [c]
[c] This is the color number. This can be any value
from 0 to 15.
Example : ColorEdit 15
Edit background
---------------
With this option, you can configure the background color of edit
fields which are used in interactive mode.
Example : 1
Keyword : ColorEditBackground [c]
[c] This is the color number. This can be any value
from 0 to 7.
Example : ColorEditBackground 1
- 29 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
3.3.3 Pathnames
----------------
Temporary directory
-------------------
This should point to a directory where PalmScan can store temporary
files. This directory is necessary for running PalmScan.
When no temporary directory is configured, PalmScan will use the TEMP
environment variable (when available). For more information about
environment variables, consult your DOS or OS/2 documentation.
Example : C:\TEMP
Keyword : TempPath [d:\path]
[d:\path] This is the directory where the temporary files
will be stored.
Example : TempPath C:\TEMP
Bad files directory
-------------------
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.
Example : C:\FILES\BAD
Keyword : BadPath [d:\path]
[d:\path] This is the directory where PalmScan will move
bad files to.
Example : BadPath C:\FILES\BAD
Infected files directory
------------------------
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.
Example : C:\FILES\INFECTED
Keyword : InfectedPath [d:\path]
[d:\path] This is the directory where PalmScan will move
infected files to.
Example : InfectedPath C:\FILES\INFECTED
- 30 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
Hacked files directory
----------------------
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 : C:\FILES\HACKED
Keyword : HackPath [d:\path]
Example : HackPath C:\FILES\HACKED
Old files directory
-------------------
PalmScan can check for files which are too old. When this check is
configured (see the Old files section), old files will be moved to
the path configured with this option. When no directory is configured
here, PalmScan will exit with errorlevel 204 when encountering files
which are too old.
Example : C:\FILES\OLD
Keyword : OldPath [d:\path]
Example : OldPath C:\FILES\OLD
Bad GIF files directory
-----------------------
When a bad graphics image (a graphics image 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 directory configured here. When no directory is configured
here, PalmScan will exit with errorlevel 205 on bad graphics images.
Keyword : BadGifPath [d:\path]
Example : BadGifPath C:\FILES\BADGIF
- 31 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
Substitute drive
----------------
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.
With the default archiver settings, this option is not necessary.
Note : This option is not available in the OS/2 version of
PalmScan, while the SUBST command is not available in
OS/2.
Example : F
Keyword : SubstDrive [Drive letter]
[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
- 32 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
3.3.4 Files Lists
------------------
Here a number of files-lists can be configured. When the files-list
have been configured here, they can be edited using PSetup.
Hacked files list
-----------------
PalmScan can check a HackList (eg. 'The Hack Report') for dangerous
or unwanted files. This HackList contains filenames or file-
specifications which PalmScan will reject. When a filename without an
extension is configured, PalmScan will assume '.*' (without quotes).
The hacklist can contain other information after a comma, which will
be ignored by PalmScan.
Example : C:\PALMSCAN\PALMSCAN.HCK
Keyword : HackList [d:\path\filename.ext]
[d:\path\filename.ext] This is the full path and filename of
the HackList to use.
Example : HackList C:\PALMSCAN\PALMSCAN.HCK
Skip files list
---------------
The skip files list can be used to make PalmScan skip certain files.
Both normal file-specifications and directories with file-
specifications can be used in the skip files list.
Example : C:\PALMSCAN\PALMSCAN.SKP
Keyword : SkipFilesList [d:\path\filename.ext]
[d:\path\filename.ext] This is the full path and filename of
the skip files list to use.
Example : SkipFilesList C:\PALMSCAN\PALMSCAN.SKP
Pack Unpacked files list
------------------------
PalmScan will pack all files which are not yet archived, which are
specified in this list.
Example : C:\PALMSCAN\PALMSCAN.PCK
Keyword : PackUnpackedFilesList [d:\path\filename.ext]
[d:\path\filename.ext] This is the full path and filename of
the pack unpacked files list to use.
Example : PackUnpackedFilesList C:\PALMSCAN\PALMSCAN.PCK
- 33 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
Remove files list
-----------------
With this list, you can tell PalmScan to remove certain files from
archives. For example, this can be used to remove other bbs's
advertisements.
Example : C:\PALMSCAN\PALMSCAN.RMV
Keyword : RemoveFilesList [d:\path\filename.ext]
[d:\path\filename.ext] This is the full path and filename of
the remove files list to use.
Example : RemoveFilesList C:\PALMSCAN\PALMSCAN.RMV
Add files list
--------------
In this list, files which must be added to archives can be
configured. File-specifications are not allowed in this list, only
path\filenames.
Example : C:\PALMSCAN\PALMSCAN.ADD
Keyword : AddFilesList [d:\path\filename.ext]
[d:\path\filename.ext] This is the full path and filename of
the add files list to use.
Example : AddFilesList C:\PALMSCAN\PALMSCAN.ADD
Password list
-------------
This files-list can contain paths and file-specifications for
archives, and passwords which should be used to unpack those
archives.
Example : C:\PALMSCAN\PALMSCAN.PWL
Keyword : PasswordList [d:\path\filename.ext]
[d:\path\filename.ext] This is the full path and filename of
the password list to use.
Example : PasswordList C:\PALMSCAN\PALMSCAN.PWL
- 34 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
3.3.5 Message System
---------------------
In this section, the PalmScan message system can be configured.
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 and have a shortage of disk space, the overlay file
can be removed. The OS/2 version of PalmScan does not use an overlay.
Memory limits aren't an issue in that version.
At the moment of the v2.02 release, the OS/2 version of PalmScan does
not support Ezycom messagebases. We are currently working on adding
this before the release of v2.03.
Net address
-----------
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.
Example : 2:2802/140
Keyword : NetAddress [Zone:Net/Node<.Point>]
[Zone:Net/Node<.Point>] Your network address.
<.Point> is optional.
Example : NetAddress 2:2802/140
Messagebase path
----------------
When an infected file or a bad archive has been found, PalmScan can
post a message to the system operator, 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.
By specifying a message area, this feature is enabled. When no
message area is configured here, the message system is disabled.
Example : C:\BBS\MSGBASE
Keyword : MessageArea [Type]<Number>[Path]
For more information about the MessageArea keyword, please read
the section about that keyword.
- 35 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
Messagebase format
------------------
When using the message system, PalmScan has to know what kind of
messagebase you want it to use. Here you can select the messagebase
format.
Example : Hudson
Keyword : MessageArea [Type]<Number>[Path]
For more information about the MessageArea keyword, please read
the section about that keyword.
Message area number
-------------------
When using a Hudson or Ezycom messagebase, a message area number must
be configured also. For Fido, Squish and JAM areas, this isn't
needed.
Example : 1
Keyword : MessageArea [Type]<Number>[Path]
For more information about the MessageArea keyword, please read
the section about that keyword.
- 36 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
MessageArea configuration keyword
---------------------------------
The MessageArea configuration keyword combines the previous three
configuration fields.
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
- 37 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
3.3.6 File-database
--------------------
File-database
-------------
PalmScan has full support for the RemoteAccess, Ezycom and Concord
file-databases. With this option, the file-database feature can be
enabled.
Example : RemoteAccess
Keyword : FDB [RA|Ezycom|Concord]
[RA] PalmScan will use the RemoteAccess 2.xx 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 that it will mark the file
as deleted, unlisted and/or not available, according
to the settings in the RemoteAccess configuration.
When an archive cannot 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 a bad archive (infected, cannot be unpacked,
etc.) is 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.
[Concord] PalmScan will use the Concord file-database.
When a bad archive (infected, cannot be unpacked,
etc.) is found, PalmScan will use the normal procedure
to either move the file or exit with an errorlevel,
and besides that it will mark the file as deleted,
unlisted and offline.
Example : FDB RA
- 38 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
To prevent problems, here is some inside information about the file-
database feature:
* When you are using one directory for different file areas,
PalmScan will always use the FIRST area which uses that
directory.
* When PalmScan adds a description to the file-database, the old
description will not be removed from the database text. It will
not be used for the file anymore, but will remain on your disk.
To remove the old description you should use the maintenance
utility included in your bbs package (for more information,
consult your bbs manual).
* When PalmScan adds an unlisted file to the RemoteAccess file-
database, it will add the default settings found in the file-
area configuration.
Uploader name
-------------
By default, PalmScan uses 'PalmScan' and the version number as
uploader name for files added to the RemoteAccess/Ezycom/Concord
file-database. With this option, you can specify an other name to use
as uploader name.
Example : Steven Hendriks
Keyword : UploaderName [Name]
[Name] The name to be used as uploader name.
Example : UploaderName Steven Hendriks
Note : This is a bonus feature, which is available in the
registered version only.
BBS system directory
--------------------
When using the RemoteAccess/Ezycom/Concord file-database, PalmScan
has to read some information from the RemoteAccess/Ezycom/Concord
configuration. Either the RA/EZY/CONCORD environment variable or this
keyword must be configured to be able to use the file-database.
Example : C:\BBS
Keyword : BBSpath [d:\path]
[d:\path] The bbs system directory.
Example : BBSpath C:\BBS
- 39 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
Update FILES.BBS
----------------
When this option is set, PalmScan will update the entry in the
FILES.BBS files list when archive conversion is done, and, in
cooperation with the FileID importing function, put the description
of the file in this files list.
Example : X
Keyword : FilesBBS [c]
[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 1.xx uses '+'. By default, no
extended descriptions character is used.
Example : FilesBBS >
Extended descriptions character
-------------------------------
When using a FILES.BBS files list, and descriptions which cover more
than one line are used, an extended descriptions character can be
used. This character is placed before each additional description
line.
Example : +
Keyword : FilesBBS [c]
[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 1.xx 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.
- 40 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
Spaces to indent
----------------
With this option, you can set the number of spaces that should be
indented in the FILES.BBS, before extended descriptions.
Example : 1
KeyWord : IndentSpaces [nn]
[nn] The number of spaces to indent.
Example : IndentSpaces 1
Download counters
-----------------
When a file which was not already listed has been added to the
FILES.BBS files list, and when an extended description has been
added, PalmScan will also update the download counter when this
option has been configured.
Example : [ ] 3
Keyword : DownloadCounter [l] [r] [nnn]
[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
- 41 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
FILES.BBS Filename
------------------
By default, PalmScan will use the file FILES.BBS in the same
directory as the processed files, when the FILES.BBS feature 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 : DESCRIPT.ION
Keyword : FilesBBSname [<path\>filename.ext]
[<path\>filename.ext] The filename of the FILES.BBS file to
use. <path\> is optional.
Example : FilesBBSname DESCRIPT.ION
Online Import
-------------
When running online under Concord, Ezycom or Filedoor, PalmScan can
place the description in a temporary file, which will then be used by
Concord, Ezycom or FileDoor.
To use this feature with Ezycom, the node on which PalmScan is
running must be specified on the commandline with the /N[node]
commandline option.
The FILE_ID import function must be used in the PalmScan
configuration for this feature to work. The OneLine, Filter, FiltLow
and FiltDraw options also work with this function.
The Ezycom or Concord file-database feature should not be used with
this, or the /NoFDB commandline option should be used, while the bbs
program will update the file-database itself.
When using the Filedoor online import feature, PalmScan will also
inform Filedoor of the changes in filesizes and filenames.
When running in local-only mode (/L commandline option), PalmScan
will never create the temporary description file.
Example : Concord
Keyword : Online [Concord|Ezycom|Filedoor]
[Concord] Use the Concord file_id.diz importing function.
[Ezycom] Use the Ezycom file_id.<node> importing function.
[Filedoor] Use the Filedoor description importing function.
Example : Online Concord
- 42 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
3.3.7 Miscellaneous
--------------------
Log file
--------
PalmScan can keep track of its activity in a logfile. When this
option is not used, no logging will be done.
Example : C:\LOG\PALMSCAN.LOG
Keyword : LogFile [d:\path\filename.ext] <Compact|Expanded>
[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.
Example : LogFile C:\LOG\PALMSCAN.LOG
Log style
---------
The log file created by PalmScan can be written in two styles:
Compact : ---------- Tue 30 Apr 96, PalmScan ...
$ 12:34:56 Local operation
Expanded : $ 30-Apr 12:34:56 PSCN PalmScan ...
$ 30-Apr 12:34:56 PSCN Local operation
Example : Expanded
Keyword : LogFile [d:\path\filename.ext] <Compact|Expanded>
<Compact> This is the default log style.
<Expanded> This is the alternative log style.
Example : LogFile C:\LOG\PSCAN%N.LOG Expanded
- 43 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
No disk space check
-------------------
Before copying and unpacking files, PalmScan will first check for the
available disk space. If it is not sufficient, the operation is
cancelled. However, on large partitions (above 2 GB), DOS could
return an incorrect value, which could result in incorrect behaviour
by PalmScan. To avoid this problem, the disk space check can be
disabled.
Disabling the disk space check will result in some speed reduction
when there is not enough space available (PalmScan will find out
while copying / unpacking a file).
Example : X
Keyword : NoDiskSpaceCheck
Example : NoDiskSpaceCheck
Exec timeout
------------
With this option a timeout value for external programs can be
configured. When an external program (like an archiver, virus
scanner, etcetera) exceeds this time, PalmScan/2 assumes it hangs,
and terminates the process in which the external program is running.
The default timeout value is 600 seconds. So when a program takes
longer than 10 minutes, PalmScan/2 will terminate it. The minimum
value is 60 seconds.
Please note that this value should not be set too low, while a
program still needs some time to do it's job.
This feature is available in the OS/2 version only, while DOS does
not support multi-threaded programs.
Example : 600
Keyword : ExecTimeOut [seconds]
[seconds] The number of seconds before PalmScan/2 should
terminate the external program.
Example : ExecTimeOut 600.
- 44 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
3.4 File Processing
--------------------
3.4.1 General settings
-----------------------
Only process new files
----------------------
For running PalmScan in a daily event, it's possible to process only
new files. PalmScan can use three methods to determine whether a file
is new:
Archive Attr 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.
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 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 : Data File
Keyword : OnlyNewFiles <FileDate|DataFile>
<FileDate> Use the File Date method.
<DataFile> Use the Data File method.
When no method is specified, PalmScan will use the archive
attribute method.
Example : OnlyNewFiles DataFile
- 45 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
Only process listed files
-------------------------
By default, all files which comply with the given file specifications
(and are not specified with in the Skip files list) 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
FILES.BBS feature is used) and/or the RemoteAccess/Ezycom/Concord
file-database (when the file-database feature is used).
Example : X
Keyword : ProcessListedOnly
Example : ProcessListedOnly
Note : This is a bonus feature, which is available in the
registered version only.
Process embedded archives
-------------------------
PalmScan has the ability to process embedded archives. With this
statement you can enable this feature. When there isn't enough memory
available to start processing an embedded archive, PalmScan will swap
itself to XMS, EMS or disk, and startup another copy of itself. The
OS/2 version will never startup another copy of itself, while there
always is enough memory available.
PalmScan will not do some things with those embedded archives, which
are done with main archives. It will not add archive headers or move
infected or bad archives. When an infected embedded archive has been
found, the main archive will be handled as being infected.
Example : X
Keyword : ArchInArch
Example : ArchInArch
Note : This is the main switch for embedded archive
processing. When this is not used, all
OnlyMainArchive switches will have no meaning.
- 46 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
New archive date
----------------
When an archive has been processed, PalmScan can touch the file date
and time on the archive. These options are available:
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.
Reset future dates : 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.
Example : Reset future dates
Keyword : Touch <Original|Today|Latest|Oldest|ResetFuture>
<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.
Example : Touch ResetFuture
Note : This is a bonus feature, which is available in the
registered version only.
- 47 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
3.4.2 Archive Conversion
-------------------------
Archive conversion
------------------
This option sets the target archive system. When no target archive
system is set, no archive conversion will be done. The archive system
configured here, must also be configured at the archivers section.
Example : RAR
Keyword : ArchiveConversion [Archiver] <OnlyMainArchive> <NoSFX>
<NoSecure> <ToSFX> <EmbeddedOnlyNormalNames>
For more information about the ArchiveConversion keyword, please
read the section about that keyword.
SFX
---
When converting archives 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.
Example : X
Keyword : ArchiveConversion [Archiver] <OnlyMainArchive> <NoSFX>
<NoSecure> <ToSFX> <EmbeddedOnlyNormalNames>
For more information about the ArchiveConversion keyword, please
read the section about that keyword.
Note : This is a bonus feature, which is available in the
registered version only.
Only Main Archives
------------------
When this switch is selected, only main archives will be converted
to the target archive type. Embedded archives will still be processed
for other options when the embedded archive processing is enabled,
but those archives will not be converted.
Example : Only Main Archives
Keyword : ArchiveConversion [Archiver] <OnlyMainArchive> <NoSFX>
<NoSecure> <ToSFX> <EmbeddedOnlyNormalNames>
For more information about the ArchiveConversion keyword, please
read the section about that keyword.
- 48 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
Don't convert secure archives
-----------------------------
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 archives embedded in secure archives will not
be altered in any way.
PalmScan can detect ARJ security envelopes, ZIP and RAR authenticity
verifications and UC2 seals.
Example : X
Keyword : ArchiveConversion [Archiver] <OnlyMainArchive> <NoSFX>
<NoSecure> <ToSFX> <EmbeddedOnlyNormalNames>
For more information about the ArchiveConversion keyword, please
read the section about that keyword.
Note : This is a bonus feature, which is available in the
registered version only.
Only convert embedded archives with normal extensions
-----------------------------------------------------
When this switch is used, PalmScan will only convert embedded
archives which have a normal extension. This can be useful for
archives which contain an installation program, which then uses the
embedded archives to install a software product. Usually, those
embedded archives do not have a normal extension, so they will not be
converted by PalmScan when this option is used.
The main archive will be converted as usual.
Example : X
Keyword : ArchiveConversion [Archiver] <OnlyMainArchive> <NoSFX>
<NoSecure> <ToSFX> <EmbeddedOnlyNormalNames>
For more information about the ArchiveConversion keyword, please
read the section about that keyword.
Note : This is a bonus feature, which is available in the
registered version only.
- 49 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
ArchiveConversion configuration keyword
---------------------------------------
Keyword : ArchiveConversion [Archiver] <OnlyMainArchive> <NoSFX>
<NoSecure> <ToSFX> <EmbeddedOnlyNormalNames>
[Archiver] This sets the target. You can supply all values
you configured with the Archiver statement.
<OnlyMainArchive> Do not convert embedded archives.
<NoSFX> Do not convert self-extracting
archives.
<NoSecure> Do not convert secure archives.
<ToSFX> The selected archiver creates
self-extracting archives.
<EmbeddedOnlyNormalNames> Only convert embedded archives
which have a normal extension.
Example : ArchiveConversion RAR OnlyMainArchive NoSecure
Convert ALL archives
--------------------
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.
When Only Main Archives is selected, only main archives which are
already in the target archive type will be converted. Embedded
archives which are already in the target archive will not be
converted.
Example : Yes
Keyword : ConvertAll <OnlyMainArchive>
<OnlyMainArchive> Only convert main archives which are already
in the target format.
Example : ConvertAll OnlyMainArchive
- 50 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
3.4.3 Self-Extracting Archives
-------------------------------
Process SFX archives
--------------------
By default, self-extracting (SFX) archives, are not recognised as
being archives. With this switch, you can tell PalmScan to process
self-extracting archives, just like every other archive. PalmScan can
detect ZIP, LZH, SQZ, ARJ, PAK, RAR and UC2 self-extracting archives.
Example : X
Keyword : ProcessSFX
Example : ProcessSFX
Do not convert self-extracting archives
---------------------------------------
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, embedded archives will not be altered.
Example : X
Keyword : ArchiveConversion [Archiver] <OnlyMainArchive> <NoSFX>
<NoSecure> <ToSFX> <EmbeddedOnlyNormalNames>
For more information about the ArchiveConversion keyword, please
read the section about that keyword.
Process UC2 self-extracting archives
------------------------------------
While UC2 itself (UC.EXE) cannot unpack them, UC2 self-extracting
archives have to be executed to extract files from it. By default,
PalmScan will not unpack UC2 SFX archives. The reason is simple, it's
just not safe (the file can be infected by viruses, or it could be a
trojan). To make PalmScan unpack UC2 SFX archives, this switch must
be used.
When one or more virus scanner(s) have been configured (Scanner
keyword), and *.EXE or anything implying *.EXE should be scanned
(VirusScan keyword), PalmScan will scan the UC2 self-extracting
archive for viruses before it will be unpacked.
Example : X
Keyword : UC2SFX [Commandline] <SecureOnly>
For more information about the UC2SFX keyword, please read the
section about that keyword.
- 51 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
UC2 SFX commandline options
---------------------------
The commandline which should be passed on to the UC2 self-extracting
archive (.EXE), when executing it, must be configured here when the
Process UC2 self-extracting archives option has been enabled.
Example : -o .
Keyword : UC2SFX [Commandline] <SecureOnly>
For more information about the UC2SFX keyword, please read the
section about that keyword.
Only process sealed UC2 self-extracting archives
------------------------------------------------
When this option is used, PalmScan will only unpack (execute) UC2
self-extracting archives which have been sealed.
Example : X
Keyword : UC2SFX [Commandline] <SecureOnly>
For more information about the UC2SFX keyword, please read the
section about that keyword.
Note : This is a bonus feature, which is available in the
registered version only.
UC2SFX configuration keyword
----------------------------
Keyword : UC2SFX [Commandline] <SecureOnly>
[Commandline] The commandline which should be passed on to the
UC2 self-extracting archive (.EXE), when
executing it.
<SecureOnly> When this option is used, PalmScan will only
unpack (execute) UC2 self-extracting archives
which have been sealed.
Example : UC2SFX -o_. SecureOnly
- 52 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
UC2 SFX seal test command
-------------------------
When only sealed UC2 SFX archives may be processed, PalmScan can test
the seal before the UC2 self-extracting archive will be unpacked. The
command to test the seal can be specified here.
Example : USAFE.EXE
Keyword : UC2SealTest [Command]
[Command] The command to execute to test UC2 seals.
Example : UC2SealTest USAFE.EXE
Note : This is a bonus feature, which is available in the
registered version only.
Scan SFX archives for viruses
-----------------------------
When one or more virus scanner(s) have been configured to scan *.EXE
or anything implying *.EXE, and this feature is used, PalmScan will
scan all self-extracting archives prior to processing them.
When this option is not used, PalmScan will still scan UC2 self-
extracting archives will still be scanned (see UC2SFX keyword).
Example : X
Keyword : ScanSFX
Example : ScanSFX
- 53 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
3.4.4 Archive Headers
----------------------
Archive header file
-------------------
PalmScan can add a header to your archives. When this filename points
to a valid ASCII textfile, this file will be used as header for the
archive.
When using UC2 as archiver, PalmScan can also add multimedia headers.
The file configured with this option will be added as TXT header. For
multimedia headers, 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
header, but do want to use other headers, you should put the filename
of the other headers 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
header as if they were normal text files).
Example : C:\PALMSCAN\HEADER.ASC
Keyword : ArchiveHeader [d:\path\filename.ext]
[d:\path\filename.ext] This is the full path and filename to
the header text file.
Example : ArchiveHeader C:\PALMSCAN\HEADER.ASC
Alternative header file
-----------------------
Just like with the archive header file option, PalmScan can add this
header to your archives. This archive header will only be used with
the archive type(s) which have the alternative header switch set.
This can be very useful for adding an ANSI header to archives which
support it, and add a normal text file to all other archives.
Example : C:\PALMSCAN\HEADER.ANS
Keyword : AnsiHeader [d:\path\filename.ext] <Archivers>
[d:\path\filename.ext] This is the full path and filename to
the header text file.
<Archivers> The archiver(s) with which this archive
header should be used.
Example : AnsiHeader C:\PALMSCAN\HEADER.ANS RAR
- 54 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
Put FILE_ID description in archive header
-----------------------------------------
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, the description will be appended to it.
Example : X
Keyword : FileIDarchiveHdr
Example : FileIDarchiveHdr
No title in headers
-------------------
By default, PalmScan will add it's title to archive headers, when an
archive header is added. With this option, you can disable it.
Example : X
Keyword : NoTitleInHdr
Example : NoTitleInHdr
Note : This is a bonus feature, which is available in the
registered version only.
- 55 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
3.4.5 Descriptions
-------------------
Import FILE_ID description
--------------------------
When this switch is set, PalmScan will import the description from
FILE_ID.DIZ or DESC.SDI file online or to FILES.BBS and/or the file-
database.
Example : X
Keyword : FileID <OneLine> <Filter> <FiltLow> <MaxWidth=value>
<MaxLines=value>
For more information about the FileID keyword, please read the
section about that keyword.
One line FILE_ID
----------------
When this switch is enabled, PalmScan will place descriptions from
FILE_ID.DIZ or DESC.SDI on one long line, instead of on multiple
lines.
Example : X
Keyword : FileID <OneLine> <Filter> <FiltLow> <MaxWidth=value>
<MaxLines=value>
For more information about the FileID keyword, please read the
section about that keyword.
Filter high ASCII
-----------------
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.
Example : X
Keyword : FileID <OneLine> <Filter> <FiltLow> <MaxWidth=value>
<MaxLines=value>
For more information about the FileID keyword, please read the
section about that keyword.
- 56 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
Filter control codes
--------------------
PalmScan can filter out ASCII control-codes (characters 0 to 31) in
FILE_ID.DIZ or DESC.SDI descriptions before importing them.
Example : X
Keyword : FileID <OneLine> <Filter> <FiltLow> <MaxWidth=value>
<MaxLines=value>
For more information about the FileID keyword, please read the
section about that keyword.
Filter drawings
---------------
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 and high ASCII filter functions,
while not everything should be filtered out. PalmScan detects
drawings by looking at character sequences on complete lines.
Example : X
Keyword : FileID <OneLine> <Filter> <FiltLow> <MaxWidth=value>
<MaxLines=value>
For more information about the FileID keyword, please read the
section about that keyword.
Maximum Width
-------------
The maximum width of imported descriptions can be configured with
this option.
Example : 50
Keyword : FileID <OneLine> <Filter> <FiltLow> <MaxWidth=value>
<MaxLines=value>
For more information about the FileID keyword, please read the
section about that keyword.
- 57 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
Maximum Length
--------------
The maximum number of lines of imported descriptions can be
configured with this option.
Example : 25
Keyword : FileID <OneLine> <Filter> <FiltLow> <MaxWidth=value>
<MaxLines=value>
For more information about the FileID keyword, please read the
section about that keyword.
FileID configuration keyword
----------------------------
Keyword : FileID <OneLine> <Filter> <FiltLow> <MaxWidth=value>
<MaxLines=value>
<OneLine> Import extended descriptions on one (long)
line.
<Filter> Filter out high ASCII (characters 127-255)
from descriptions when importing them.
<FiltLow> Filter out ASCII control codes (characters
0-31) from descriptions when importing them.
<FiltDraw> Filter out standard ASCII drawings from
descriptions when importing them.
<MaxWidth=value> The maximum width of imported descriptions.
<MaxLines=value> The maximum number of lines of imported
descriptions.
Example : FileID OneLine Filter FiltLow FiltDraw
MaxWidth=50 MaxLines=25
- 58 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
Describe MOD's
--------------
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.
When Only Main Archives is selected, 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 embedded archive processing is enabled.
Example : Yes
Keyword : DescribeMod <OnlyMainArchive>
Example : DescribeMod OnlyMainArchive
- 59 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
3.5 Archivers
--------------
The archivers are essential for PalmScan's operation. They are needed
to extract files from archives, pack archives, add headers and test
archives. This section explains what the commands are used for.
3.5.1 Archiver commands
------------------------
In the configuration file, every archiver takes up multiple lines.
First, there must be an Archiver keyword:
Keyword : Archiver [ext]
[ext] This is the normal extension of archives created
by this archiver. This will also be used as the
name of the archive within PalmScan.
Example : ZIP
After the Archiver keyword, all commands can be specified. There are
several keywords available which must be used to pass on parameters
to the archivers:
@Archive Will be replaced by the full path and filename of the
archive which is being processed. When the path and/or
filename contains spaces, PalmScan will add a '"'
(without quotes) before and after the path\filename.
@Path Will be replaced by the directory, without trailing
backlash ('\'), where files should be unpacked to or
packed from. This keyword usually is not necessary
with most archivers, while PalmScan will always make
this directory the current directory before executing
an archiver command.
@Filename Will be replaced by the filename to be unpacked,
packed or added as archive header. This can be either
*.* or a normal filename.
@Filenames Will be replaced by the filenames to be unpacked,
packed or added as archive header. This can be either
*.*, a normal filename, or multiple normal filenames
(separated by spaces). This keyword should never be
used in conjunction with @Path, while only the first
filename would get the path in front of it then. It
should only be used when the archiver supports
multiple filenames on it's commandline.
@Size Will be replaced by the target size when packing a
multi-volume archive. Therefor, this keyword is only
available at the multi-volume compression commands.
- 60 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
@Password Will be replaced by the password needed to unpack or
test a password protected archive. When no password is
needed, it will be replaced by an empty string, and
the commandline option directly in front of this
keyword will be removed.
This option is available at the Unpack, OS2unpack,
MVunpack, OS2MVunpack, Test and OS2test commands.
When this keyword is not used, PalmScan will never try
to unpack or test a password protected archive.
For each command, there are two versions: A DOS command and an OS/2
command. The DOS version of PalmScan will only use the DOS commands.
The OS/2 version will use the OS/2 command when configured, and the
DOS command when no OS/2 command is available. The OS/2 version will
also use the DOS unpack and/or test commands when a password
protected archive is being processed, and the @Password keyword is
not used with the OS/2 unpack and/or test commands, and is used with
the DOS unpack and/or test commands.
In the following sections, ZIP will be used as examples at most
commands, RAR is used at the multi-volume commands. A complete list
of commands is listed at the end of this chapter.
Compression
-----------
This is the full command for the current archiver to compress files.
Example : pkzip -ex -r -p @Archive @Filenames
Keywords : Pack [command]
OS2pack [command]
Examples : Pack pkzip -ex -r -p @Archive @Filenames
OS2pack zip -r -9 -S @Archive @Filenames
Decompression
-------------
This is the full command for the current archiver to extract
archives.
Example : pkunzip -o -d -s@Password @Archive @Filenames
Keywords : Unpack [command]
OS2unpack [command]
Examples : Unpack pkunzip -o -d -s@Password @Archive
@Filenames
OS2unpack unzip -o @Archive @Filenames
- 61 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
Add Header
----------
This is the full command for the current archiver to add a header to
an archive.
Example : pkzip -z<@Path\@Filename @Archive
Keywords : Header [command]
OS2header [command]
Examples : Header pkzip -z<@Path\@Filename @Archive
OS2header zip -z<@Path\@Filename @Archive
Besides using it for adding an archive header, this feature can also
be used to add an authenticity validation. For example, this can be
used for ZIP:
Header C:\PALMSCAN\ZIPAV.BAT @Path\@Filename @Archive
Where ZIPAV.BAT would contain this:
copy C:\PALMSCAN\AVEXTRA.TXT .\
pkzip -! -ex -xAVEXTRA.TXT %2
pkzip -z<%1 %2
Alternative header
------------------
Check this switch to use the alternative archive header with this
archiver.
Example : X
Keyword : AnsiHeader [d:\path\filename.ext] <Archivers>
Example : AnsiHeader C:\PALMSCAN\HEADER.ANS RAR
- 62 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
Test
----
When an archive cannot be unpacked, PalmScan will test the archive
when a test command has been configured. This can be useful for
archives which have been created with another file-system (e.g. HPFS
long filenames cannot be unpacked in DOS). Normally, PalmScan will
mark those archives as bad, but when the archive test feature is
used, it will only be marked as bad when it also fails the archive
test.
This feature should be used with caution! When an archive cannot be
unpacked, and it does pass the archive test, these actions will not
be performed:
- Virus scan
- Embedded archive processing
- Old files check will only be done when configured to check the
original date
- Removal of unwanted files
- Adding files
- Music files descriptions
- Adding CRC-32 file list
In brief, you should only use this feature when necessary. I.e., if
you never or hardly ever receive any files which are marked as bad
because of the filenames in the archive, you should not use this
feature.
Example : pkzip -t -s@Password @Archive
Keywords : Test [command]
OS2test [command]
Examples : Test pkzip -t -s@Password @Archive
OS2test zip -T @Archive
Note : This is a bonus feature, which is available in the
registered version only.
Multi-Volume Compression
------------------------
This is the full command for the current archiver to create a multi-
volume archive.
Example : rar a -r -y -o- -std -m5 -v@Size @Archive @Filenames
Keywords : MVpack [command]
OS2MVpack [command]
Examples : MVpack rar a -r -y -o- -std -m5 -v@Size @Archive
@Filenames
OS2MVpack rar a -r -y -o- -std -m5 -v@Size
@Archive @Filenames
- 63 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
Multi-Volume Decompression
--------------------------
This is the full command for the current archiver to unpack multi-
volume archives.
Example : rar x -r -y -o- -std -c- -p@Password @Archive
@Filenames
Keywords : MVunpack [command]
OS2MVunpack [command]
Examples : MVunpack rar x -r -y -o- -std -c- -p@Password
@Archive @Filenames
OS2MVunpack rar x -r -y -o- -std -c- -p@Password
@Archive @Filenames
Example archiver commands
-------------------------
Here follows a list of archiver commands which can be used in
PalmScan. Please note that this list is not complete. It contains
only those commands that have been tested with PalmScan. The Test
commands have intentionally been left out, while those should not be
used by unexperienced users.
Archiver ARC
Pack pkarc a @Archive @Filenames
OS2pack arc a @Archive @Filenames
Unpack pak e /wa @Archive @Filenames
OS2unpack arc xo @Archive @Filenames
Header pkarc x<@Path\@Filename @Archive
Archiver ZIP
Pack pkzip -ex -r -p @Archive @Filenames
OS2pack zip -k -r -9 -S @Archive @Filenames
Unpack pkunzip -o -d -s@Password @Archive @Filenames
OS2unpack unzip -o @Archive @Filenames
Header pkzip -z<@Path\@Filename @Archive
OS2header zip -z<@Path\@Filename @Archive
Archiver LZH
Pack lha a /rxpat @Archive @Filenames
Unpack lha x /c @Archive @Filenames
Archiver ZOO
Pack zoo aPh @Archive @Filenames
Unpack zoo eO// @Archive @Filenames
Header zoo cA<@Path\@Filename @Archive
Archiver SQZ
Pack sqz a /p3 /s @Archive @Filenames
Unpack sqz x -o1 @Archive @Filenames
- 64 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
Archiver HYP
Pack hyper -a @Archive @Filenames
Unpack hyper -xo @Archive @Filenames
Archiver ARJ
Pack arj a -r -y @Archive @Filenames
Unpack arj x -y -g@Password @Archive @Filenames
OS2unpack unarj X @Archive @Filenames
MVpack arj a -r -y -v@Size @Archive @Filenames
MVunpack arj x -y -v -g@Password @Archive @Filenames
Header arj c -z@Path\@Filename @Archive
Archiver HAP
Pack hap a @Archive @Filenames
Unpack pah e @Archive @Filenames
Archiver PAK
Pack pak a /i @Archive @Filenames
Unpack pak e /wa @Archive @Filenames
Header pak h<@Path\@Filename @Archive
Archiver UC2
Pack uc a -s -tst -f -b @Archive @Filenames
Unpack uc e -s -f !ban=off @Archive @Filenames
Header uc a -tt -f -b @Archive @Path\@Filename
Archiver RAR
Pack rar a -r -y -o- -std -m5 @Archive @Filenames
OS2pack rar a -r -y -o- -std -m5 @Archive @Filenames
Unpack rar x -r -y -o- -std -c- -p@Password @Archive @Filenames
OS2unpack rar x -r -y -o- -std -c- -p@Password @Archive @Filenames
MVpack rar a -r -y -o- -std -m5 -v@Size @Archive @Filenames
OS2MVpack rar a -r -y -o- -std -m5 -v@Size @Archive @Filenames
MVunpack rar x -r -y -o- -std -c- -p@Password @Archive @Filenames
OS2MVunpack rar x -r -y -o- -std -c- -p@Password @Archive @Filenames
Header rar c -y -std @Archive =@Path\@Filename
OS2header rar c -y -std @Archive =@Path\@Filename
Archiver DWC
Pack dwc a @Archive @Filenames
Unpack dwc e @Archive @Filenames
- 65 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
3.5.2 Archive Protection
-------------------------
UC2 protection
--------------
When an archive has been converted to UC2, PalmScan can add all
available UC2 protections to it. By default, no protection will be
added.
Keyword : UC2protection <BasicUpdates> <Delete> <Add> <Optimize>
<Unprotect> <ReviseComment>
<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
--------
When an archive has been converted to RAR, PalmScan can add a lock to
it. By default, RAR archives will not be locked.
Keywords : RARlock [command]
OS2RARlock [command]
[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
- 66 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
3.6 Virus scan
---------------
3.6.1 Files to scan
--------------------
In this list, file specifications of files which should be scanned
for viruses, can be entered. When one or more files which comply to
the file specifications configured here, PalmScan will start the
virus scan.
Examples : *.EXE
*.COM
*.OV?
*.DLL
Keyword : VirusScan <filespec> <filespecs>
<filespec> This can be any valid DOS or OS/2 file
specification.
When you give a file specification, 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, and the
VirusScan keyword is used, PalmScan will always
execute the virus scanner(s). In PSetup, there
must always be at least one file specification,
e.g. *.*.
Example : VirusScan *.EXE *.COM *.OVR *.OVL
3.6.2 Virus scanners
---------------------
Here up to 20 virus scanners can be configured. There are two
keywords available for this: Scanner and OS2scanner. The DOS version
always uses the Scanner keyword, the OS/2 uses the OS2scanner keyword
and, when no OS/2 scanner is configured with the same name, the
Scanner keyword.
Scanner name
------------
This is the name of the virus scanner.
Keywords : Scanner [name] [command] [lll] <[hhh] <[nnn]
<filespecs>>>
OS2scanner [name] [command] [lll] <[hhh] <[nnn]
<filespecs>>>
For more information about the Scanner keyword, please read the
section about that keyword.
- 67 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
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 keywords which
will be replaced with the correct string by PalmScan:
@PATH The directory that should be scanned (without trailing
backlash).
@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)
@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.
Keywords : Scanner [name] [command] [lll] <[hhh] <[nnn]
<filespecs>>>
OS2scanner [name] [command] [lll] <[hhh] <[nnn]
<filespecs>>>
For more information about the Scanner keyword, please read the
section about that keyword.
Low Errorlevel
--------------
This is the lowest errorlevel the virus scanner will return when a
virus has been found.
Keywords : Scanner [name] [command] [lll] <[hhh] <[nnn]
<filespecs>>>
OS2scanner [name] [command] [lll] <[hhh] <[nnn]
<filespecs>>>
For more information about the Scanner keyword, please read the
section about that keyword.
- 68 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
High Errorlevel
---------------
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 the low errorlevel when a virus has been
found.
Keywords : Scanner [name] [command] [lll] <[hhh] <[nnn]
<filespecs>>>
OS2scanner [name] [command] [lll] <[hhh] <[nnn]
<filespecs>>>
For more information about the Scanner keyword, please read the
section about that keyword.
Other Errorlevel
----------------
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 scanners which return another
errorlevel just because there are no executables found. With this
option you can make PalmScan simply ignore that errorlevel.
Keywords : Scanner [name] [command] [lll] <[hhh] <[nnn]
<filespecs>>>
OS2scanner [name] [command] [lll] <[hhh] <[nnn]
<filespecs>>>
For more information about the Scanner keyword, please read the
section about that keyword.
File specifications
-------------------
Up to 5 file specifications can optionally be given. First, PalmScan
will check the global file specifications (configured in the files to
scan section). 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.
Keywords : Scanner [name] [command] [lll] <[hhh] <[nnn]
<filespecs>>>
OS2scanner [name] [command] [lll] <[hhh] <[nnn]
<filespecs>>>
For more information about the Scanner keyword, please read the
section about that keyword.
- 69 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
Scanner configuration keyword
-----------------------------
Keyword : Scanner [name] [command] [lll] <[hhh] <[nnn] <filespecs>>>
[name] The name of the virus scanner.
[command] The command to start this virus scanner.
[lll] The lowest errorlevel the virus scanner returns when a
virus has been found.
<hhh> The highest errorlevel the virus scanner returns when
a virus has been found.
<nnn> The errorlevel that the virus scanner returns when
nothing is wrong.
<filespecs> Up to 5 scanner-specific file specifications.
Examples : Scanner McAfee_Scan
SCAN_/NOEXPIRE_/NOMEM_/REPORT_@REPORT_/SUB_@FULL
13 13 14
OS2scanner McAfee_Scan
OS2SCAN_/NOEXPIRE_/REPORT_@REPORT_/SUB_@FULL 13
13 14
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
- 70 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
3.6.3 Options
--------------
Complete scan
-------------
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 all infected
files in an archive.
Example : X
Keyword : CompleteScan
Example : CompleteScan
Fast scan
---------
PalmScan can scan for viruses in the main archive and in all embedded
archives in one run. When this feature is used, PalmScan will unpack
all embedded archives right after the main archive has been unpacked.
The virus scan is done at the point where it would normally scan for
viruses in the main archive. All other embedded archive processing is
done the same as without this feature.
For the fast scan feature to work properly, your virus scanners must
be configured to scan the current directory and all subdirectories.
(The example virus scanner commands will do this properly).
When this feature is not used, PalmScan will scan each embedded
archive separately.
Example : X
Keyword : FastScan
Example : FastScan
Note : This is a bonus feature, which is available in the
registered version only.
No DOS scanners
---------------
When this keyword is used, the OS/2 version of PalmScan will ignore
the configured DOS virus scanners, and only use the OS/2 virus
scanners. This keyword has no effect on the operation of the DOS
version.
Example : X
Keyword : NoDOSscanners
Example : NoDOSscanners
- 71 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
3.7 Hacked Files
-----------------
In this list, file-specifications of files which are dangerous or
unwanted can be configured.
Files which are found in this list, will be moved to the hacked files
directory, or, when no hacked files directory is configured, PalmScan
will exit with an errorlevel.
For this feature to work properly, a hacked files list must be
configured in the files lists section.
Example : PKZIP201.*
3.8 Skip Files
---------------
In this list, file-specifications of files which should not be
processed can be configured. Full path names can also be included in
these file specifications.
For this feature to work properly, a skip files list must be
configured in the files lists section.
Examples : BIMODEM.LOG
D:\FILES\SKIP\*.*
- 72 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
3.9 Pack Unpacked
------------------
File specifications
-------------------
In this list, file-specifications of unpacked files which should be
packed can be configured. All files which comply to one or more of
the configured file-specifications, and are not archives, will be
archived with the archiver configured at the archive conversion
feature.
For this feature to work properly, a pack unpacked files list must be
configured in the files lists section.
Example : *.TXT
Minimum size
------------
The minimum size (in bytes) for unpacked files which should be
packed, can be configured with this option. This option is available
so very small files will not be packed, which would otherwise cause
an archive which is larger than the original file.
Another use can be that files which fit into one allocation block (on
FAT partitions, this often is 8192 bytes) will not get packed. It
might result in a smaller file when a file which is smaller than one
allocation block is packed, but wouldn't result in reduction in disk
space usage.
Example : 2048
Keyword : PackUnpackedSize [size]
[size] This is the minimum size in bytes.
Example : PackUnpackedSize 2048
- 73 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
3.10 Remove Files
-----------------
Many archives contain some files which have no relation with the
actual archive, like advertisements added at bulletin boards. This
can eventually take up a large part of your available disk space.
PalmScan can remove these files from the archives.
In this list, file-specifications of files which should be removed
from archives, can be configured. Optional for each file-
specification, a filesize and CRC-32 can be configured. When a
filesize and/or CRC-32 is configured for a file-specification, only
those files which comply to the file-specification and have the
filesize and/or CRC-32 as configured for this file-specification,
will be removed. This can be useful for removing advertisements which
have another filename every time, but have the same contents (thus
have the same filesize and CRC-32). It can also be used to remove
empty files by configuring the filesize to 0.
For this feature to work properly, a remove files list must be
configured in the files lists section.
Examples : OASISBBS.ADV
CALL.* /SIZE=248 /CRC=23a86bf9
*.* /SIZE=0
- 74 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
3.11 Add Files
--------------
Just like PalmScan can remove files from archives, it can also add
files to them. This can be used to add an advertisement for your
bulletin board, or whatever you want added to the archives.
Only full path and filenames can be configured in this list. PalmScan
will add these files in the home directory of the main archive.
For this feature to work properly, an add files list must be
configured in the files lists section.
Example : C:\PALMSCAN\OASISBBS.ADV
Add CRC file list
-----------------
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 v2.02 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.
Example : Only Main Archive
Keyword : AddCRCfile <OnlyMainArchive>
<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 when using the
registered version of PalmScan.
- 75 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
3.12 Archive Passwords
----------------------
This files-list can contain paths and file-specifications for
archives, and passwords which should be used to unpack those
archives.
When a password protected archive is found in this list, PalmScan
will use the password configured here to unpack or test the archive.
When the archive is not found in this list, and PalmScan is running
in interactive mode (/Interactive commandline option), PalmScan will
ask for the password before it starts to unpack or test the archive.
When an archive is not found in this list, and PalmScan is not
running in interactive mode, it will never try to unpack or test an
archive.
Example : ALLFIX.* /Password=FINALLY
- 76 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
3.13 GIF settings
-----------------
Add GIF specifications to descriptions
--------------------------------------
PalmScan will add GIF/PNG (resolution and colors) and JFIF/JPEG
(resolution and color/gray) specifications 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 a 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 : X
Keyword : GIFspecs <[left bracket] ['by' character] [right
bracket]>
Example : GIFspecs < * >
- 77 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
GIF pack
--------
To convert GIF pictures to another format, this feature can be used.
The title is only used to display to what format the file is being
converted, but must be configured when using this feature.
The command that should be executed to convert the GIF picture must
also be configured when using this feature.
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.
If you do not want embedded graphics files to be converted, 'Do NOT
convert embedded graphics files' should be selected. Some archives
contain graphics files which are used by the program(s) inside the
archive. Converting those graphics files would result in the programs
not finding the graphics files when they are needed.
Programs which replace the original file (e.g. GIFlite) can be used
with this feature.
Example : X
JFIF
CJPEG.EXE @FILENAME.@EXT @FILENAME.JPG
Keyword : GIFpack [title] [command] <NoEmbedded>
[title] The title of the configured GIF pack utility.
[command] The command that should be executed to pack the
GIF file.
<NoEmbedded> Do not convert embedded graphics files.
Example : GIFpack JFIF CJPEG.EXE @FILENAME.@EXT
@FILENAME.JPG
- 78 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
JFIF unpack
-----------
PalmScan will use this command 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.
Example : DJPEG.EXE
Keyword : JFIFunpack [command]
[command] This is the command that should be executed to
convert the JFIF file.
Example : JFIFunpack DJPEG.EXE
JPEG unpack
-----------
This is almost 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.
Example : JPG2GIF.EXE
Keyword : JPEGunpack [command]
[command] This is the command that should be executed to
convert the JPEG file.
Example : JPEGunpack JPG2GIF.EXE
GIFblast unpack
---------------
PalmScan will use this command to convert GIFblast files to GIF.
Example : GIFBLAST.EXE -D
Keyword : GIFBLASTunpack [command]
[command] This is the command that should be executed to
convert the GIFblast file.
Example : GIFBLASTunpack GIFBLAST.EXE_-D
- 79 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
Repack JFIF files
-----------------
When this option is selected, JFIF files will first be converted to
GIF, and then converted using the command configured with the GIFpack
keyword.
Example : X
Keyword : JFIFrepack
Example : JFIFrepack
Repack JPEG files
-----------------
hen this option is selected, JPEG files will first be converted to
GIF, and then converted using the command configured with the GIFpack
keyword.
Example : X
Keyword : JPEGrepack
Example : JPEGrepack
Repack GIFblast files
---------------------
When this option is selected, GIFblast files will first be converted
to GIF, and then converted using the command configured with the
GIFpack keyword.
Example : X
Keyword : GIFBLASTrepack
Example : GIFBLASTrepack
- 80 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
Minimum resolution
------------------
PalmScan can reject GIF, PNG, 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 as bad GIF directory. When no bad
GIF directory is configured, PalmScan will exit with errorlevel 205.
When a message area is configured, a message to the system operator
will also be posted.
Example : 320x200x256
Keyword : MinimumResolution [horizontal]x[vertical]x[colors]
[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
---------------------------
PalmScan can use an external GIF testing program to test all GIF
files. Up to ten errorlevels can be configured, which will cause
PalmScan to treat the file as bad GIF file.
Example : GIFTEST.EXE /M:320x200x256
1 20 25
Keyword : GIFtest [command] <errorlevels>
[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
- 81 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
3.14 Old files
---------------
PalmScan can check for files which are too old. Either the maximum
age in days or a date can be used for this check.
The date that will be checked can also be selected. Original means
PalmScan will check the original date of the archive. Oldest means
PalmScan will check the oldest date of all files in the archive.
Latest means PalmScan will check the latest date of all files in the
archive.
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 as old files directory. When no old
files directory is configured, PalmScan will exit with errorlevel
204. When a message area is configured, a message to the system
operator will also be posted.
Example : 01-01-1995
Keyword : OldFiles [[-days]|[dd-mm-yyyy]]
<Original|Latest|Oldest>
[-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
- 82 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
3.15 Include Configurations
----------------------------
In this list, configuration files which should be included in the
configuration, can be configured. PSetup will not read the included
configuration files (else those would be combined to one
configuration file when saving it).
PalmScan will read included configuration files before reading the
entries in the original configuration file, thus options in the
original configuration file can override options in included
configuration files.
Example : C:\PALMSCAN\ARCHIVER.CFG
Keyword : Include [configuration-filename]
[configuration-filename] This is the full path and filename of
the configuration file to be included.
Example : Include C:\PALMSCAN\ARCHIVER.CFG
- 83 -
PalmScan v2.02 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.
- 84 -
PalmScan v2.02 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
Concord Pasi Talliniemi
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, OS/2, PC-DOS International Business Machines Corp.
JAM Joaquim Homrighausen, Andrew Milner,
Mats Birch, Mats Wallin
LHA Haruyasu Yoskizaki
Microsoft, MS-DOS Microsoft Corporation
PAK NoGate Consulting
PKARC, PKZIP PKWARE, Inc.
ProBoard Philippe Leybaert
QuickBBS Pegasus Software
RAFT Chris Buijs
RAR Eugene Roshal
RemoteAccess 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
- 85 -
PalmScan v2.02 User guide
---------------------------------------------------------------------
I Index
--------
/All . . . . . . 19 . . . 55 RegKey . . . . . 27
/AnyArea . . . . 19 FilesBBS . . . . 40 RemoveFilesList . 34,
/C[configuration-file FilesBBSname . . 42 74
name] . 20 GIFBLASTrepack . 80 Scanner . . . . . 70
/Debug . . . . . 23 GIFBLASTunpack . 79 ScanSFX . . . . . 53
/D[dorinfo-filename] GIFpack . . . . . 78 SkipFilesList . . 33,
. . . 20 GIFspecs . . . . 77 72
/FDBmaint<areanr<-are GIFtest . . . . . 81 SubstDrive . . . 32
anr>> . 19 HackList . . 33, 72 SysopName . . . . 27
/Fix<+> . . . . . 20 HackPath . . . . 31 TempPath . . . . 30
/Interactive . . 23 Header . . . . . 62 Test . . . . . . 63
/L . . . . . . . 20 Include . . . . . 83 Touch . . . . . . 47
/Mono . . . . . . 23 IndentSpaces . . 41 UC2protection . . 66
/Move[Path] . . . 22 InfectedPath . . 30 UC2SealTest . . . 53
/NoChanges . . . 21 JFIFrepack . . . 80 UC2SFX . . . . . 52
/NoCls . . . . . 23 JFIFunpack . . . 79 Unpack . . . . . 61
/NoConversion . . 21 JPEGrepack . . . 80 VirusScan . . . . 67
/NoFDB . . . . . 21 JPEGunpack . . . 79
/NoFilesbbs . . . 21 LogFile . . . . . 43
/NoMove . . . . . 22 MessageArea . . . 37
/NoScan . . . . . 22 MinimumResolution
/N[node] . . . . 20 . . . 81
/P[priority] . . 23 MVpack . . . . . 63
/S . . . . . . . 22 MVunpack . . . . 64
/T[archiver] . . 21 NetAddress . . . 35
/Unlisted . . . . 22 NoDiskSpaceCheck
/V[Size] . . . . 22 . . . 44
AddCRCfile . . . 75 NoDOSscanners . . 71
AddFilesList . . 34, NoTitleInHdr . . 55
75 OldFiles . . . . 82
AnsiHeader . . . 54 OldPath . . . . . 31
ArchInArch . . . 46 Online . . . . . 42
ArchiveConversion OnlyNewFiles . . 45
. . . 50 OS2header . . . . 62
ArchiveHeader . . 54 OS2key . . . . . 27
Archiver . . . . 60 OS2MVpack . . . . 63
BadGifPath . . . 31 OS2MVunpack . . . 64
BadPath . . . . . 30 OS2pack . . . . . 61
BBSname . . . . . 27 OS2RARlock . . . 66
BBSpath . . . . . 39 OS2test . . . . . 63
ColorBackground . 29 OS2unpack . . . . 61
ColorEdit . . . . 29 Pack . . . . . . 61
ColorEditBackground PackUnpackedFilesList
. . . 29 . . . 73
ColorHighlight . 28 PackUnpackedList
ColorNormal . . . 28 . . . 33
CompleteScan . . 71 PackUnpackedSize
ConvertAll . . . 50 . . . 73
DescribeMod . . . 59 PasswordList . . 34,
DownloadCounter . 41 76
ExecTimeOut . . . 44 ProcessListedOnly
FastScan . . . . 71 . . . 46
FDB . . . . . . . 38 ProcessSFX . . . 51
FileID . . . . . 58 RARlock . . . . . 66
FileIDarchiveHdr RedirectOutput . 28
- 86 -