Hi i have 2 isues when importing badareas.lst

1)

my badareas.lst:

BLUEWAVE Discussion about Bluewave reader and doors.
BR.MEDICINA
BR.POLITICA
FSX_ENG ENiGMA 1/2 BBS Support/Dev

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.


2)

My fsx group have internal prefix FSX_

The imported FSX_ENG area do no have the prefix at first time ,
then, if i edit a save the prefix are update to FSX_FSX_ENG

Also, i have a area as template.. the storage directory was not set from template in the imported area.

This sems to be a bug in the import process.

thanks!

---
þ Synchronet þ Dock Sud BBS TLD 24 HS - bbs.docksud.com.ar

Re: issues importing BADAREAS.LST
By: Ragnarok to DOVE-Net.Synchronet_Discussion on Mon Mar 23 2020 05:53 pm

Hi i have 2 isues when importing badareas.lst

1)

my badareas.lst:

BLUEWAVE Discussion about Bluewave reader and doors.
BR.MEDICINA
BR.POLITICA
FSX_ENG ENiGMA 1/2 BBS Support/Dev

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)?

2)

My fsx group have internal prefix FSX_

The imported FSX_ENG area do no have the prefix at first time ,
then, if i edit a save the prefix are update to FSX_FSX_ENG

Also, i have a area as template.. the storage directory was not set from template in the imported area.

This sems to be a bug in the import process.

I was able to reproduce this one and looks like an easy fix. Thanks for the report!

digital man

Synchronet/BBS Terminology Definition #10:
C64 = Commodore 64 (personal computer)
Norco, CA WX: 61.7øF, 62.0% humidity, 3 mph NNW wind, 0.61 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

El 23/3/20 a las 21:20, Digital Man escribi¢:

Re: issues importing BADAREAS.LST
By: Ragnarok to DOVE-Net.Synchronet_Discussion on Mon Mar 23 2020 05:53 pm

Hi i have 2 isues when importing badareas.lst

1)

my badareas.lst:

BLUEWAVE Discussion about Bluewave reader and doors.
BR.MEDICINA
BR.POLITICA
FSX_ENG ENiGMA 1/2 BBS Support/Dev

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 know that i can do this job by hand (add the unconfigured area). I
just found this use case.

2)

My fsx group have internal prefix FSX_

The imported FSX_ENG area do no have the prefix at first time ,
then, if i edit a save the prefix are update to FSX_FSX_ENG

Also, i have a area as template.. the storage directory was not set from template in the imported area.

This sems to be a bug in the import process.

I was able to reproduce this one and looks like an easy fix. Thanks for the report!

digital man

Great! Thanks you!

---
þ Synchronet þ Dock Sud BBS TLD 24 HS - bbs.docksud.com.ar

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

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net