Go to the first, previous, next, last section, table of contents.
- Syntax:
-
Areafile type filename
- Examples:
-
Areafile Fastecho c:\fastecho\fastecho.cfg
-
-
Areafile Squish c:\squish\squish.cfg
-
-
Areafile AreasBBS c:\squish\areas.bbs
-
-
Areafile GEcho c:\gecho
-
-
Areafile Fidoconfig
This keyword tells MsgEd TE which areafile to use. The type
parameter designates the type of tosser configuration file to use. It can be
`Squish', `Fastecho', `GEcho', `fidoconfig' or
`AreasBBS'. The filename parameter specifies werhe to find the
tosser configuration that should be read. It's useage depends on the type of
your tosser:
- `AreasBBS', `Fastecho'
The path to and filename of the configuration file, like
c:\fastecho\fastecho.cfg
.
- `Gecho'
You must specify the path to your GEcho installation directory rather than a
configuration file name, e.g.
c:\gecho
. Only GEcho 1.20 is supported.
- `fidoconfig'
According to the Husky policy of doing things, the path to the fidoconfig
file is read from the default value or from the `FIDOCONFIG' environment
variable. Hence, for fidoconfig, the second parameter of this keyword is not
used to configure the path to the config file. Instead, it is used to
configure how the config file should be treated. This can be:
- `Areas'
Only the mail area configuration (echo-, local and netmail areas) is read
from fidoconfig, i.E. the fidoconfig file is only used like any other
areafile. This is also the default behaviour if you omit the second
parameter.
- `Settings'
If you specify `Areafile Fidoconfig Settings', MsgEd TE will read
as much configuration settings from the fidoconfig file as possible. Among
other things, this is the user name(s), the Fido AKA(s) and the echotoss log
file position. Mail area configuration, on the other hand, is not read.
- `Both'
With this setting, both the general configuration settings and the mail area
configuration will be read from fidoconfig.
The fidoconfig routines are able to follow include statements inside the
fidoconfig file automatically.
- `Squish'
The path to and name of the configuration file, like in
c:\squish\squish.cfg
. Plase note that only the area definitions from
this file itself will be read. If the Squish configuration file references
another `areas.bbs' file, you have to define it separately for
MsgEd TE using a second Areafile
statement.
Go to the first, previous, next, last section, table of contents.