home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The World of Computer Software
/
World_Of_Computer_Software-02-387-Vol-3of3.iso
/
c
/
cn311-sw.zip
/
WHATSNEW.CN
< prev
Wrap
Text File
|
1991-11-19
|
5KB
|
102 lines
What's new in CircuitNet 3.10:
1: New Record formats for the mail packets. Packets are 15%
smaller than the same messages in v3.04's format.
2: Configuration/Installation has been greatly simplified.
CONFIGUR.EXE and CONFS.EXE have been combined into CONFIG.EXE,
with added capabilities for configuring net-mail related functions
in Spitfire as well. Message conferences can be added and
deleted and completely configured for netmail using only
CONFIG.EXE.
3: CircuitNet now uses a parallel conference configuration file
that matches the SpitFire SFMCONF.DAT file record for record.
This gives CircuitNet the capability to expand with Spitfire
and match same conference limits as Spitfire.
4: Improved routing. CircuitNet now uses a text file called
CNROUTES.LST to control what packet a routed message is
included in. Routed messages are now only included in packets
that are in the path to the destination. The routing list is
created and maintained by IMPORT.EXE.
4a: WildCard Routing: Multiple destination nodes can be specified
for routed messages using standard DOS wildcard formats.
(* and ?)
5: Name swapping on outgoing and incoming messages is no longer
case sensitive. The "Sysop <NodeID>" format has been extended
to accept wildcard Node Id's, and the special format "Sysop
All". Such messages are now displayed as "carbon copies" of
messages TO: the original name that was swapped from. (i.e.
TO: Sysop, Carbon copy of message TO: Sysop All) "Sysop
<node>" format messages are treated as routed messages by
Import, and NOT imported into nodes that do not match the
<node> designation.
6: Improved Duplicate rejection: Duplicate rejection is now based
on History information maintained in SFMSGxxx.HST files for
each conference. The number of history records to maintain for
each conference is configurable from 512 to 2048. CircuitNet
establishes a unique message number for each message, and
duplicate rejection and threading are based on the recorded
history kept in the .HST files.
6b: Extract maintains up to 30 days history for each node serviced,
and will send a message with the same number once every 30
days.
7: NetWork wide threading is now supported. Provided some portion
of the thread is represented in the history file then linking of
threads is maintained accurately throughout the network.
(assuming the Spitfire messages haven't been renumbered by a
message packing utility. In which case the Various thread
elements would be threaded to the wrong thread start.)
8: Speed has been substantially increased over version 3.04 in all modules
except PRIMER.EXE. Added features in Primer have offset any speed gains
resulting from the new data formats.
9: Orphan Message Recovery: Any message which
a) is addressed to the sysop (or a name that will convert to
SysopUserName).
AND
b) would otherwise not be imported because the conference
isn't found; Will be marked as an orphan message, and
imported into SFMSG01.*.
10: MailCall V3.10 is now an integral part of the package, as
version 1.0 cannot use the new CIRCUIT.CFG record.
11: Status Reporting: Import, Primer, and Extract will as a minimum,
enter a private "Comment to the Sysop" in conference #1 with the
start time, stop time, and number of messages processed. The Status
report will thread continuation messages to the original if 91 lines
are exceeded.
12: Variable logging levels: Import, Primer, and Extract, will
accept command line parameters of NOLOG, BRIEF, and VERBOSE to
set logging levels.
NOLOG is the minimum level of logging, and produces a minimal
status report. No entries are made to the Activity Log.
Entries to the Error Log are the minimum information to identify
the error, and the source.
BRIEF is the default setting. Conference totals are given in
the status report, and copies are written to the Activity Log.
Error logging is unaffected. Status information for Extract
doesn't change, but is included in the Activity Log as well as
the Status Report.
VERBOSE is virtually the same as the current logging, with the
TO:, FROM:, SUBJECT, ORIGIN: and VIA: information for each
message written to the Activity log. Error information
written to the ErrorLog is expanded to include more
information on the errors.