Hello everybody!
So I have my badareas.lst location defined in echocfg like this,
../Logs/badareas.lst
But when I go into a message group and want to import the badareas.lst the location is here,
../data/badareas.lst
Where else is this location defined so I can have them match?
RickV wrote to All <=-
Hello everybody!
So I have my badareas.lst location defined in echocfg like this,
../Logs/badareas.lst
But when I go into a message group and want to import the badareas.lst
the location is here,
../data/badareas.lst
Re: Badareas.lst location
By: RickV to All on Wed Sep 24 2025 06:17 pm
Hello everybody!
So I have my badareas.lst location defined in echocfg like this,
../Logs/badareas.lst
But when I go into a message group and want to import the
badareas.lst the location is here,
../data/badareas.lst
Where else is this location defined so I can have them match?
The only place that is defined is in your ctrl/sbbsecho.ini file
(which can be edited using echocfg) - the default value is "../data/badareas.lst", so it looks like you changed it: BadAreaFile = ../data/badareas.lst
--
digital man (rob)
RickV wrote to All <=-
Hello everybody!
So I have my badareas.lst location defined in echocfg like this,
../Logs/badareas.lst
But when I go into a message group and want to import the
badareas.lst the location is here,
../data/badareas.lst
Why would you do that? (put it in a Logs directory).
It's not a log. It's a list of bad (undefined) echo areas. Keep it
in ../data where it belongs, and where other parts of SBBS expect it
to be. Sheesh.
Hello Digital!../logs/badareas.lst, that's where I want it. But
19 Apr 71 23:13, you wrote to me:
Re: Badareas.lst location
By: RickV to All on Wed Sep 24 2025 06:17 pm
Hello everybody!
So I have my badareas.lst location defined in echocfg like this,
../Logs/badareas.lst
But when I go into a message group and want to import the
badareas.lst the location is here,
../data/badareas.lst
Where else is this location defined so I can have them match?
The only place that is defined is in your ctrl/sbbsecho.ini fileYes I did change it to
(which can be edited using echocfg) - the default value is "../data/badareas.lst", so it looks like you changed it: BadAreaFile = ../data/badareas.lst
when I try and import the badareas it's shows ../data/badareas.lst, I then have to change it to where the file is. ../logs. Why is it not seeing it where I have it set to? Thanks my question.
Could this be a bug?
Re: Badareas.lst location
By: RickV to Digital Man on Wed Sep 24 2025 09:57 pm
../logs/badareas.lst, that's where I want it. But
Hello Digital!
19 Apr 71 23:13, you wrote to me:
Re: Badareas.lst locationthis,
By: RickV to All on Wed Sep 24 2025 06:17 pm
Hello everybody!
So I have my badareas.lst location defined in echocfg like
file
../Logs/badareas.lst
But when I go into a message group and want to import the
badareas.lst the location is here,
../data/badareas.lst
Where else is this location defined so I can have them match?
The only place that is defined is in your ctrl/sbbsecho.ini
(which can be edited using echocfg) - the default value isBadAreaFile =
"../data/badareas.lst", so it looks like you changed it:
../data/badareas.lstYes I did change it to
when I try and import the badareas it's shows ../data/badareas.lst,
I then have to change it to where the file is. ../logs. Why is it
not seeing it where I have it set to? Thanks my question.
Because SCFG doesn't read or write to the sbbsecho.ini file.
Could this be a bug?
No, operating as designed.
--
digital man (rob)
RickV wrote to Dan Clough <=-
So I have my badareas.lst location defined in echocfg like this,
../Logs/badareas.lst
But when I go into a message group and want to import the
badareas.lst the location is here,
../data/badareas.lst
Why would you do that? (put it in a Logs directory).
It's not a log. It's a list of bad (undefined) echo areas. Keep it
in ../data where it belongs, and where other parts of SBBS expect it
to be. Sheesh.
Ok, but don't you think it should work as defined in the config setting you set? Also why then is it DEFINABLE?
OK, certainly not a big deal. Can I ask why the option to put it in a different directory then?
Digitalman - seems like this is a bug to me. The function in SCFG is
not reading the defined location of 'badareas.lst' and seems hard-wired
to ../data/badareas.lst .
RickV wrote to Dan Clough <=-
So I have my badareas.lst location defined in echocfg like this,
../Logs/badareas.lst
But when I go into a message group and want to import the
badareas.lst the location is here,
../data/badareas.lst
Why would you do that? (put it in a Logs directory).
It's not a log. It's a list of bad (undefined) echo areas. Keep
it in ../data where it belongs, and where other parts of SBBS
expect it to be. Sheesh.
Ok, but don't you think it should work as defined in the config
setting you set? Also why then is it DEFINABLE?
Well, yes. I got curious and went to check what you're saying. I
changed the defined location of 'badareas.lst' (in sbbsecho.ini, using
Echocfg). Then I went into SCFG/Message Areas/Message Group/Import
Areas/badareas.lst ... and ... it still showed the location as
../data/badareas.lst . So it does appear to be broken, as you said.
Digitalman - seems like this is a bug to me. The function in SCFG is
not reading the defined location of 'badareas.lst' and seems
hard-wired to ../data/badareas.lst .
Digital Man wrote to Gamgee <=-
Re: Re: Badareas.lst location
By: Gamgee to RickV on Thu Sep 25 2025 09:19 am
Digitalman - seems like this is a bug to me. The function in SCFG is
not reading the defined location of 'badareas.lst' and seems hard-wired
to ../data/badareas.lst .
That's just the default value in the input dialog; typing a different value overrides the default.
Yes in theory, SCFG could read the sbbsecho.ini file to find whatever path/filename the sysop chose to name that file. However, a sysop can create/use multiple sbbsecho configuration files (they don't have to be ctrl/sbbsecho.ini), so SCFG wouldn't magically know how to find any
other non-default SBBSecho config files.
If you think it's a bug, file a bug report.
Yes in theory, SCFG could read the sbbsecho.ini file to find whatever path/filename the sysop chose to name that file. However, a sysop can create/use multiple sbbsecho configuration files (they don't have to be ctrl/sbbsecho.ini), so SCFG wouldn't magically know how to find any other non-default SBBSecho config files.
That seems a pretty niche use-case - I'd guess that VERY few sysops are using multiple sbbsecho.ini files. If somebody *was*, then yes I could
see how they might need to type in a new value in the input dialog to
import that badareas.lst into SCFG. But for the other 99% ...? To be
fair - I see ZERO reason to change it from the default location anyway.
I guess my question then is - does the location specified in
sbbsecho.ini for the badareas.lst file actually make that file get created/updated in the location specified?
Or will it always go to ../data ?
Digital Man wrote to Gamgee <=-
Re: Re: Badareas.lst location
By: Gamgee to Digital Man on Thu Sep 25 2025 01:51 pm
Yes in theory, SCFG could read the sbbsecho.ini file to find whatever path/filename the sysop chose to name that file. However, a sysop can create/use multiple sbbsecho configuration files (they don't have to be ctrl/sbbsecho.ini), so SCFG wouldn't magically know how to find any other non-default SBBSecho config files.
That seems a pretty niche use-case - I'd guess that VERY few sysops are using multiple sbbsecho.ini files. If somebody *was*, then yes I could
see how they might need to type in a new value in the input dialog to
import that badareas.lst into SCFG. But for the other 99% ...? To be
fair - I see ZERO reason to change it from the default location anyway.
If a sysop had multiple sbbsecho config files and they all used the default badareas.lst file path (which seems unlikely), then the sysop would not need to type in a new value if/when importing that
badareas.lst file into SCFG. I only mentioned the sbbsecho.ini file
issue because it means that desired/expected behavior is that the bad
area file path is pulled from that file automatically, but there's
really no way for SCFG to know what sbbsecho config file path/filename that SBBSecho is *actually* using.
I guess my question then is - does the location specified in
sbbsecho.ini for the badareas.lst file actually make that file get created/updated in the location specified?
Yes.
Or will it always go to ../data ?
No, the path/filename set in sbbsecho.ini is what SBBSecho (or at least the instance that runs with that config file) will update/write when messages for bad area-tags are received.
Digital Man did say "it's operating as designed", so for some reason
that's the way it suppose to be.
No, the path/filename set in sbbsecho.ini is what SBBSecho (or at least
the instance that runs with that config file) will update/write when messages for bad area-tags are received.
User Name: [ John Doe ]
But as soon as you type a character, it prints that character and wipes out the example to allow you to continue. Even if you were to hit "Enter" with John Doe there, it wouldn't save that username to the user base, because it's just displayed to assist you as an example.
Basically the same situation?
Sysop: | DaiTengu |
---|---|
Location: | Appleton, WI |
Users: | 1,071 |
Nodes: | 10 (0 / 10) |
Uptime: | 64:34:29 |
Calls: | 13,754 |
Calls today: | 1 |
Files: | 186,984 |
D/L today: |
8,326 files (2,405M bytes) |
Messages: | 2,425,522 |