SFNetAdd32 v0.4b Beta 1
=======================

Release date: August 4, 2026

SFNetAdd32 is a native 32-bit Windows utility for safely inspecting and
appending Spitfire v3.7 message conferences. It includes a guided Wizard Mode,
read-only inspection, backups, dry runs, offline safety checks, verification,
and rollback protection.

This beta also reads the SFToss32 v1.07 named multi-link CFG format while
remaining compatible with the older flat single-link format. The live
SFTOSS32.CFG is never modified.

INSTALLATION
------------

1. Create a writable folder such as:

       C:\SFNETADD32

2. Extract the entire ZIP into that folder. Do not run the program from inside
   the ZIP.

3. Keep these two files together:

       SFNetAdd32.exe
       SFNetAdd32-profiles.ini

4. Run SFNetAdd32.exe. No installer is required.

The program may create SFNetAdd32.cfg and SFNetAdd32.log in its own folder.

QUICK START
-----------

For normal conference work:

1. Start Wizard Mode.
2. Enter the number of Spitfire nodes and confirm each node path.
3. Confirm the shared MESSAGE directory.
4. Run the read-only inspection.
5. Choose or confirm a backup location.
6. Import the FTN .NA area list.
7. Review every proposed conference name and setting.
8. Run the dry run and safety check.
9. Stop before the uppercase YES page unless you deliberately intend to write.

For SFToss32 v1.07 CFG inspection:

1. Open Advanced Tools.
2. Select the SFTOSS32.CFG file on the Setup page.
3. Review the Report page.
4. Confirm link names, addresses, hubs, output paths, zone rules, AREA counts,
   and password states.
5. Compare the summary with SFTOSS32.EXE -check.

Packet passwords are shown only as "set" or "none". A link with no packet
password must omit the PKTPW line completely; a blank PKTPW line is an error.

BEFORE ANY REAL COMMIT
----------------------

* Make a current backup of the shared MESSAGE directory.
* Confirm every configured node's SFMCONF.DAT matches.
* Close all Spitfire node windows and ensure no callers are active.
* Stop SFToss32, Internet Rex, and every other mailer or tosser.
* Confirm SFTOSS.BSY is absent.
* Run the final safety check immediately before writing.
* Read the complete dry-run plan.
* Enter exact uppercase YES only when the append is intentional.

SFNetAdd32 automatically creates a transaction backup of every configured
node's SFMCONF.DAT before a commit. It appends new conference records only; it
does not insert, delete, renumber, pack, or overwrite existing message bases.

After a successful append, start Node 1 with Spitfire's Test Files Upon Boot set
to Yes so Spitfire can create the new empty SFMSGxx files. Shut Node 1 down and
run SFNetAdd32's final inspection before restoring normal service.

RUNNING FROM ANOTHER WORKSTATION
--------------------------------

Mapped drives and UNC paths may be used. File-based checks such as SFWHOSON.DAT
and SFTOSS.BSY still work over the network. Process detection sees only the
computer running SFNetAdd32, so remote Spitfire nodes, SFToss32, Internet Rex,
and other mailers must be stopped and verified manually on the BBS host.

BETA 1 MULTI-LINK BOUNDARY
---------------------------

This is the multi-link parser-foundation beta. It reads and validates legacy
and v1.07 multi-link CFG files, but Wizard Mode does not yet ask which named link
owns a newly imported .NA list and does not yet generate final copy-and-paste
AREA additions. Production SFTOSS32.CFG writing is intentionally not included.

MORE INFORMATION
----------------

The docs folder contains:

  WHATS_NEW.txt                 Changes in v0.4b Beta 1
  BETA_TESTING.txt              Safe testing and bug-report information
  KNOWN_LIMITATIONS.txt         Current beta boundaries
  SAFETY_AND_BACKUPS.txt        Detailed write-safety procedure
  SFTOSS32_MULTI_LINK_NOTES.txt Multi-link and password behavior
  LICENSE.txt                   License and compatibility notice
  SHA256_MANIFEST.txt           Package file hashes

The examples folder contains safe sample CFG and .NA files. Complete source and
tests are under source; ordinary sysops do not need that folder to run the tool.
