Set the contents of text files
Syntax: WRITE <A|B|C|H|I|L|S> <CR>
The WRITE command is used to set the contents of several
news/information files for the user. It is also used to set a couple of special
purpose configuration files (Beacon and Setsearch).
By using the WRITE-Command, the texts for L(A)test news, (B)eacon,
(C)-Text, (H)elp, (I)nfo, (LO)cal and (S)etsearch may be entered. All texts except
(B)eacon and (S)etsearch may have any desired format. The C-text is sent after the
standard system prompt at the beginning of a connect. Standard prompt is
"xxxx/FlexNet Vx.x". The C-Text is shown after this.
We recommend the following usage of the texts:
LATEST NEWS: recent information about the
node and things every user should know
INFO: general information about the digipeater.
QTH, hardware, antennas, use of IO-ports etc. You should not forget to mention the user
QRG’s.
LOCAL: this text is appended to the C-Text,
when the user comes direct, i.e. without digipeaters in the path. This is the right place
for information about the channel access method and other information which is only
interesting for local users.
HELP: A short user’s guide to the
system with the most important commands.
The end of the text is marked by either /EX or Ctrl-Z. The text is saved up to the last
line before the /EX. Since many PR-stations use "split screen" programs, it is
recommended to begin every text except the C-Text with a single <CR>. This looks
much better.
The Beacon-file has a special
format. You may set up any beacon on any port. The file format is as follows:
# <t> <p> <tocall> [via [via ...] ] :Beacon
text..........................#
<#> delimits the different beacon information
<t> time between two beacon transmissions, in minutes. (1..255 minutes)
<p> port number where the beacon is to be sent
<tocall> Destination call of the beacon, for example "BEACON",
"RMNC", "FLXNET", "TEST" or similar , there may be up to 8
digipeaters specified, via which the beacon will be sent.
Example:
All beacons are sent as UI (Unproto-Information) with the command bit
set.
The SETSEARCH-file has a special format, too. There may be as many
search paths as you like. The limit is dependent upon the available memory. The number of
the digipeaters is limited to 7. The format is:
<call1>
<call1> [ <call2> [ <call 3> [ <call 4> [ <call 5> ]]]]
The SETSEARCH-file contains all paths via which the FIND-Command sends
its UI-Frames. The first callsign in the line is the digipeater which shall send the UI to
the user, the following digipeaters specify the path to the destination digi. These paths
should always be identical to the path a user will use. This means, digipeaters on the
route to the destination should be left out, the autorotter will know the way.
Example:
