SFNetAdd32 v0.4b Beta 1 - Testing and Bug Reports
=================================================

This is a public beta. The safest first test is completely read-only.

RECOMMENDED TEST
----------------

1. Back up every node's SFMCONF.DAT and the shared MESSAGE directory.
2. Open Advanced Tools and select a copy or the live SFTOSS32.CFG.
3. Confirm the CFG is identified as Legacy single-link or Multi-link.
4. Confirm password states appear only as set or none.
5. Compare link names, addresses, hubs, output paths, zones, and AREA counts with:

       SFTOSS32.EXE -check

6. Scroll, resize, maximize, and switch tabs with populated reports.
7. Run Wizard Mode's read-only inspection.
8. Optionally import an existing .NA file to confirm duplicate tags are blocked.
9. Optionally import a future-network .NA and continue through Dry Run and Safety.
10. Stop before entering uppercase YES unless a real append is intended.

PLEASE INCLUDE IN A REPORT
--------------------------

* Windows version and 32-bit/64-bit host information.
* Whether SFNetAdd32 is running locally or through mapped/UNC paths.
* Legacy or multi-link CFG format.
* Link and AREA counts reported by SFNetAdd32 and SFTOSS32 -check.
* The exact step and message shown when the problem occurred.
* Whether the issue repeats after restarting the program.
* An exported report only after confirming it contains no private information.

Never publish or send a live CFG containing an actual packet password.

VALIDATION STATUS
-----------------

The parser and unchanged writer path were runtime-tested by the project owner on
Windows XP in the Test 1a build. Tests included a live FidoNet/Zer0Net CFG,
password set/none handling, multi-node mismatch blocking, duplicate .NA blocking,
and a future-network dry run through the Safety page. The public Beta 1 EXE was
rebuilt only to change release-label text; static, parser, writer, and
reproducible-build checks passed.
