home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 2 BBS
/
02-BBS.zip
/
flm140.zip
/
Whatsnew.Txt
< prev
Wrap
Text File
|
1996-12-08
|
22KB
|
516 lines
FLM
Changes and Additions
1.40 Dec 08 1996
- Divisions containing no listable areas are not reported
in the output lists anymore.
- Lines of FILES.BBS starting with control characters are
not deleted anymore.
- Please note that the RAR "Extract" entry in Compress.Cfg
may require the -y and -std switches to avoid that RAR
asks for user input while invoked by FLM !
- If the FILES.BBS does not exist and Adopt is enabled on
the area, FLM now creates the FILES.BBS instead of
skipping the area.
- New statement for setting the maximum message size:
MsgSize <bytes>
- New statement for allowing "<path>\" entries in the
okfile:
default: "<path>\*.*"
OkDirsOnly: "<path>"
OkDirsSlash: "<path>\"
- New statement for announcing _all_ adopted files,
regardless of their file dates.
AdoptAnnounce
- New command line switch for multiple announce periods:
-a[n] 0 <= n <= 9.
FLM keeps 10 different "last-exec" dates for
announcements (you may want to use '-a0' for daily
announcements, '-a1' for weekly ones and so on.
Examples:
-a Do NOT announce
-a0 Announce files newer than last-exec date 0
-a9 Announce files newer than last-exec date 9
- New statement to assure UpperCase adoptions:
AdoptUpperCase
- FLM had problems in deleting old FILE_ID.DIZ files with
Hidden, System or Read-Only attributes when extracting a
new one while adopting files; fixed.
1.37 Aug 20 1996
- When MultiLineDesc was not used, the descriptions
imported from FILE_ID.DIZ (for adopted files) had the
continuation lines starting at column 79. Fixed.
1.36 Aug 15 1996
- FILES.BBS lines starting with an HighAscii (>127)
character in the first column are now taken as comments.
- New statements to kill Orphans (files that do not have a
files.bbs entry): KillOrphans, NoKillOrphans,
KillOrphansExclude.
- New statement "OkDirsOnly" to list paths in the OkFile
with no trailing "\*.*".
- New CompressCfg statement to allow extraction of
FILE_ID.DIZ for orphan adoption.
- New DescStart statement to allow a description prefix
(e.g. download counter) for adopted files.
- Adopted files are now immediately reported and
announced, if new.
Previously they were not reported until next run of
FLM.
1.35 May 31 1996
- Support for multiple NewHeader, AllHeader, OkHeader,
MagicFile specifications.
Multiple statements and multiple arguments are allowed.
- New "AnnExclude <filespec> ..." statement, to exclude
specified files from the announcements.
This statement can be used both in the global
announcement section and inside each "AreaTag/AreaPath"
block.
- Fixed problem with AreaTag when the corresponding area
does not have anything after the path in Squish.Cfg
(might happen for *.MSG netmails).
- New FLM.ICO
- New NT version.
1.34 March 3 1996
- A nasty bug has been fixed: if RemMis is not used, the
presence of a comment line at the head of the files.bbs
of the first area causes an access violation in v 1.33.
Sorry...
1.33 March 1 1996
- OS/2: Magics on HPFS are resolved using the upload
(creation) date.
- If the file description contains high ascii codes
(>127), the announcements will now contain remapped
plain-ASCII characters.
- You can allow High Ascii characters in some (or even
all) areas by the use of the "HighAsciiOk" statement in
the global or local-override announcement sections.
- New (global) statement: UniqueDmpLine.
Makes FLM generate FILES.DMP filebase files with
descriptions on one line only (multiple lines are
concatenated).
By default, FLM outputs multi-line descriptions without
changes to FILES.DMP: when using L)ocate and N)ewfiles
commands, Maximus will respect the original formatting,
but the continuation lines will be aligned to the left.
When this statement is used, the original formatting of
descriptions is lost (in the filebase) but Maximus will
be able to word-wrap and align when executing L)ocate or
N)ewfiles commands.
- New (global) "AreaExclude <WTAG> ..." statement.
The specified areas are completely excluded from
processing.
1.32 Restricted Beta
- OS/2: Problem with remote (LAN) directories fixed.
The C stat function had problems: substituted with
direct OS/2 API calls.
- New statement: MultiLineDesc <nnn> [<c>]
By default, files.bbs description must be on a single
line; this statement enables Multi-Line support.
<nnn> is the number of spaces that must precede the
continuation lines.
<c> is the continuation character.
If <c> is NOT specified, it is assumed that the
continuation lines must be preceded by <nnn> spaces.
If <c> IS specified, it is assumed that the continuation
lines must be preceded by <nnn> spaces, the <c>
character and one more space.
For example, when the 2nd and following description
lines in files.bbs start at the 32nd column, use:
MultiLineDesc 31
A description in files.bbs would be like:
Test.Zip This is the first description line
this is the 2nd line
this is the 3rd line
^ ^^
1 31 32
When the continuation lines are preceded by a '|'
character, use:
MultiLineDesc 29 |
A description in files.bbs would be like:
Test.Zip This is the first description line
| this is the 2nd line
| this is the 3rd line
^ ^ ^
1 29 32
1.31
- ATTENTION: this version is for Maximus 3.xx ONLY.
Support for Maximus 2.xx has been dropped.
- Added support for "DateAuto"/"DateList"/"DateManual"
options (filearea.ctl) and "File Date Manual"/"File Date
Automatic" (max.ctl). Previously automatic dating was
assumed.
- "Adopt" and "Remmis" are automatically disabled in
"DateManual" and "DateList" areas.
- Areas that are offline can still be listed if they are
"DateList" and the "FileList" is on-line. In this case
"Offl" is written in the output lists before the area
description (just below "Area:").
- Support for path specification in the files.bbs.
e.g. "d:\file\test\test.zip This is a test" is a valid
files.bbs entry.
- Specification in "FileList" (filearea.ctl) of a file
list with an extension different from ".BBS" is now
allowed.
- OS/2 HPFS: ATTENTION: New files are now recognized by
the "creation" date, while they are listed with their
"last write" date, to be consistent with maximus 3.00.
- Added support for the "MAXIMUS" environment variable.
The "MaxPrm" cfg statement remains as an override.
- Added semaphore for mutual exclusive write-access to the
filebase by ApWorks programs.
- Fixed bug that did not exclude the "special" tags
beginning with '<' from the "*" wildcard.
- Fixed bug that caused echo tags of "AreaTag <Tag> <Path>
[-$]" not to be logged to echotoss.log when the <Path>
was specified.
1.30
- New dos 32 bit version, 16 bit one has been dropped.
Dos extender (DOS4GW.EXE) required.
- Since the dash '-' is a legal filename character,
files.bbs lines beginning with '-' are now considered
comments only if the '-' is followed by a space "- ".
- The files.bbs flags /t and /b are not reported to the
file lists anymore.
- Internal support for maximus filebase added. Now you can
make FLM compile the filebase while it is generating the
file lists: no more need for running the external
FB/FBP.
- When you use the "OkMaxFiles" statement, FLM
automatically generates both MaxFiles.Idx and
UniFiles.Idx (which is like MaxFiles.Idx with duplicate
files removed). Then an entry is added in the OkFile so
that your Binkley-style mailer uses the UniFiles.Idx
index for file-requests.
- If you do not want the UniFiles.Idx entry in your Okfile
but still want to compile the filebase, you can use the
"FBCompile" statement (global section). This statement
is automatically assumed (and thus redundant) whenever
you have at least one "OkMaxFiles" statement in you
configuration file.
- Announcements for new files implemented, please see the
documentation.
- When compiling the filebase ("OkMaxFiles" or "FBCompile"
used), FLM can optionally report duplicates: use the
<DUPES> tag in some defined announcement message area
(usually the local (co)SysOp area or netmail to the
SysOp).
- New cfg statements (global): "NoAnnDupeTag <WTag> ..."
and "NoAnnDupePath <PartPath> ..." to avoid excessive
dupe announcements. In the case you have lots of dupes
you do not want announced (e.g. on CDROMs), you can
exclude areas (NoAnnDupeTag) or paths (NoAnnDupePath).
<WTag> is a tag specification with optional '*'
wildcard.
<PartPath> is a partial path specification: all the
dupes that have a path beginning with <PartPath> will
not be announced. Please be aware that you could have
the announcement of a single file as "dupe" if it is not
excluded while its corresponding duplicate is.
Example:
NoAnnDupeTag 1!apw* GFX*
NoAnnDupePath d:\bbstest\file\1!apb g: h:
- New cfg statement: "AreaTag <Tag> [<path> [-$]]". You
can now define your announcement areas starting with the
"AreaTag" statement in the place of the "AreaPath" one.
FLM will look-up the <Tag> in Squish.Cfg to find the
corresponding path, type and primary address.
If you specify the optional <path> and type, no look-up
is done in SquishCfg (see "SquishCfg" statement below).
- New cfg statement (global): "SquishCfg <filename>". It
is used to specify the squish configuration file, so
that FLM can automatically get the path, type (SDM vs
Squish) and primary address for the announcement areas
defined with the "AreaTag" statement.
When SquishCfg is defined, if you use "AreaTag <Tag>" to
define announcement areas, the "FromNode <adr>"
statement is only used to override the primary address
specified for that area in Squish.Cfg (including the
-p<adr> overrides).
FLM supports the "Include" keyword of Squish.Cfg: just
be sure to always use the full pathname in the Include
statement if FLM and Squish run from different paths.
Both echomail and netmail areas are recognized by their
Squish tags.
Netmail areas will have the Private attribute and no
origin by default. Local overrides are still possible
through local "Origin" and "Attr" statements.
- New cfg statement: "EchoTossLog <filename>". It is used
to override the specification found in the Maximus
control file, that FLM gets from Max.Prm. When FLM
writes echomail messages in areas defined with the
"AreaTag" statement, the corresponding echomail tags are
appended to this file, one per line.
If you do not like this output, you can override with
the NUL name: "EchoTossLog NUL".
- "Adopt" and "RemMis" are automatically disabled in areas
where Files.Bbs is Read-Only (e.g. CDROMS with no
separate files.bbs specified via the "FileList"
statement in Maximus cfg).
- New "special" tag "<CDROM>" can be used to disable
"Adopt" and "RemMis" in all the CDROM areas; e.g.:
Adopt *
NoAdopt <CDROM>
RemMis *
NoRemMis <CDROM>
- New cfg statement (global): "Files <num>" to increase
the number of files that can be open at the same time.
The Operating System allows 20 files per process by
default, including the 5 "standard" ones. If you need
FLM to open many files, you might need to increase this
limit. When you use this statement (with <num> > 20),
FLM reports both on screen and to the logs the exact
total number of files that can be open at the same time
(should not be less than <num>).
E.g.: "Files 50"
DOS: WARNING: You need to specify a "Files=<num>"
statement in your config.sys also. The "Files <num>"
specification in FLM.cfg does not allow FLM to use more
files than specified in the "Files=<num>" statement in
your config.sys.
E.g.: "Files=50"
- Password Protected Magics now supported.
Example for Magic.Lst:
Magic1 c:\file\file1???.zip
Magic2 c:\file\file2???.zip pwd1
The second item is protected.
FLM will write to the okfile the resolved magics; e.g:
@Magic1 c:\file\file1999.zip
@Magic2 !pwd1 c:\file\file2888.zip
- Summaries added at the end of the lists.
- New cfg statement (global): "DateFormat USA|EURO|JAPAN"
to set the date format to mm-dd-yy, dd-mm-yy, yy-mm-dd
respectively. e.g.:
DateFormat EURO
- FILES.* and *.BBS are now automatically excluded from
Adoption (no need to list them in "AdoptExclude").
- New cfg statements: "AllFilesCmd <cmd>" and "NewFilesCmd
<cmd>" to allow easy integration in FLM.CFG of the
commands related to FLM that must be executed after the
generation of the file lists is complete (till now you
had to put them in the calling batch file).
If the command does not begin with the name of an
executable file, the default command interpreter is
invoked. The "%f" parameter can be used to represent
the name of the file (as specified in the AllFiles and
NewFiles statements respectively).
In case of multiple commands, you can invoke a batch
file (.CMD (OS/2) or .BAT (DOS)) or use multiple
"AllFilesCmd" and "NewFilesCmd": they will be executed
in sequence.
Note: Usually you will like creating the file lists in a
place different from the destination file area,
otherwise the file list will show a "0 length" file-list
file, since it is "under construction" while FLM
examines the area.
Example:
The commands in the following example are for 4OS2
(trademark of JP Software): if you do not use this
excellent command interpreter you would need a slightly
different syntax.
NewFiles \file\ApWorks.new
NewFilesCmd *move %f \file\1!apwork\
AllFiles \file\ApWorks.All
AllFilesCmd copy %f \file\1!apwork\
AllFilesCmd zip -mj \file\ApWorks %f
AllFilesCmd *move \file\ApWorks.zip \file\1!apwork\
1.24
- First OS/2 version
- Now the global WrapCol setting can be overriden by local
use of the same WrapCol keyword. The local WrapCol can
be used even if you do not use a global one.
- New optional parameter for WrapCol (right margin). Now
the "WrapCol [<num> [<num>]]" syntax allows to specify
both the left and right margin for long word wrapped
descriptions.
- New "AdoptExclude <filespec> ..." keyword (global) to
exclude some files from adoption (wildcards in filespec
follow the OS/2 behaviour).
- Whenever a file name must be specified, it can be
included in ", following the OS/2 rules. e.g. "flm
123.cfg" is a valid filename (the " are necessary due to
the blank char).
1.23
- Areas not listed in any output file are NOT read: this
way you do not loose time scanning CDROM areas when you
do not include them in any list. Always remember to
exclude CDROM area from adoption (Adopt) and missing
removal (RemMis).
- File description can be word wrapped: see WrapCol in
Flm.cfg.
1.22
- When a file was listed in files.bbs but had no
description, its line was erroneously handled as a
comment; fixed.
1.21
- Fixed bug (area inclusion/exclusion worked as if all
area specifications were terminated by '*').
1.20
- Added multiple listing capability, Area
inclusion/exclusion, Maxfiles.idx okfile support.
1.10
- Added AREA.NDX ordering and missing exclusion.
1.00
- First version, list only.