OS/2 Shareware BBS: 2 BBS/02-BBS.zip/nodew103.zip/NODEREQ.HLP

OS/2 Help File | 1998-08-17 | 22KB | 538 lines

ΓòÉΓòÉΓòÉ 1. Main Menu ΓòÉΓòÉΓòÉ

You must supply the following information in your node request form:

     Your name

     Your VOICE phone

     Name of your node

     Your location

     Your DATA phone

     Hours of operation

     Maximum connection baudrate

     Modem type and capabilities

     Type of mailer software


ΓòÉΓòÉΓòÉ 1.1. Your name ΓòÉΓòÉΓòÉ

Type your real name in this field, e.g. "Ivan Ivanoff". This information will
be placed in the your nodelist line, so be sure to type everything correctly.

Usually, this field may contain both your name and surname as in the example
shown above. This is traditional for Net 5020.

No nick-names are permitted. Consider it mandatory to use your real name here.


ΓòÉΓòÉΓòÉ 1.2. Your VOICE phone ΓòÉΓòÉΓòÉ

Your Network Coordinator must be able to contact you by voice, in case of
computer hardware malfunction, or some similar accident which makes it unable
to communicate via netmail.

You may place your home or office phone here, preferably the home one to make
it possible for your coordinator to contact you during holidays or week-ends.


ΓòÉΓòÉΓòÉ 1.3. Name of your node ΓòÉΓòÉΓòÉ

Type the desired name for your mail station. This name is reflected in the
nodelist line as well.

According to the unofficial Z2C statement, the word "BBS" is stripped from the
nodelist line by the local Network Coordinator. Therefore, it's recommended not
to include this acronym, otherwise your nodelist entry may be changed without
any notice.

Note:  An official FTS-0005 limit for this field is 20 characters. But no one
really checks it.


ΓòÉΓòÉΓòÉ 1.4. Your location ΓòÉΓòÉΓòÉ

This information is used for the nodelist line. No detailed address is
required. Basically, for Moscow stations, simple "Moscow, Russia" or even
"Moscow" will be enough.

Note:  Since the Wizard includes information from this field in the nodelist
line, any extra information, such as district or street name, may result in
rejecting your node request application. Don't be a kid, and don't type useless
stuff.


ΓòÉΓòÉΓòÉ 1.5. Your DATA Phone ΓòÉΓòÉΓòÉ

This is the phone number which should be used when calling your system. If it's
the same as your voice phone, you are required to duplicate it anyway without
typing something like "THE-SAME" or similar stuff. Failing to do this results
in your node request filled improperly.

Since this program is designed for intra-Moscow usage only, the 7-095- is
automatically added to the nodelist line and the first digits are stripped from
your data phone in order to leave the last 7 ones. Therefore, any of the three
following records are considered valid:

     7-095-621-5628

     [phone]

     6215628

 Check your final nodelist line after filling this field, it must contain a
 valid phone number in the FTS-approved form: "7-095-xxx-xxxx". If it does not,
 check this field again.


ΓòÉΓòÉΓòÉ 1.6. Hours of operation ΓòÉΓòÉΓòÉ

This is perhaps the most difficult part of writing the node request manually.
Fortunately, Node Request Wizard allows you to do this without referring to FAQ
and FSC-0062 stuff.

The only thing you need to know is that your hours of operation must include
05:30-07:30 time period. This is Zone 2 mail hour extended by so-called Moscow
local mail hour, the time when your system always must be up. Therefore,
settings like "01:00-07:00" are not advised (although formally permitted in Net
5020).

If you're operating a 24h "continuous mail" system, check the button next to
these two fields instead of setting something like "00:00-00:00".

Refer to Skip Txy flag if equal to Zone 2 MH if your system is private and you
want to state that it operates during mail hours only...


ΓòÉΓòÉΓòÉ 1.7. 24h (Continuous Mail) ΓòÉΓòÉΓòÉ

If your system really operates round-the-clock, accepting inbound netmail all
the time, check this field. It overrides the values of "Hours of operation"
spin buttons when selected and the CM flag is included into your nodelist line
to indicate you are capable of 24h operation.

Note:  So-called "CM outbound" systems may not use this flag unless they have a
capability to always process all modem inbound calls. If your system uses a
"tone password" or a similar stuff for this feature, you may not use this flag.


