SFNetAdd32 v0.4b Beta 1 - SFToss32 Multi-Link Notes
===================================================

SUPPORTED CFG FORMATS
---------------------

Legacy single-link format:

  ADDRESS, HUB, OUTDIR, and optional PKTPW are flat directives. SFNetAdd32 shows
  the implicit link name DEFAULT. Normal one-network use remains supported.

SFToss32 v1.07 multi-link format:

  Global directives appear before the first [LINK name] section. Each link has
  its own ADDRESS, HUB, OUTDIR, optional PKTPW, NETMAILZONE rules, and AREA tags.

PASSWORD RULE
-------------

A link using a packet password has a populated line such as:

  PKTPW ********

SFNetAdd32 never shows or exports that value. It reports only:

  password=set

A link using no packet password must omit the entire PKTPW directive. It reports:

  password=none

This is invalid and must be rejected:

  PKTPW

A blank PKTPW is not the same as no password.

ROUTING MODEL
-------------

* Echomail ownership is selected by the exact Spitfire Net ID/AREA tag.
* NetMail ownership is selected by destination zone through NETMAILZONE.
* AREA and link comparisons are case-insensitive.
* The same AREA may not belong to two links.
* Zone ranges may not overlap between links.
* Duplicate link names, addresses, hubs, and OUTDIR paths are errors.
* In multi-link mode there is no invented default or fallback link.

CURRENT BETA BEHAVIOR
---------------------

SFNetAdd32 reads and validates the CFG, preserves unknown directives for its
report, and leaves the production file unchanged. It does not yet assign a new
.NA import to a named link or generate the final AREA addition plan.

Compare the SFNetAdd32 summary with:

  SFTOSS32.EXE -check

The link count, names, addresses, hubs, output directories, password states,
AREA counts, and NetMail zone rules should agree.

LEGACY TO MULTI-LINK
--------------------

The beta does not automatically convert a legacy CFG. A second network requires
reviewed conversion of the complete link portion into named [LINK ...] blocks.
Do not mix legacy flat link directives with named link sections.
