Hello Sean.

12 Nov 02 21:48, Sean Dennis wrote to Mike Tripp:

 SD> I've printed out your message and am gonna try setting things up.

=If= it works as advertised, you should be able to make SEAL do most of the
work for you.  Just run SEALCFG to define each uplink as a filefeed and
point to the appropriate .NA file and then loop through commandline runs
of:

SEAL ADD F  
SEAL LINK  F 

SEAL should make all of the necessary entries in TICK.CFG for you,
presumably with the appropriate AKA flag next to each uplink/downlink and
will add the matching ;Filespec lines with appropriate descriptions from
the matching .NA, security locks/levels defaults from the matching uplink,
etc.

Be forewarned:  It will also generate a netmail for each uplink request and
a downlink notification of the manual change for each link.  Assuming you
already have these links established from your NEF setup, then you either
want to kill those SEAL-generated netmails before they scan out or consider
using a temporary netmail area definition as a bucket so that SEAL writes
them to another area that won't go anywhere and can be deleted easily. 
Don't forget to reset back to your real netmail area again after cleanup.

I think a lot of folks have done themselves more harm than good by
attempting to do manual changes to SQUISH.CFG, TICK.CFG, and/or SEAL.INI to
emulate what they think SEAL would do, rather than just convincing SEAL to
actually put it there in the first place.

.\\ike

--- GoldED 2.50+