TIP: Click on subject to list as thread! ANSI
echo: bluewave
to: Nancy Backus
from: James Bradley
date: 2009-01-23 18:24:14
subject: BW Full Screen [was--

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

 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.

 NB> You do realize, don't you, that BW will read any packets that are in
 NB> either QWK or BW format?  You just don't get ALL the bells and whistles
 NB> with a QWK packet that you would for a BW one... but for normal
 NB> messaging there isn't really a lot of difference between the two.  The

Ya, I'm using QWK packets, of course, but if the BW door was here - that would
be the carrot on the end of a stick I couldn't help but chase.

 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

 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.

 NB> I've run into my scenario often enough...  One learns to be careful and
 NB> watchful... :)  Sometimes the sysop will alert you to the area #'s
 NB> change, which is always helpful...  :)

My "bad"... I forgot to mention my problem occurred on Multimail
IIR correctly.


 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.

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

I only remember it working with BW. It has a syntax that is actually learnable
too! 

 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.

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

What is it - - - and it fills in the address from the
tear-line and
places the reply into the netmail 'echo'. Off it goes! 



... "The camera adds ten pounds. Stop eathing bloody cameras!"
--Carr, Jimmy
___ MultiMail/Linux v0.49

--- Maximus 3.01
* Origin: -=-= Calgary Organization CDN (403) 242-3221 (1:342/77)
SEEN-BY: 10/1 3 14/250 18/200 34/999 120/228 123/500 128/2 140/1 222/2 226/0
SEEN-BY: 236/150 249/303 250/306 261/20 38 100 1381 1404 1406 1410 1418
SEEN-BY: 266/1413 280/1027 320/119 396/45 633/104 260 267 285 690/682 734
SEEN-BY: 712/848 800/432 801/161 189 2222/700 2320/100 2905/0
@PATH: 342/77 140/1 261/38 633/260 267

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.