ΓòÉΓòÉΓòÉ 1.8. Maximum Connection Baudrate ΓòÉΓòÉΓòÉ

The maximum connection baudrate your modem supports. For V34-capable modems, it
may be 28800 or 33600 baud; V32bis modems have a maximum baudrate of 14400
baud. Refer to your modem documentation if you still aren't sure what the
maximum baudrate for your modem is. A way of determining it on US Robotics
modems is so-called self-test: type "AT&T1" in any terminal emulator and look
at the "CONNECT ....." modem response.

If you take a look on the nodelist line, you'll probably notice that ",9600,"
is shown there instead of higher baud rates. That is correct. You need to
specify some additional flags (see Modem Capability Flags) to represent this
information in the nodelist. That's done for compatibility purposes.

Note:  Some 14400 modem users may be confused by 57600 baud rate stated in
documentation for their modems. There's nothing common between this value and
the actual capabilities of your modem. The "57600 baud" usually refers to the
maximum communication port data transfer rate which means you'll get a higher
CPS rate on uncompressed files. Never type 57333 or 57600 in this field unless
your modem supports the X2 protocol.


ΓòÉΓòÉΓòÉ 1.9. Modem Model ΓòÉΓòÉΓòÉ

This field holds the manufacturer and the brand name of your model. For
example, "ZyXEL U-1496+" Never type "generic", "unknown" or something similar:
your node request will be rejected for a long time.


ΓòÉΓòÉΓòÉ 1.10. Modem Capability Flags ΓòÉΓòÉΓòÉ

This field may be difficult to fill if your modem is not listed in the Modem
Wizard directory. If you didn't use Wizard, do it right now to check if your
modem is listed there. If not, select a generic modem with the same baudrate as
yours and read on...

First of all, if you have an RPI or WinModem, there are no error-correction
protocols at all. So, simply back out, your modem probably has no other
capabilities except V32B.

