home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Boston 2
/
boston-2.iso
/
DOS
/
HILFEN
/
MODEM
/
SALES
/
MISC.XXX
/
TX2MB220.ZIP
/
CHANGES.210
< prev
next >
Wrap
Text File
|
1991-03-10
|
7KB
|
131 lines
┌─────────────────────────────────────────────────────────────────────────────┐
│ TXT2MSG - Textfile to PCBoard 14.x Messagebase Utility │
│-----------------------------------------------------------------------------│
│ CHANGES.ver - function and documentation changes since last release │
│ Revision changes are in reverse order, ie, newest changes are at the top. │
└─────────────────────────────────────────────────────────────────────────────┘
Ver Date, notes, changes
------- ----------------------------------------------------------------------
2.10 Tue 01-08-1991 *Release*
General release of 2.10 w/SQ2MSG support.
I have NOT limited any features or functions for this release. If you
enjoy getting the fully functional shareware to test out, please
express yourself by registering TXT2MSG! You're getting TWO programs
in one (TXT2MSG and SQ2MSG).
As always, if you can come up with a function not implemented, let me
know and I'll see about adding it. Also, pass on your batch files so
other Sysops can benefit from your ideas.
------- ----------------------------------------------------------------------
2.10f Mon 01-07-1991 *Beta*
Fix SQ2MSG processing dealing with PCBverify generated ANSWERx files.
The blank line at the beginning of the ANSWERx file caused TXT2MSG to
enter a single empty (blank) message before processing the other
script answers. No harm but annoying to get an empty message.
------- ----------------------------------------------------------------------
2.10e Tue 01-08-1991 *Alpha*
Added SQ2MSG processing! Now there is no longer a need for the
seperate utility SQ2MSG as it's functions are built into TXT2MSG!
SQ2MSG, which perhaps gets wider use than TXT2MSG, allows you to take
users' script questionnaire ANSWERx files and insert them as messages
for your review. Optionally, you may include the users' callers logs
entries on the end for verification of reading bulletins, etc!
To use SQ2MSG processing: Specify the ANSWERx file to process with
the -q switch (-qd:\dir\filename). Only one ANSWERx file can be
processed at a time so you may need multiple calls to TXT2MSG to
process all your ANSWERx files. This operation has been verified to
work with PCBverify generated logs as well.
ALL other files specified (excepting the conference file of course)
are considered callers logs. IF any callers logs are specified, they
will be scanned for callers log entries from the user answering the
script. These log entries will be appended to the message generated.
The -n (no header modifications) switch is assumed when -q is
specified.
The -f (from username) switch is disabled during SQ2MSG processing
since the messages will be addressed from the user completing the
script questionnaire.
All other switches are active. Be careful! TXT2MSG defaults to
PUBLIC messages addressed to ALL -- having folks script answers
entered as a public message unintentionally might piss off some new
users!
I recommend that you always use the -r (R/O, to Sysop) switch when
dealing with SQ2MSG processing. In some cases you might want the
answers to be public (such as when asking for access to a private or
adult type conference, in that conference for others to review and
vote on) but not often.
------- ----------------------------------------------------------------------
2.10c Wed 12-05-1990 *Alpha*
Working version number change. Because of the new conference number
support feature just added, TXT2MSG takes on a new ability and a new
version number.
If you have RNETCONF, CONFINFO, or CNAMES environment variables
specified, you may use a conference number in place of the conference
messagebase. TXT2MSG will search RNETCONF, then CONFINFO, then CNAMES
trying to lookup the messagebase file specification. CNAMES is an
uncommon environment variable so I should explain that one: Set this
environment variable to the reflect the drive\directory\name of your
CNAMES file. Do NOT include a period or extension on the filename.
RNETCONF is as per the RNet specification rules. CONFINFO is the
complete specification for your ProDoor CONFINFO file.
Examples:
SET RNETCONF=d:\rnet\rnetconf
SET CONFINFO=d:\prod\confinfo
SET CNAMES=d:\pcb\main\cnames
You must be running a later version of PCBoard (14.2+) which produces
a CNAMES.$$$ file for TXT2MSG to read. If you are using an earlier
version of PCBoard 14.x, you will need to use RNETCONF or CONFINFO.
The new conference number support makes the PROUMAIL.BAT example
batchfile easier to read and maintain. It also allows you to rename
or move conferences without having to worry about chasing down those
batchfiles with TXT2MSG in them (though, you'll have to do that
initially to change to conference numbers from files... but it's not
needed).
Increased max_files from 100 to 250. Ed Hopper was running into the
100 file processing limit.
------- ----------------------------------------------------------------------
2.02b Tue 12-04-1990 *Alpha*
Fixed blank line compression; was not working if the -n (no text
header control/mods allowed) switch was in effect.
Added DATE: and TIME: keywords to textfile parsing. Only minor
checking is done as to the validity of the commands. Usage is:
DATE: MM-DD-YY
TIME: HH:MM (may be longer, will only take first 5)
Corrected a bug where TX2 would stop reading text from a file when it
encountered a bad header (such as no name following TO:). TXT2 will
now simply do what it can to recover and continue.
Corrected bug where multiple message textfiles over 10 messages long
were only showing "0-9" for the message number. Will now correctly
show message numbers from "0-99" for a single given textfile (that's a
9500 line message!)
------------------------------------------------------------------------------