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
/
CHANGES.311
next >
Wrap
Text File
|
1992-02-15
|
5KB
|
120 lines
2-15-92 4:02:57 pm What's new in CircuitNet v3.11
1: IMPORT.EXE -- Bug that blocked messages to "Sysop" as a logon
name has been fixed.
2: IMPORT.EXE -- Remote conference deletion re-written. See Errata
section below.
3: IMPORT.EXE -- Corrected date format on imported messages
corrected to conform to Spitfire's date/time format. (Replaced '/'
with '-' in the date string.)
4: CONFIG.EXE -- Corrected typo in message conferences menu to
properly reflect the LAST conference as the one to be deleted.
5: PRIMER.EXE -- Fixed bug in parsing of remote delete command
format. Most incidental spaces are now ignored.
6: PRIMER.EXE -- Primer now strips routing and conference delete
commands from the Subject field of outgoing routed messages. This
was done to eliminate the problem of replies to routed messages not
being sent because the route in the subject was not changed.
Replies to routed messages will now default to unrouted messages if
the subject is not changed.
7: EXTRACT.EXE -- Corrected ommision of outbound duplicate
rejection in v3.10 release.
8: ALL MODULES -- Corrected DATE/TIME formatting error in Status
Report messages.
9: ALL MODULES -- Changed Status Report messages to conform to
SpitFire's Comment to the Sysop form.
ERRATA (Errors in the documentation file.)
1: All references to .PTO, .DTO, and .?TO ciles should be changed
to .CNP, .CND, and .CN? respectively.
2: The section on Remote Dossier Adjustments was not updated from
the v3.04 specifications. Replace with the following text:
REMOTE DOSSIER ADJUSTMENT
Adding a conference: Adding a conference simply requires sending a
routed message IN that conference. Assign the desired codename to a
Spitfire Conference, and then enter a routed message in that
conference to be sent net-mail. Route the message to any node you
know already echoes that conference. (Usually routing to your host
is sufficient.) Address the message TO: Sysop <NodeId> of the node
you route the message to. WildCard routing and Sysop specifiers are
permissible. The desired conference will be added to ALL dossier
files required for you to echo the conference between your node and
the node the message is routed to.
Deleting a conference: Remote deletion of conferences is more
tightly restricted.
1: You can only delete conferences from the Dossier file for YOUR
node on systems you echo directly to. You CANNOT delete conferences
in nodes you do not build packets for.
2: The message must be FROM: the name given as Sysop User Name in
Config. A message from any other name will produce an error message
from Primer in both the Activity and Error log files alerting you to
an "Unauthorized attempt to delete a conference", and the message
will NOT be processed. The warning message will be repeated each
time primer is run until the offending message is deleted, or until
the Sysop User Name is changed to match the From: field in the
message.
3: The Subject: filed must contain a routing specifier AND a
deletion command. non-routed attempts to delete a message will be
processed as a normal message and sent into the network, but will
have NO effect on the dossier files. (i.e. SUBJ: >>MYHOST--BANANAS)
4: The last character of the codename to delete must be followed by
a space, or be the last character in the subject. Imbedded spaces
are ignored. any text following the '>>' marker, (including the
marker), will be removed once Primer parses the information so any
text following the codename will be lost.
5: On the recieving end, the name of the Dossier file to modify
must match the node ID of the true origin of the message. In other
words, you cannot modify any dossier file except the one for YOUR
node on a system that builds packets FOR you. (i.e. your host, or a
direct dependent of your node.)
NOTE: All traffic in the conference must cease, or the automatic
update feature of IMPORT will re-add the conference. All message in
the packet containing the deletion command will Import normally
before the deletion is made, so the command can delete the
conference it is sent in, but it must be manually removed from the
affected dossier file on your end. (After the delete command is sent
if it is in the affected conference. Any time if in another
conference.)
Please address any questions to:
Harold Niemi
2039 Civic Center Drive
Suite 125
No. Las Vegas, NV 89030-6399
PHONE (702) 649-0156
OR
Via CircuitNet International network (Node ID: 702399)
OR
A comment to Sysop on:
The Wizard's MailBag BBS
(702) 399-8558 (9600 v.42)