Servus mark!

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...

Did you run tparser?

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

tparser should tell you.

 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...

Why not? ;) Just kidding.

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

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

MsgBaseDir /path/to/msgbase

keyword in my config files. It should be before any link or area definitions.
Btw, there is a bug in the example config, carbon copy definition must be
after echoarea definitions.


For JAM in general i found an echomail of 2006:

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

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

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

Tschuess

Kai

--- GoldED+/LNX 1.1.4.7