Just checking to make sure things are working properly with HPT.
I do have a question. I have separate files for my config. (config, areas, links, filearea, etc...)
When a new message echo is created, is there a way to have it put the entry in the 'areas' config, instead of the main 'config'?
It's not a major issue, just a curious question... :)
enWhen a new message echo is created, is there a way to have it put the
in the 'areas' config, instead of the main 'config'?
Yes, I don't have that in my config these days but have done it in the past. You'll need a couple keywords for that in the link definitions for that I believe.
I've been meaning to look closer at that myself but haven't done so yet.
I'll have to keep reading about the keywords. Like I said, not a big
deal, just would like to keep the config files neat and orderly... ;)
It's a bit of a pain to set everything up initially, but once it's running, it's quick and had a lot of functionality. :)
Just checking to make sure things are working properly with HPT.
I do have a question. I have separate files for my config. (config,
areas, links, filearea, etc...)
When a new message echo is created, is there a way to have it put the entry in the 'areas' config, instead of the main 'config'?
I do have a question. I have separate files for my config. (config,
areas, links, filearea, etc...)
When a new message echo is created, is there a way to have it put the
entry in the 'areas' config, instead of the main 'config'?
Yes, in husky 1.9 it is AreafixAutoCreateFile for echos and FilefixAutoCreateFile for file echos.
Yes, in husky 1.9 it is AreafixAutoCreateFile for echos and
FilefixAutoCreateFile for file echos.
i think what he's asking is more like, will autoadded areas be placed into one
of
fidonet.areas
fsxnet.areas
micronet.areas
instead of the main config file... does hpt and friends differentiate areas coming from certain addresses to be able to do this?
i think what he's asking is more like, will autoadded areas be placed
into one o f
fidonet.areas
fsxnet.areas
micronet.areas
instead of the main config file... does hpt and friends differentiate areas comi ng from certain addresses to be able to do this?
intYes, in husky 1.9 it is AreafixAutoCreateFile for echos and
FilefixAutoCreateFile for file echos.
i think what he's asking is more like, will autoadded areas be placed
of
Yes, with the above keywords in a node definition new areas will be
added to the given file. This works with message and file areas. Be sure to include the file in your config.. :)
theWhen a new message echo is created, is there a way to have it put
entry in the 'areas' config, instead of the main 'config'?
Yes, in husky 1.9 it is AreafixAutoCreateFile for echos and FilefixAutoCreateFil e for file echos.
Yes, with the above keywords in a node definition new areas will be
added to the given file. This works with message and file areas. Be sure
to include the file in your config.. :)
Ahhh, found it... It's easy to get lost in the documentation for the config files... :)
Sounds like you've taken your husky config further along than I have. I may need to ping you for keywords and placement at some point.. :)
Looks like you've plugged husky into Mystic as well.. I like it.. :)
it'si think what he's asking is more like, will autoadded areas be placed
into one o f
fidonet.areas
fsxnet.areas
micronet.areas
instead of the main config file... does hpt and friends differentiate
areas comi ng from certain addresses to be able to do this?
That's exactly it. I'm not sure if it's possible or not. If it's not,
alright, as I don't have that many areas being autoadded. It actuallygives
me a chance to view/correct the entry before moving it to the otherconfig
file.
I do have a question. I have separate files for my config.
(config, areas, links, filearea, etc...)
When a new message echo is created, is there a way to have it
put the entry in the 'areas' config, instead of the main
'config'?
Yes, in husky 1.9 it is AreafixAutoCreateFile for echos and
FilefixAutoCreateFile for file echos.
i think what he's asking is more like, will autoadded areas be placed
into one of
fidonet.areas
fsxnet.areas
micronet.areas
instead of the main config file... does hpt and friends differentiate areas coming from certain addresses to be able to do this?
editing the entries and cleaning things up... still have a bunch to fix the short title on but i can see the echotag in golded and that's more i mportant than what some title says ;)
When a new message echo is created, is there a way to have it
put the entry in the 'areas' config, instead of the main
'config'?
Yes, in husky 1.9 it is AreafixAutoCreateFile for echos and
FilefixAutoCreateFile for file echos.
Alan has already answered your question so I have nothing to do. :)
instead of the main config file... does hpt and friends differentiate
areas coming from certain addresses to be able to do this?
Alan has already answered your question so I have nothing to do. :)
editing the entries and cleaning things up... still have a bunch to
fix the short title on but i can see the echotag in golded and that's
more i mportant than what some title says ;)
I've been working on that as well. I just about have all of the file
echos done. There were a few that auto-added yesterday.
The message echos still need to have the descriptions added to them. That's a bit of a daunting task with over 550 echos set up right
now... I think I'll work on them in sections, so it's not so bad... :)
whoa! i have like 5 or 6 groups in effect for one network, alone... plus
i use Z for all newly autoadded echos... i've not done anything with
FDNs yet... anyway , at 5 groups per network, i'd run out of groups at 5 networks joined... i reall y like sbbs' 8 character groups... they're
nicer than the single characters once used a lot better than the 4 characters ones that came later... i was just abou t hitting my limits
in fastecho, too, when i was running it... especially when h aving to
block access to the individual beta testing areas and private echo area
s i carry... i won't even mention limiting access to zone restricted
sysop only areas and the like ;)
whoa! i have like 5 or 6 groups in effect for one network, alone...
plus i use Z for all newly autoadded echos... i've not done anything
with
I'm just using one group per network, for the most part. I do have
another group set up for the usenet newsgroups that I carry, and I get those from multiple hubs, so it gets a bit interesting. I also work
with 4 different hubs just for fidonet as well...
FDNs yet... anyway , at 5 groups per network, i'd run out of groups
at 5 networks joined... i reall y like sbbs' 8 character groups...
they're
Are you referring to groups in hpt?
If so, you can have many more groups. I've stopped using single
letters for groups, and started using 'fido', 'fsx', etc. It makes it
a lot easier to keep them straight in my head...
nicer than the single characters once used a lot better than the 4
characters ones that came later... i was just abou t hitting my
limits in fastecho, too, when i was running it... especially when h
aving to
It's been awhile since I used Synchronet. I do have it running on one
of my systems, but it's acting as a FTN<>QWK gateway for a couple networks. I really don't even look at it that often...
block access to the individual beta testing areas and private echo
area s i carry... i won't even mention limiting access to zone
restricted sysop only areas and the like ;)
I haven't even worried about that, as I don't have any feeds outside
the zone. :)
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 371 |
Nodes: | 16 (2 / 14) |
Uptime: | 173:44:39 |
Calls: | 7,915 |
Files: | 12,983 |
Messages: | 5,797,634 |