TIP: Click on subject to list as thread! ANSI
echo: bluewave
to: James Bradley
from: Nancy Backus
date: 2009-01-25 23:35:08
subject: BW Full Screen

-=> Quoting James Bradley to Nancy Backus on 01-23-09 18:24 <=-

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

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

Is there a MultiMail door, too?  I thought it was only a reader?  In any
case, I've never used it in any form, being perfectly happy with my BW
which works just fine... :)  And the only time I've ever had problems
with messages going to the wrong echo has been with something changing
on the bbs end of things so that I needed to have a new configuration
from the bbs to get the messages into the right echoes...  
 
 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!  ;)

 JB> I only remember it working with BW. It has a syntax that is actually
 JB> learnable too! 
 
That it is.  :)  I've had occasion on just about every bbs I've ever
been on to need to fix the read pointers... so I've learned about every
way there is (and found, as I said, that some just don't work the way
they pretend to... )  Some of them I found by serendipity, too...

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

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

Nope, - does it...  I went and looked it up...  :)

ttyl      neb

... Multitasking: Screwing everything up at once.

* Origin: (1:3634/12)
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: 3634/12 123/500 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™.