-=> Quoting James Bradley to Nancy Backus on 20 Jan 09  02:25:10 <=-

 JB>> My guy will not put in the fudged door, as it can't be endorsed by the
 JB>> author. /-:
 NB>> That is his choice...

 JB> He pays the phone bill. I'm sorta sticking to Multimail here, but if
 JB> the door was there, I'd be *very* tempted to use a DOS emulation
 JB> program to run BW. 

You do realize, don't you, that BW will read any packets that are in
either QWK or BW format?  You just don't get ALL the bells and whistles
with a QWK packet that you would for a BW one... but for normal
messaging there isn't really a lot of difference between the two.  The
biggest difference that I pay any attention to is that the subject line
is limited in a QWK packet, where it isn't in BW.  But that is really a
minor issue most of the time... :)

 NB>> That's never happened to me.  Odd that...  Only time I knew that adding
 NB>> or subtracting an echo would affect where the messages get shuffled was
 NB>> when the sysop did so, and the areas got different numbers...  The QWK
 NB>> packet areas depend on the numbers, not the echotags, quite often
 NB>> anyway...  If the numbers didn't change in the door, it shouldn't have
 NB>> affected your upload, even if you added or subtracted which available
 NB>> echoes you were going to d/l...  Were you perhaps adding an area that
 NB>> was new to the bbs?  That could have been a coincidental change of
 NB>> numbers there that then affected your u/l...

 JB> Ah... That would make more sense than the nonsense I was trying to
 JB> attach to it. I just forget how Maximus handles those things, but I
 JB> recall some new echoes going in around that same time.
 
I've run into my scenario often enough...  One learns to be careful and
watchful... :)  Sometimes the sysop will alert you to the area #'s
change, which is always helpful...  :)

 NB>> I only have used the offline area tagging occasionally... Usually I do
 NB>> it when I'm in the door... especially if I think I might have to adjust
 NB>> how many messages there for the first d/l... :)

 JB> Then it occurred to me how much I was using the last read pointer
 JB> setting, and how much I missed that when I was blowing up mail packets
 JB> last year. 

There are ways to fix the last-read pointers in most doors... not in
all... and some are easier than others...  In Wildcat QWK, it's
possible, but a little convoluted...  I've had some that supposedly had
multiple ways of doing it, and to the best of my ability I couldn't make
a one of them work!  ;)

 JB> The access to netmail is also sorely lacking here. I had BW add a
 JB> custom header, that added the extra address line for my mail to be
 JB> forwarded to a "soupgate", that sent it off to my email address.
 JB> Multimail treats the netmail area as if it was just another echo, so an
 JB> additional "To: " line has to be added for the
recipient's address, and
 JB> if I want to use soup, I need two of those lines to tell soup where to
 JB> send it. 

I'm not using it lately for net- or e-mail, but when I was, I used that
feature in BW packets, too... and missed it when I had to use the "top
of the message" methods for QWK-type messages... different for each type
of BBS software, too...  :(

 JB>> ... I'm not totally worthless. I can serve as a bad example!
 NB>> Ah, yes...  there's a number of us around...  

 JB> I'm in good company. <-;

Indeed.  ;)

ttyl      neb

... Fortune cookie slip:  Learn Chinese: expensive    gui
--- Blue Wave/DOS v2.20