Re: Re: issues importing BADAREAS.LST
  By: Ragnarok to Digital Man on Mon Mar 23 2020 10:04 pm

 > >  > here i have mixed areas from 2 nets that
 > >  > FSX_ENG is from FSX net and the others are from FIDONET..
 >
 > >  > so, i cannot use the import option, because these all finished in the
 > >  > grup that i was select
 >
 > >  > maybe adding the node can help to identify where come from.
 >
 > > The EchoList file format (of which the badareas.lst is conforming) does
 > > not contian node numbers. Perhaps if the source zone number is > 6, then
 > > store it in a separate file (e.g. badareas.z21.lst)?
 >
 > Yeah, i think that separated files per zone/network just help to
 > identify the unconfigured areas. Also the auto add areas function seems
 > to be very useful!

I think I'm going to create SCFG import support for echostats.ini instead as
that file already has the packet origin address and keeps track of the
known/unknown status of each area. It's not as concise as badareas.lst, but it
has the relevant information needed.

 > I know that i can do this job by hand (add the unconfigured area). I
 > just found this use case.

Awesome.

                                            digital man

Synchronet "Real Fact" #49:
Synchronet program was named 'sbbs' instead of 'sync' to avoid conflict w/Unix.
Norco, CA WX: 56.1øF, 74.0% humidity, 8 mph ENE wind, 0.61 inches rain/24hrs
--- SBBSecho 3.10-Linux