Tag Alan!
Am 23 Jun 15, Alan Ianson schrieb an All:
AI> I am in the process of setting up golded with Mystic, Golded+ doesn't
AI> internally support Mystic, does it?
If it would, i wouldn't support you. The FTN compatibiliy of mystic can be
called alpha by good will and it's not liked by many nodes i know.
AI> Some of the areas I have here are QWK networks. Does Golded+ support
AI> QWK message areas?
I don't have any ged+ docs, but the goldusr.doc of golded 2.50 had an
explanation of goldeds QWK features. If you could get actual docs, user guide
and reference guide, you may find keywords like
QWKIMPORTPATH
Path where incoming QWK packet files (CONTROL.DAT and
MESSAGES.DAT) can be found.
and a good introduction into goldeds qwk system. It had some limitations, i.e.:
"GoldED currently doesn't support unpacking and packing of compressed .QWK and
.REP packets. You must unpack and pack your QWK/REP packets manually or using a
batchfile."
and it does overwrite export, so you must deliver exported mails before writing
again.
There are many keywords beginning with QWK... to much to keep it short here.
AI> I'm not exactly sure what the internal difference between QWK and FTN
AI> msgs except that QWK areas don't have any of the kludges that FTN
AI> msgs do and there is no node number on the origin line. Is there a
AI> setting I can use in golded's config for the QWK areas?
I'm sorry, i can remember using Yuppie!s QWK features once, but i can't
remember any details. As of goldref told me "CTRLINFO
Enables or disables tearline and/or origin in random system groups." it should
be possible to use golded random system for qwk origin lines. It may be
possible that the origin line is replaced by the uplink node system of the qwk
user.
AI> One last question, a couple of the nets I have here use alias/handle
AI> rather than real names, is there a setting that I can use with a group
AI> of areas to use my nickname by default?
Yes. That can be defined by goldeds random system. The standard config file for
that is called goldrand.cfg. Don't get confused, it's more of a template and
random system.
It uses group and endgroup statements to define configuration blocks.
The group statement can be an echotag like following, where all REQUEST.* echos
use that group, or by the member line for each echoarea that should get that
config block too.
#GROUP REQUEST.*
# MEMBER
# AKA 2:240/1351.7
#; template request.tpl
# ORIGIN "OS/2... a point of no return"
# ORIGIN "Hyperspeed SCSI-Modem: 3,2MB/s"
#TWITMODE blank
#ENDGROUP
As far as i know USERNAME is a valid keyword for the random system too.
Kai
--- GoldED+/LNX 1.1.4.7
* Origin: Target locked (2:240/1351.7)
|