Sean Dennis wrote in a message to All:

SD> I'm using Seal 0.50 for my areafix manager and it works great... the
SD> question I have is how can I specify different networks in TIC.CFG? 
SD> I carry 10 networks and filebones for each of them... do I have to
SD> specify my alias for each network or do I just put in each
SD> uplink/downlink into TIC.CFG and let Seal worry about it?

Beware Seal for TIC processing...

Well, almost... this is a really specific problem that SEAL has with TIC
stuff... and it forced me to dump it and consequentially take up with NEF.

SEAL TIC processing has trouble with Binkley Style Outbounds (BSO) and the
way it handles points in a seperate point directory. IIRC... (it's been a
while since I saw this...) the problem is with PassThru file areas. If a
file comes in, that is distributed amongst regular nodes you feed and
points you feed, it builds up all the outgoing TIC files properly and
places them in the appropriate outbound directories. Great!

Once the point calls in and picks up his mail/files SEAL will see that the
area is PassThru, and that the point picked up the file. I guess it gets
confused about OutBound directories at that point... it sees no more .FLO
files with the FILE in it in *THAT* *POINT* directory and deletes the
PassThru file. Bad!

The problem is that there may be other downlink nodes in the *NON-POINT*
outbound directory with that file still in their .FLO files, but it's been
deleted so it only can send the accompanying .TIC file.

So if you have a mixture of points and nodes for downlinks, and you run
with a BSO where your points are in a .PNT directory (e.g.
P:\out\007c13a1.pnt), and you handle passthru file areas... you could get
burnt... :-(

*Paul*
--- timEd/386 1.10.y2k+