24 May 15 19:44, you wrote to me:

 KR> Servus mark!

 KR> Am 24 May 15, mark lewis schrieb an All:

 ml>> autoAreaCreate on
 ml>> autoAreaCreateDefaults -p 30 -dupeCheck move -dupeHistory 11

 ml>> i had to comment them out of my config... that doesn't make sense,
 ml>> though, because those lines are in the default/sample...

 KR> Did you run tparser?

i just found out about it from another response...

 ml>> could it be that something else is missing for those lines to be
 ml>> valid?

 KR> tparser should tell you.

i'll give it a try...

 ml>> maybe something other option that tells where to create the areas?
 ml>> i've got several hundred areas to turn on and i really don't want to
 ml>> have to manually add each one to the config...

 KR> Why not? ;) Just kidding.

:lol:

 KR> As hpt is part of the husky suite, which is controlled by fidoconfig,
 KR> some config keywords are location/sequence sensitive. Fidoconfig is
 KR> the idea of a single configuration keyword place for all husky
 KR> modules. Some modules still have their own keywords but may use
 KR> existing configs of fidoconfig too.

yeah, i still gotta try to get the docs together into a readable format
that is easily accessible to me...

 KR> I'm to lazy to check where it belongs to, but i can tell you i have a

 KR> MsgBaseDir /path/to/msgbase

i'll add that to my configs...

 KR> keyword in my config files. It should be before any link or area
 KR> definitions.

ok... one thing i'm going to have to get used to is moving areas from one
location to another... i'm used to having a configuration binary where i
can change the name of the area files or the directory they are stored in
and the config binary automatically moves them for me...

eg:
old: /home/myuser/ftn/msgbase/foo
new: /home/myuser/ftn/msgbase/fido/backbone/foo

"foo" is the base name of the area's storage files, foo.jlr,
foo.jdx, etc...

 KR> Btw, there is a bug in the example config, carbon copy
 KR> definition must be after echoarea definitions.

i read about that recently... i don't have that in the example i pulled out
of one of the directories... the one i have is very very basic...

 KR> For JAM in general i found an echomail of 2006:

 KR> +++++++
 KR>  Gert Koefoed Andersen               2:236/150       01 Aug 06  18:36:00

 KR> Husky and specially hpt and msged stable support Jam and msg style echoes
 KR> bad bad bad, and gives error both why packing and scan echoes by Jam style
 KR> echoes.
 KR> +++++++

i'm not sure i understand the problem... sounds like it is about getting
messages out... i'm not having any problems doing that as can be seen by
these posts and my netmails to my uplink areafix ;) i'm all JAM over here
at this time...

 KR> There are not many JAM users out there and i don't know if issues were
 KR> fixed. So take care of your backup.

i will... for now it is easy enough... just starting out and pulling
%rescans from my uplink...

---