Here's a summary of commonly-used flags:

ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéFlag ΓöéImpliesΓöéDescription          Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéV22  Γöé       ΓöéThis flag is not     Γöé
Γöé     Γöé       Γöérequired. It should  Γöé
Γöé     Γöé       Γöéonly be used with    Γöé
Γöé     Γöé       Γöé1200 baud modems.    Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéV32  ΓöéV22    ΓöéV32 is actual with   Γöé
Γöé     Γöé       Γöérarely-used 9600     Γöé
Γöé     Γöé       Γöémodems. See also HST.Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéV32B ΓöéV32    ΓöéAlmost all 14400 and Γöé
Γöé     Γöé       Γöé16800 baud modems    Γöé
Γöé     Γöé       Γöésupport this         Γöé
Γöé     Γöé       Γöéstandard. Choose it. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéV32T ΓöéV32B   ΓöéModems supporting    Γöé
Γöé     Γöé       Γöé19200 and 21600 baud Γöé
Γöé     Γöé       Γöérates usually supportΓöé
Γöé     Γöé       Γöéthis standard.       Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéZYX  ΓöéV32B,  ΓöéZyXEL 14400 baud     Γöé
Γöé     ΓöéV42B   Γöémodems use this      Γöé
Γöé     Γöé       Γöéprotocol. Note that  Γöé
Γöé     Γöé       Γöéit implies V32B and  Γöé
Γöé     Γöé       ΓöéV42B flags.          Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéZ19  ΓöéZYX    ΓöéZyXEL 19200 baud     Γöé
Γöé     Γöé       Γöémodems use this      Γöé
Γöé     Γöé       Γöéprotocol. However,   Γöé
Γöé     Γöé       Γöéit's not officially  Γöé
Γöé     Γöé       Γöéapproved and is      Γöé
Γöé     Γöé       Γöéconsidered a         Γöé
Γöé     Γöé       Γöé"user-defined" flag  Γöé
Γöé     Γöé       Γöéin Zone 2.           Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéVFC  Γöé       ΓöéV.Fast Class appearedΓöé
Γöé     Γöé       Γöésome time before V.34Γöé
Γöé     Γöé       Γöéand is implemented inΓöé
Γöé     Γöé       Γöédual-standard modems.Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéV34  Γöé       ΓöéAll V.34 (28800 baud)Γöé
Γöé     Γöé       Γöéand V.34+ (33600     Γöé
Γöé     Γöé       Γöébaud) capable modems Γöé
Γöé     Γöé       Γöémust use this flag.  Γöé
Γöé     Γöé       ΓöéNote there is V34+   Γöé
Γöé     Γöé       Γöéflag.                Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéMNP  Γöé       ΓöéMNP is a basic data  Γöé
Γöé     Γöé       Γöécompression and errorΓöé
Γöé     Γöé       Γöécorrection method. ItΓöé
Γöé     Γöé       Γöéhas been superseded  Γöé
Γöé     Γöé       Γöéby V32bis.           Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéV42  Γöé       ΓöéThis error correctingΓöé
Γöé     Γöé       Γöétechnology is usuallyΓöé
Γöé     Γöé       Γöéimplemented in       Γöé
Γöé     Γöé       Γöéconjuction with MNP  Γöé
Γöé     Γöé       Γöélevel 5, see V42B    Γöé
Γöé     Γöé       Γöéjust below.          Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéV42B ΓöéMNP,V42ΓöéV42bis is currently  Γöé
Γöé     Γöé       Γöéimplemented in most  Γöé
Γöé     Γöé       Γöéof modems. We        Γöé
Γöé     Γöé       Γöérecommend to use thisΓöé
Γöé     Γöé       Γöéflag if you don't    Γöé
Γöé     Γöé       Γöéexactly know which   Γöé
Γöé     Γöé       Γöéerror correction and Γöé
Γöé     Γöé       Γöécompression protocolsΓöé
Γöé     Γöé       Γöéare supported by yourΓöé
Γöé     Γöé       Γöémodem.               Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéHST  Γöé       ΓöéHST flag corresponds Γöé
Γöé     Γöé       Γöéto the 9600 bps High Γöé
Γöé     Γöé       ΓöéSpeed Technology.    Γöé
Γöé     Γöé       ΓöéIt's rarely used.    Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéH14  ΓöéHST    ΓöéThis protocol is     Γöé
Γöé     Γöé       Γöéimplemented in many  Γöé
Γöé     Γöé       ΓöéUSR Courier modems.  Γöé
Γöé     Γöé       ΓöéLater ones, includingΓöé
Γöé     Γöé       ΓöéRussian Courier and  Γöé
Γöé     Γöé       Γöéthose capable of     Γöé
Γöé     Γöé       ΓöéV.34, include supportΓöé
Γöé     Γöé       Γöéfor 16800 baud HST.  Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéH16  ΓöéH14    ΓöéMost widely used now.Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéPEP  Γöé       ΓöéPacket Ensemble      Γöé
Γöé     Γöé       ΓöéProtocol is of no    Γöé
Γöé     Γöé       Γöémuch use today,      Γöé
Γöé     Γöé       Γöéhowever, as of AugustΓöé
Γöé     Γöé       Γöé1998, there are some Γöé
Γöé     Γöé       Γöénodes in Net 5020    Γöé
Γöé     Γöé       Γöé(e.g. 2:5020/1206)   Γöé
Γöé     Γöé       Γöéstill supporting it. Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ


ΓòÉΓòÉΓòÉ 1.11. Modem Wizard ΓòÉΓòÉΓòÉ

Modem Wizard offers you a quick and easy way to pick the nodelist flags and
similar stuff corresponding to your modem.

If your modem is not listed there, pick the "generic" modem with the closest
matching characteristics. Then check the  Modem Capability Flags field.


ΓòÉΓòÉΓòÉ 1.12. Mailer Capabilities ΓòÉΓòÉΓòÉ

The three check boxes regarding mail exchange protocols are intended for
advanced users. These settings do not directly affect your nodelist entry but
they define file request capabilities which form a file-request flag.

The FSC-0056 is commonly regarded as EMSI protocol. Most of the modern mailers
support it.

FTS-0006 or FTS-0001 capability is still offered by some mailers.


ΓòÉΓòÉΓòÉ 1.13. File and Update Requests ΓòÉΓòÉΓòÉ

Your mailer software may provide support for various types of file and update
requests, depending on its FTS capabilities and protocol implementation. The
four check boxes form a set of file request options and an appropriate X x flag
is added to the nodelist line.

This option is for advanced users only. Unexperienced ones should use Mailer
Wizard to recall a set of file-request flags corresponding to the default
set-up of their mailer.

Depending on the different mailer capabilities, some of the protocols may be
disabled (greyed). That's because EMSI standard does not support Bark
file/update requests by its definition, and FTS-0001 mailers are not
WaZoo-capable.


ΓòÉΓòÉΓòÉ 1.14. Mailer name ΓòÉΓòÉΓòÉ

Name and version number of your mailer software. For example, "T-Mail
2600.DOS/Noncommercial".

This information is not reflected in the nodelist entry but must be supplied to
your Network Coordinator.


ΓòÉΓòÉΓòÉ 1.15. Mailer Wizard ΓòÉΓòÉΓòÉ

For unexperienced users, this option is a great thing. Just click and choose
"T-Mail" as we don't believe you're using something else... Anyway there's a
list of other choices.

The information supplied by Mailer Wizard corresponds to the default set-up of
the specific mailer and is usually enough for a node request. However, we
recommend to include your mailer's version number in the Name field because
different releases of some mailers have different capabilities.


ΓòÉΓòÉΓòÉ 1.16. Final nodelist line ΓòÉΓòÉΓòÉ

This field dynamically changes as you alter the settings in any of the previous
fields. It's read-only by itself.

This entry will be included in the nodelist exactly in the same form as it
looks here, with an exception for BBS entries (see  Name of your node)


ΓòÉΓòÉΓòÉ 2. Modem Wizard ΓòÉΓòÉΓòÉ

The Modem Wizard offers a list of most popular modem types. If you've found one
that matches your modem (voice models are not listed separately, of course),
don't read on.

If your modem is not listed here, follow these steps:

   1. Look for a generic model with the same baudrate. If there are no models
      matching your modem's baudrate, quit the Wizard and fill the appropriate
      fields manually. (Bad luck...)

   2. There may be different categories of the "generic" models. You'll need to
      know about your modem capabilities. This information can be found in the
      user's manual.

   3. Pick a matching generic model.

   4. Quit the Modem Wizard. A message box appears informing that you need to
      state the manufacturer of your modem. Press ENTER.

   5. Go to the Model field and type the exact manufacturer and model of your
      modem, e.g. "Gateway Telepath 2000".

   6. Process with the rest of your application form.


ΓòÉΓòÉΓòÉ 3. Mailer Wizard ΓòÉΓòÉΓòÉ

To automatically supply information regarding your mailer's capabilities, you
may use this option. If you find your mailer in the list provided, the only
thing needed to be done is to state its version number and binding in the Name
field.

If the mailer you use is not listed, you'll need to supply the following
information (read the documentation and the on-line help):

   1. Version number (e.g. "2.55beta")

   2. Binding (build mode, e.g. "OS/2")

   3. Type (commercial/nocommercial/registered shareware version)


ΓòÉΓòÉΓòÉ 4. Templates ΓòÉΓòÉΓòÉ

To facilitate the node request creation, four templates are provided. There is
no functional difference in the program's behavior with either of them but the
start-up assignments and the formatting of the output file will be different.
Here's a summary:

Brief is preferred if you want to use your node as a private, mail-only station
with minimum information placed into nodelist. When you select this template,
the only things you'll probably need to correct are your name, phone, node
name, and modem information.

Standard and Advanced are two choices for those who are planning to reflect
more information for the nodelist. You need to browse through all the fields to
get it working. The principial difference between these two templates is the
different set of capability flags (see the Advanced menu).

If you're experienced enough, you may try None to start from a scratch. Don't
forget to specify the correct time of operation, otherwise your node request
will be most probably disqualified.


ΓòÉΓòÉΓòÉ 5. Advanced Settings ΓòÉΓòÉΓòÉ

The settings in this menu are intended mainly for advanced users. If you can't
understand something, you can skip it as it won't affect the processing of your
node request.

     Mail-Only

     Listed-Only

     No compression

     Encrypted mail

     Skip ,U,Txy if equal to Zone 2 MH


ΓòÉΓòÉΓòÉ 5.1. Mail-Only ΓòÉΓòÉΓòÉ

Checking this field adds the MO flag to the nodelist entry. Check it only if
you don't have a public BBS. This field is useless if you operate during zone
mail hour only.


