| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Seal |
Sean Dennis wrote in a message to All: SD> Hello, All. SD> I'm using Seal 0.50 for my areafix manager and it works great... SD> the question I have is how can I specify different networks in SD> TIC.CFG? I carry 10 networks and filebones for each of them... do SD> I have to specify my alias for each network or do I just put in SD> each uplink/downlink into TIC.CFG and let Seal worry about it? SD> I know that sounds confusing, but I've used NEF up to this time and SD> am just trying to sort things out. SD> Any and all help is appreciated. ;) I just looked at mine, and here's what I see: Net 270 Node 615 Aka (7 lines of stuff here, many for nets that don't exist any more) The address I used in each net is listed on a separate Aka line. In (path to inbound directory) Zone 1 (path to zone 1 outbound) (Followed by paths to outbound directories for each AKA) This is followed by the area stuff, like so: Area (path to file area) (area name) (node) (parameters) ;FileSpec (seal-specific stuff) repeated as necessary, and then some lines for things like LogPath, Crc, etc. I use Seal 0.40 here, don't recall if I ever upgraded to 0.50, and let it create the files initially -- if you're worried about it stepping on what you already have then point 'em someplace other than any existing files. Then fiddle with it using your favorite editor. Not that big a deal... ---* Origin: TANSTAAFL BBS 717-838-8539 (1:270/615) SEEN-BY: 10/345 106/1 128/187 150/115 220 167/133 226/600 229/1000 2000 3000 SEEN-BY: 249/116 270/615 280/5003 379/1 1200 633/267 270 712/848 2404/201 SEEN-BY: 3800/1 @PATH: 270/615 150/220 379/1 633/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™.