Dec 212017
 
Latest Version Of QBBS's QEcho, MailToss and QLink programs.
File QNET_262.ZIP from The Programmer’s Corner in
Category BBS Files
Latest Version Of QBBS’s QEcho, MailToss and QLink programs.
File Name File Size Zip Size Zip Type
CHANGES.DOC 8885 3447 deflated
MAILSCAN.EXE 22720 12362 deflated
MAILTOSS.EXE 26192 13793 deflated
QECHO.EXE 69568 30659 deflated

Download File QNET_262.ZIP Here

Contents of the CHANGES.DOC file


**WARNING****WARNING****WARNING****WARNING****WARNING****WARNING****WARNING**


MAKE BACKUP COPIES OF YOUR CURRENT RELEASE VERSIONS OF THE QUICKBBS
MAIL UTILITIES! THIS STUFF MAY CAUSE HAIR LOSS, CURL YOUR SPINE, OR
LOSE THE WAR FOR THE ALLIES! YOU'VE BEEN WARNED.


Changes for QuickBBS 2.62 Utilities

MAILSCAN -

1. The dreaded date bug has been terminated with extreme prejudice.
(I've always wanted to say that)

2. Complete zone awareness is now in mailscan. If you send a
netmail message to a zone other than the zone defined as your primary
zone, a ^AINTL line is generated, reflecting the correct destination
zone, and uses your primary zone as the originating zone. This
causes OMMM to put the message in the appropriate outbound directory.
This should also work for other packers also. Please let us know if
it does not, so we can contact the author of that software!

3. A file called NETMAIL.BBS is generated when netmail is entered
from within the BBS. This is a file of word, and contains the record
numbers of the netmail messages entered. This is used a starting
point when scanning for outbound netmail. The code we got was not
utilizing this file at all. It makes quite a difference in speed,
especially when you have a lot of messages online.

Changes in 2.61e (Beta)

4. Added complete error trapping, as in QUICKBBS.EXE. This will
create/append ERRORS.LOG as necessary, giving time, date, error
message, and program that generated the error.

5. There was a bug in updating the user credit, where MAILSCAN
would generate a runtime error 100. The mail was extracted ok, just
that the user credit never got updated. That's history.

Changes in 2.61f (Beta)

6. Doesn't do direct screen writes anymore. No reason to configure
this, as there's not that much displayed anyway.


Changes in 2.62 (Release)

7. Mailscan will not work with RemoteAccess, unless you are a registered
user of QuickBBS. I didn't do all this work on this program, so
someone could use it with RA. After all, I don't work for them!


MAILTOSS -


1. Would only work with 50 or less message boards, fixed.

2. Zone support was also added here. If a ^AINTL line is found,
then mailscan reads it for determining originating, AND receiving
zone for that particular message. If none is found, then the zone
specified in config.bbs is used as the origin & receiving zone.

Changes in 2.61d (Beta)

3. Added complete error trapping, as in QUICKBBS.EXE. This will
create/append ERRORS.LOG as necessary, giving time, date, error
message, and program that generated the error.

Changes in 2.61e (Beta)

4. Doesn't do direct screen writes anymore. No reason to configure
this, as there's not that much displayed anyway.

Changes in 2.61f (Beta)

5. Closed StdOut in the wrong place, causing a runtime error 105.
This is now fixed. No real big deal, but one info message would get
lost in limbo.

Changes in 2.62 (Release)

6. Mailtoss will not work with RemoteAccess, unless you are a
registered user of QuickBBS. I didn't do all this work on this
program, so someone could use it with RA. After all, I don't work for
them!



QECHO -

1. Short packets, resulting in bizarre results - SWATTED! This
required us to add nulls on to the end of Qecho packets.

2. Dreaded date bug fixed. Exact same code (and problem) as
MAILSCAN. Replaced this with pop-in routine generic to QECHO &
MAILSCAN.

3. The private bit is not stripped of off echomail anymore. If you
have an echo area allowing private echomail, it will get sent that way.

4. Adjusted memory allocation, which was causing problems executing
certain UNARCCOMMAND's. (SPAZ, I think), and some ARCCOMMAND's.

5. ARCCOMMAND is now obsolete. This has been replaced by two
commands, PACKERS & ENDPACKERS. These two command are used thusly:

; Qecho.CTL extract
;
PACKERS
375/1 pkzip/aex
375/11 zoo -a
375/12 pak a
375/32 lharc a /m
ENDPACKERS
;

Simply put a node number, and a commandline for your favorite file
compression utility. If the PACKERS..ENDPACKERS section is not found
then PKPAK -OCT -A is used as a default archiver. This is also the case
if a node is not listed in the PACKERS section of the control file. This
function has been tested with PKPAK, PKZIP, LHARC , PAK, and ZOO. If
you use OMMM, then you need ZZAPPL, which is called by OMMM, and
functions exactly like this section of the QECHO.CTL file.

PKPAK was chosen as the default for several reasons. Mostly, because
it's faster than spit on teflon at making .ARC's. With the -OCT switch,
PKPAK makes ARC compatible archives (i.e., no squashing), which is the
FidoNet standard for compressed mail. You must have PKPAK in your path.

6. UNARCCOMMAND is now history. Qecho reads the compressed mail
file and calls the appropriate un-compressor. Qecho understands these
formats:


.ARC - Calls PKUNPAK
.ZIP - Calls PKUNZIP
.PAK - Calls PAK
.ZOO - Calls ZOO
.LZH - Calls LHARC

The extensions denoted represent the format used for compression - the
actual filename will obviously be different. I was going to put in
DWC, but couldn't find a copy to test with. Does anyone really use
that anyway??? The appropriate un-compressor must be in your path!

Changes in 2.61f (Beta)

7. Had reports of Qecho choking if an echo message had a lowercase
AREA: tag. This is fixed - now it don't care upper from lower.

8. Tightened up a loophole in the uncompression file checking. There
were instances when Qecho would think a PAK file was an ARC file. Not
no more!

Changes in 2.61g (Beta)

9. Added complete error trapping, as in QUICKBBS.EXE. This will
create/append ERRORS.LOG as necessary, giving time, date, error
message, and program that generated the error.

Changes in 2.61h (Beta)

10. Qecho will now recognize mail archives with extensions of *.??0 -
*.??Z. It will not create archives with names higher than *.??9, as
this is not in FTSC specs. Recognizing the "A" - "Z" on the extension
is so that mail from some other packers will be unpacked.

11. Doesn't do direct screen writes anymore. No reason to configure
this, as there's not that much displayed anyway.


Changes in 2.61i (Beta)

12. Qecho now adds it's own tearline when exporting messages.


Changes in 2.61j (Beta)

13. New parameter added. If a -j is passed to Qecho, the program
swaps itself to EMS, if available, or disk (in that order), to allow
more room for the archiver or unarchiver to run. This should help out
the DoubleDos/Desqview folks to squeeze the BBS partition down a
little smaller. From testing here, it appears that about 200K is all
you need. This is about the minimum for PKZIP to run.

14. The *.??9/*.??0 rollover problem has been corrected, and Qecho no
longer deletes the mail archive.

15. Command help screen has been added. If Qecho is passed a -?, a
help screen will be displayed.

Changes in 2.61k (Beta)

16. Found a bug in the outbound archiving swap code. Qecho would
swap the first time ok, but successive swaps would fail. This is
fixed.

17. In nuking the 9/0 rollover Qecho doesn't delete the .pkt file
after adding it to the archive. This is fixed, Qecho now deletes the
.PKT files after making the compressed mail file.

Changes in 2.61-l (Beta)

18. Qecho now deletes the mail packets after archiving. You can use
your archiver's move option, or add. Qecho will handle it either way.

19. You can pass Qecho a drive to create the swap file on. Simply
add the drive letter after the -j. For example, to swap to my
extended memory ramdrive f:, I would use:

Qecho -p -e -a -jf: (colon optional)

In testing here, the swap file is about 160K or so, so make sure you
have enough room on whatever drive you specify.

Changes in 2.61-m (Beta)

20. Had an extra LF in my tearline, which caused ZMAILQ to choke, and
append on another origin line. I removed my extra LF, but Claude
should be a little less picky.

Changes in 2.62 (Release)

21. Removed the Tearline. I can't count all the heartburn I've
gotten over this one. Multiple tears are kind yucky, but so is
removing the QuickBBS tearline. I removed mine.

22. Qecho will not work with RemoteAccess, unless you are a
registered user of QuickBBS. I didn't do all this work on this
program, so someone could use it with RA. After all, I don't work for
them!


 December 21, 2017  Add comments

Leave a Reply