-------------------------------------------------------------------------------
PalmScan v1.12 Fidonet 2:2802/140
VirNet 9:310/0
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-28800 bps) OASE 200:3110/0
-------------------------------------------------------------------------------
Internet : stv_hendriks@hrovx1.hro.nl
steven.hendriks@f140.n2802.z2.fidonet.org
uucp : uunet!m2xenix!puddle!2!2802!140!steven.hendriks
-------------------------------------------------------------------------------
This update log describes the changes since release 1.11.
+ indicates a new option
- indicates a bug fix
/ indicates a changed option
| indicates an option available in the registered version only
+ Added detection for UC2 seals.
+ Added support for UC2 protection. When an archive is being converted to UC2,
PalmScan can add all available UC2 protections. The configuration keyword
for this feature is:
UC2protection
By default, no protection will be added. The options for UC2protection are:
BasicUpdates - No basic updates
Delete - No delete
Add - No add
Optimize - No optimize
Unprotect - No unprotect
ReviseComment - No revise comment
Example : UC2protection Add Unprotect
- This will protect converted UC2 archives against adding and
unprotecting.
/ Added a commandline option: /N[node]
When the node number is specified with this commandline option, PalmScan
will use it's multi-node support. This makes sure that PalmScan will run
smoothly on multi-node systems.
+ |The maximum number of lines and the maximum width of descriptions imported
|in the RemoteAccess and Ezycom 1.10 file-databases, from file_id.diz and
|desc.sdi are now configurable with these options (at the FileID keyword) :
| MaxWidth=<number of characters>
| MaxLines=<number of lines>
|Example:
| FileID MaxWidth=50 MaxLines=25
|Using these options when using the OneLine option can change the lay-out of
|the descriptions completely (just try it:).
|These options are only available for the RemoteAccess 2.0x and Ezycom 1.10
|file-databases.
+ Added support for the Ezycom 1.10 file-database. All features for
description manipulation are available: OneLine, Filter, FiltLow, FiltDraw,
MaxWidth and MaxLines. PalmScan will use a maximum description size of 2048
characters (as specified in the Ezycom structures).
Also, support for SQZ has been added for Ezycom 1.10 users when running the
FDB maintenance.
The configuration keyword for the Ezycom 1.10 fdb support is the same as for
the Ezycom 1.02 fdb support:
FDB Ezycom
PalmScan will detect the version used.
+ Added support for the Ezycom 1.10 FILE_ID importing function. PalmScan will
place the FILE_ID.<node> file in the temporary directory as configured in
the Ezycom configuration.
The configuration keyword for this function is:
EzyFileID
The node on which PalmScan is running must also be specified on the
commandline with this commandline option:
/N[node]
Also, the FileID keyword must be used in the PalmScan configuration. The
OneLine, Filter, FiltLow and FiltDraw options also work with this function.
The 'FDB Ezycom' keyword should not be used with this (or /NoFDB should be
used on the commandline), it won't work when running in UPCONV.BAT while
Ezycom places uploaded files in a temporary upload directory.
When running in local-only mode (/L commandline option), PalmScan will never
create the FILE_ID.<node> file.
/ When running in local-only mode (/L commandline option), PalmScan will no
longer update any FileDoor files.
+ |Standard ASCII drawings (for which characters within the range 32 to 126 are
|used) in descriptions can now be filtered out before importing these
|descriptions. The switch at the FileID keyword for this option is:
| FiltDraw
|This works a bit different than the control codes (FiltLow) and high ascii
|(Filter) filter functions, while not everything should be filtered out.
|PalmScan is able to filter out most of the drawings, but I cannot guarantee
|that everything is filtered out. PalmScan would need too much artificial
|intelligence for that ;-)
+ Added a maintenance for the RemoteAccess file-database. The commandline
option for this feature is:
/FDBMAINT<areanr>
PalmScan will first search the FDB for files which haven't been processed,
and place them in a file named FILEINFO.FIX. After that, the PalmScan
FileInfo system will take over and all those files will be processed.
Files will be converted to the archive format configured in the RemoteAccess
file-area configuration. When no archive format is configured for an area,
files in that will not be processed.
PalmScan uses LASTSCAN.PS in the file-database directory to store the last
time when the FDB maintenance has been run. All files which have an upload
date after the date of that file will be processed.
<areanr> This is the area number which should be processed by PalmScan. By
default, PalmScan will process all file areas which have an
archive format configured.
+ The file-database maintenance for the Ezycom and RemoteAccess file-databases
can now also be run for a range of areas. The cmmandline option for this is:
/FDBmaint<areanr<-areanr>>
Examples:
/FDBmaint - Process all areas
/FDBmaint5 - Only process area 5
/FDBmaint10-20 - Process areas 10 to 20
+ The file-database maintenance can now be forced to process all files instead
of only files which haven't been processed before, with this commandline
option (besides /FDBMAINT...) :
/ALL
/ When running the file-database maintenance, file-specifications given on the
PalmScan commandline are now used for the file-database maintenance.
Example:
PalmScan /fdbmaint *.arj /all
- Will process all *.arj files which are in the file-database in areas
which have a destination archiver configured.
+ |The file-database support can now be temporary disabled with this
|commandline option:
| /NOFDB
+ |The files.bbs support can now be temporary disabled with this commandline
|option:
| /NOFILESBBS
/ The default extended descriptions character for FILES.BBS has changed to
none.
+ The log style is now configurable with these options at the LogFile keyword:
Compact - This is the style which was already being used (default) :
---------- Sat 01 Jan 94, PalmScan ...
$ 12:34:56 Local operation
Expanded :
$ 01-Jan 12:34:56 PSCN PalmScan ...
$ 01-Jan 12:34:56 PSCN Local operation
Example:
LogFile C:\Log\PalmScan.Log Expanded
- When only a filename (no path) was configured at the LogFile, PalmScan would
add the log of embedded processes to the parent archives. Now it will put
the log file in the same directory as where PalmScan.Exe is located.
+ Added the option to use different log files with different nodes. %N in the
log filename will be replaced by the node number PalmScan is running on
(which should be specified with the /N commandline parameter). Example:
LogFile c:\log\palm%n.log
+ |Added another option to the Touch keyword:
| Touch 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.
+ |Added a commandline option to override the configured destination archiver:
| /T[archiver]
|Example : /TARJ
|When no archiver is configured in the PalmScan configuration, and this
|commandline option is used, 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.
+ The minimum size for unpacked files which should be packed (PackUnpacked
keyword) can now be configured:
PackUnpackedSize [size]
The size must be given in bytes.
/ Changed the GIF pack routines. GIF packers which do not create a complete
new file but replace the original file (eg. GIFlite) can now also be used.
Also, when the 'packed' file is larger than the original file, PalmScan will
use the original file.
- The GIF (un)pack commands didn't accept commandline options, fixed.
/ Because some GIF pack utilities need both the original and destination
filename, these were not able to convert GIF files under PalmScan. PalmScan
will by default add the original filename and extension to the GIFpack
commandline. This is now configurable with these options on the GIFpack
keyword:
@FILENAME - Will be replaced by the original filename (without extension)
@EXT - Will be replaced by the original extension
Example:
CJPEG.EXE @FILENAME.@EXT @FILENAME.JPG
- will be replaced by: CJPEG.EXE 12345678.GIF 12345678.JPG
(when processing 12345678.GIF).
+ The message system has been completely rewritten. PalmScan now supports
these messagebase types:
- Fido (*.msg)
- Hudson
- Squish
- Ezycom (both 1.02 and 1.10)
- JAM
The configuration keyword for the message system is:
MessageArea [Type]<Number>[Path]
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
The keyword NetmailPath can still be used for a Fido style area.
Because of the large code size consumption, the message system has been
moved to an overlay file (PALMSCAN.OVR). If you don't use the message
system, the overlay file can be removed.
+ Added support for virus scanner reports. When a virus has been found, and
this feature has been enabled, PalmScan will include the report in the
message. To use this feature, @REPORT must be included on the virus scanner
commandline, along with the apropriate command for that program.
Examples:
McAfee Scan : /REPORT @REPORT
ThunderByte Scan : LOG LOGNAME=@REPORT
F-Prot : /REPORT=@REPORT
PalmScan will replace @REPORT with a filename for the report.
+ Added the option to scan embedded archives when a virus has already been
found in the archive which is being processed. The configuration keyword for
this option is:
CompleteScan
Normally, PalmScan will not process embedded archives when a virus has
already been found. This keyword enables the processing of those embedded
archives, which is especially useful when using the message system. PalmScan
will then create a complete overview of the infected files.
+ On the Scanner configuration keyword, up to 5 file specifications can
optionally be given. First, PalmScan will check the global file
specifications (on the VirusScan keyword). When there are files which comply
with those, the virus scanning will start. Before executing each virus
scanner, PalmScan will check the file specifications for those virus
scanners, and only execute them when there are no file specifications or
when there are files which comply with those specifications.
The Scanner keyword can now be used like this:
Scanner [name] [command] [lll] <[hhh] <[nnn] <filespecs>>>
When filespecs are being used, both the 'high' and 'nothing' errorlevels
must be used.
Example: VirusScan *.exe *.com *.ov? *.ans
Scanner TBscan TBSCAN_AF_NB_NM_BA_IN_NA_OLD_@SPECIAL 2 127 1 *.exe
*.com *.ov?
Scanner ANSItest ANSITEST_(whatever)_@SPECIAL x y z *.ans
In this example, TBscan will be executed when there executables and/or
overlay files, ANSItest will be executed when there are ANSI files.
- When escape was pressed to terminate the file processing, PalmScan will now
correctly exit when a listfile or the FileInfo system is used.
/ When the TempPath has not been configured, PalmScan will now use the TEMP
environment variable (when available).
+ Added a commandline option:
/DEBUG
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.
/ Changed some stuff in the PSetup interface:
- Cursor up/down will now go to the previous/next field;
- Empty space in edit fields is now shown in a different way when editing a
field;
- The menu and dialog borders have changed;
- Enter will now go to the next field on input fields and press a button
when that button is currently selected;
- F10 will close a window and keep the changes.
+ Added an alternate colorset to PSetup. Startup PSetup with commandline
option /A or -A to use this colorset.
+ Added a help system to PSetup. The help system uses PALMSCAN.DOC, which must
be placed in the same directory where PSETUP.EXE is located.
{EOF}