TIP: Click on subject to list as thread! ANSI
echo: maximus
to: LINDA HARGRAVES
from: PATRICK MCCULLOUGH
date: 1997-08-28 01:59:00
subject: new message area/menu

 Linda Hargraves wrote in a message to All:
LH> Hi,
LH> I hope someone can give me some help.  I am running max 2.02 and
LH> please don't tell me to upgrade.  I like this version.
 That's the best reason to stay with any version: if it works
 for you, use it.  :)
LH> I am trying to figure out an easy way to make some message
LH> changes.  I want to have a menu something like this:
LH>     Local Messages 
LH>     Fidonet Local Message Bases
LH>     Fidonet National Message Bases
LH>     Netmail/Internet e-mail
LH>    I know I need a ctl file for each area and I am working on them. 
 Unless 2.02 is vastly different than 3.0 (I've never used 2.02), why
 do you _need_ seperate CTLs for each area?  I have local, Fido, and
 an 'othernet' echos all in one CTL.  Works fine.
 Actually, someone can correct me on this, but I think you *could*
 roll all the CTLs into one if you wanted.  At least under 3.x anyway.
LH> What I want to know is: can I have each area start with Area 1
LH> without getting them mixed up?  So far I have them as starting with
LH> different numbers.  I have msgarea.ctl, msgarea1.ctl & msgarea2.ctl
LH> and am putting them in max.ctl.
 Don't think you can repeat 1... but how about letter/number combos?
 Say, L1 for local, FL1 for Fido local,  F1 for Fido national, and
 Net for netmail and Inet for email?
 Dunno if you can do that under 2.02... but it's great under 3.x.  One
 of the best parts is that if you drop an echo, you don't have any
 problems with renumbering.
LH> If anyone can give me a little help, I would appreciate it very
LH> much.
 Hope this has helped.  :)
 Patrick
--- timEd 1.10
---------------
* Origin: Layzner SPT-LZ-00X (1:133/1024)

SOURCE: echomail via exec-pc

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