ΓòÉΓòÉΓòÉ 5.2. Listed-Only ΓòÉΓòÉΓòÉ

Checking this field adds the LO flag to the nodelist entry. If you do not
accept calls from systems missing in the world nodelist, or their points, check
it.


ΓòÉΓòÉΓòÉ 5.3. No Compression ΓòÉΓòÉΓòÉ

If you don't accept inbound compressed netmail, check this field. This will
append the MN flag to your nodelist entry.


ΓòÉΓòÉΓòÉ 5.4. Encrypted mail ΓòÉΓòÉΓòÉ

If you can accept inbound encrypted netmail, check this field. The ENC flag
will be appended to your nodelist entry.


ΓòÉΓòÉΓòÉ 5.5. Skip ,U,Txy if equal to Zone 2 MH ΓòÉΓòÉΓòÉ

The ,U,Tcd flag is officially obsolete in Net 5020 because it equals to the
ZMH. However, it may be left there to emphasize that you don't accept inbound
calls at any other time.


ΓòÉΓòÉΓòÉ 6. Preview ΓòÉΓòÉΓòÉ

The Preview screen displays the exact layout of the node application form.
After saving it, you may correct it using your mail editor. We advise to
correct the field headers because they will be the same in many requests
generated using this tool.


ΓòÉΓòÉΓòÉ 7. Saving your Node Request form ΓòÉΓòÉΓòÉ

Just type fully-qualified path and filename for storing the form. It'll be an
ordinary text file (not a Fido-MSG file) which you can imbed into your letter
addressed to the nodemaker.


ΓòÉΓòÉΓòÉ 8. Appendices ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ 8.1. Network Coordinator ΓòÉΓòÉΓòÉ

A person whose abilities are to maintain the local network. For the present
time (August, 2nd, 1998), the Net 5020 coordinator is Alex GolosOFF.

The term "network coordinator" is usually abreviated to "NC". The term "N5020C"
refers to the Net 5020 Coordinator.

According to the Policy 4.07, you must forward your node request form to your
network coordinator.

Please take a minute to read the following chapter regarding the Net 5020 node
application policy:

Applying for a node number in Moscow


ΓòÉΓòÉΓòÉ 8.2. Applying for a node number in Moscow (Net 5020) ΓòÉΓòÉΓòÉ

Historically, the "nodemaking" scheme used in Moscow slightly differs from the
procedure given in Policy 4. This makes a lot of confusion for newcomers and
generally prevents the growth of the network, not due to the complexity of this
procedure but because of many people involved and low level of mutual
responsibility.

Beginning with July, 17th, 1998, the new procedure approved by N5020C is as
follows:

   1. Find a hub system that accepts new downlinks.

   2. Send an inquiry to the hub system operator. If he confirms that he can
      provide netmail feed to you, go to the next step otherwise try another
      hub.

   3. Write a node request application form.

   4. Forward your application among with the hub's confirmation message to the
      nodemaker. As of August, 2nd, 1998, the current nodemaker is Sergej
      Qkowlew.

   5. Immediately after sending your node request, configure your mailer
      software to allow inbound callers during 05:30-07:30, Moscow local time.
      Be sure to disable any file/update requests or BBS entries during this
      time. Failing to do so may result in cancelling your application.

   6. It takes up to a month for the nodemaker to process your node request. Be
      sure your mail system is functioning properly during this time. If you
      didn't receive a message saying that your request is cancelled, then
      everything is going OK and you'll appear in a local nodelist in the
      nearest future.

 There are also some differences between the official node request form
 described in Policy 4 and the one used in Net 5020. You need to include a
 prototype for your nodelist entry yourself in Moscow. Therefore, there's a
 higher degree of your responsibility for the node request processing.


ΓòÉΓòÉΓòÉ 8.3. Nodemaker ΓòÉΓòÉΓòÉ

A nodemaker is not proposed by the Policy. However, the size of Net 5020
requires a more decentralized node making system. Prior to July 17th, 1998,
nodemaker's responsibility was to collect node requests forwarded by hub
sysops. However, a new N5020C statement instructs the candidates to send their
node request forms themselves, including a hub's approval in their messages.

The nodemaker reviews your node request and if it's considered correct,
forwards it to the local Network Coordinator He also tests your system's
capability to observe mail events and we suggest to set up your mailer
properly...