-------------------------------------------------------------------------------
PalmScan 1.11 Fidonet 2:2802/140
VirNet 9:310/400
Copyright (C) 1993,94 PNN 13:315/107
by Steven Hendriks DigitalNet 15:1100/300
Hoofd 22 SIGnet 27:1331/40
3214 AH Zuidland OasisNet 52:52/0
the Netherlands AlarmNet 64:300/0
data: +31-1881-3132 (300-19200 bps, 24hrs/day) OASE 203:203/300
-------------------------------------------------------------------------------
This update log decribed the changes since release 1.10.
+ indicates a new option
- indicates a bug fix
/ indicates a changed option
| indicates an option available in the registered version only
- PalmScan could hang the system on some ZIP archives with authenticity
validations which contain large AV info blocks. Fixed.
/ Executing external programs (eg. archivers, virus scanners) is now safer
when no complete directory is configured on the command. PalmScan will never
execute a file which is in a temporary directory (ie. the archive which is
being processed) or in the directory where PalmScan was started (except when
that directory is in the path, or when no path is configured (PATH
environment variable).
Please note that it is always faster to include a full path (and extension)
of external programs, while PalmScan doesn't have to search for the
executable before executing it then.
- PalmScan did not update the RemoteAccess file-database when directories in
the RemoteAccess file-area configuration had a trailing backslash. Fixed.
/ Changed the keywords 'RAfilebase' to 'FDB RA', and 'RApath' to 'BBSpath'.
PalmScan will still understand the old keywords though.
+ Added support for the Ezycom file-database. The configuration keyword to
enable this feature is:
FDB Ezycom
For using this option, the EZY environment variable must be set, or the
Ezycom system directory must be specified with this keyword:
BBSpath [D:\PATH]
PalmScan will always use the FIRST area which uses the same directory as
where the file which is being processed was found.
When the FileID keyword is also used, 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 an infected file, an archive which can't be unpacked, or a file which
exists in the Hacklist, was found, PalmScan will use the normal procedure to
either move the file or exit with an errorlevel, and besides this it will
also mark the file as offline in the Ezycom file-database.
- Fixed a problem with opening the FILES.BBS when it was already opened by
another program (this could occur when running under SuperBBS).
+ Added three commandline options:
/MONO - Forces monochrome mode.
/NOCLS - Do not clear the screen at startup.
| /NOREG - Do not display 'Registered to ...' at startup.
+ Added support for the DOOR.SYS dropfile. In online mode, PalmScan will now
first check for this file, and use it if it exists. If it does not exist,
PalmScan will still use the DORINFOx.DEF dropfile.
+ The PalmScan FileInfo system has been built in. This system introduces an
enhanced communication between PalmScan and programs using PalmScan. It will
most likely be built in into some many-used programs, such as File Echo
Processors.
To use this feature, you should startup PalmScan with one of these
commandline options:
/FIX - Read-Only mode, the FileInfo file will be deleted when all files
have been processed.
/FIX+ - 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.
+ Added a maintenance for the Ezycom file-database. The commandline option for
this feature is:
/FDBMAINT<areanr>
PalmScan will first search the FDB for files which haven't been checked, and
place them in a file called FILEINFO.FIX. After that, the PalmScan FileInfo
system will take over and all those files will be processed.
Files will be converted to the archiver configured in the Ezycom file-area
configuration.
When no area number is specified, all areas will be processed.
· Note : When using PalmScan with Ezycom, the file-database can NOT be updated
when PalmScan is started from UPCONV.BAT or DOCONV.BAT. Ezycom will handle
this itself, so you should disable 'FDB Ezycom' when PalmScan is started
from either one of these batchfiles within Ezycom. The best way to use
PalmScan with Ezycom is by not using it in these batchfiles, but running
it in an event with the FDB maintenance feature.
- Fixed a memory problem in PSetup.
+ Added support for UltraCompressor II (UC2).
Example PalmScan configuration settings for UC2:
Archiver UC2 uc_a_-s_-tt_-f_-b uc_e_-s_-f_!ban=off uc_a_-tt_-f_-b
(!ban=off is quite important when unpacking archives, while you wouldn't
want your pc waiting for a key when displaying a GIF picture, or wake up
with the sound of a MOD file blasting through the house;-).
The archive header configured in the PalmScan configuration will be added as
.TXT type banner, for multimedia banners, you should put the GIF/JPG/MOD/ASK
files in the same directory and filename as the configured archive header,
and with extension GIF/JPG/MOD/ASK. Example:
ArchiveHeader c:\text\banner.asc
This will add banner.asc as .TXT header, and banner.gif, banner.jpg,
banner.mod and/or banner.ask (when found) as multimedia banners.
If you don't want to use the .TXT banner, but do want to use other banners,
you should put the filename of the other banners at the ArchiveHeader
keyword without extension, or with an extension of a non-existing file
(never put the .GIF/JPG/MOD extensions there, PalmScan will then add these
files as archive banner as if they were normal text files).
PalmScan does not yet detect any seals on UC2 archives, this will be added
as soon as I've received more information on this.
/ PalmScan will now display some help about the commandline parameters when
started without any.
+ Pressing escape will now abort the PalmScan run. PalmScan will first finish
the file which is being processed, and after that ask if it should continue
processing or not.
+ The filename of the files.bbs file to be used can now be configured:
FilesBBSname [filename]
By default, [filename] is FILES.BBS.
When it is configured to another filename, PalmScan will first try this
file, and if that fails it will still use the normal FILES.BBS. This option
can also be used for 4DOS descript.ion files, or when you have your
files.bbs in a sub-directory of the directory where the files are located,
eg: FilesBBSname LIST\FILES.BBS
- On some systems, PalmScan wouldn't detect errorlevels of external programs
correctly. Fixed.
/ |When ZIP archives which have an AV are not being converted (NoSecure option
|at the ArchiveConversion keyword), PalmScan will now add a header to it
|(when an archive header is configured).