on 01-16-09 23:16: Nancy Backus to James Bradley re: Re: BW Full Screen [was--

 JB> Just filed down a Toyota alternator, and crammed it into the 4WD
 JB> Subaru puddle-jumper.  The list just got shorter!

 NB> Good for you.  :)  Congrats... :)

Thanks! I'm new to wrenching, so it's still a learning curve that looks like a
cliff. Stupid thing, everything was fine through weeks of -30C. -10C, and
everything went kaput. For the record, it was a Ford Festiva alternator that
shoe-horned into the Subaru, in case anyone wants to try it at home. 

 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...

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

 JB> I was still happy to use QWK packets. Provided I didn't add
 JB> or delete areas before uploading an existing reply, the message usually
 JB> got out to the intended area. Oddly, I had a message ready to fly for
 JB> Linux and added an area before I uploaded it. That message was hence
 JB> shuffled to Memories. 

 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...

Ah... That would make more sense than the nonsense I was trying to attach to
it. I just forget how Maximus handles those things, but I recall some new
echoes going in around that same time.

 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... :)

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

 JB> twit-filter, indicates I was on plenty.  I was using
 JB> f'req quite a bit back when I ran a board.

 NB> I wasn't much of a file person...  mostly it's been messages, so of
 NB> course the BW reader was a must...  it's what actually made reading
 NB> genealogy messages feasible back in the days of 500+ per day... as well
 NB> as being able to craft replies there... rather important when you
 NB> really want things to be right...

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

 JB> ... I'm not totally worthless. I can serve as a bad example!

 NB> Ah, yes...  there's a number of us around...  

I'm in good company. <-;



... What's another word for Thesaurus?
___ MultiMail/Linux v0.49

--- Maximus 3.01