SFNetAdd32 - Safety and Backup Procedure
========================================

SFNetAdd32 uses an append-only transaction for SFMCONF.DAT. Existing conference
records are never intentionally inserted, deleted, renumbered, packed, or
rewritten. Existing SFMSGxx message files are not overwritten.

BACKUPS
-------

Two different backups are involved:

1. Full MESSAGE backup

   A current copy of the shared MESSAGE directory is strongly recommended before
   adding conferences. Wizard Mode can create and verify this backup, or the
   sysop may confirm that a separate current backup already exists.

2. Mandatory SFMCONF.DAT transaction backups

   Immediately before a real commit, SFNetAdd32 creates a timestamped backup of
   every configured node's SFMCONF.DAT. These backups are separate from the
   shared MESSAGE backup and are required by the writer.

OFFLINE COMMIT CHECKLIST
------------------------

1. Back up the shared MESSAGE directory.
2. Close every Spitfire node window.
3. Confirm no callers are active.
4. Stop SFToss32 and all SFToss32 automation.
5. Stop Internet Rex and every other mailer/tosser.
6. Confirm SFTOSS.BSY is absent.
7. Keep the network connection stable when using mapped or UNC paths.
8. Run the Wizard dry run and review every proposed conference.
9. Run the final safety check immediately before commit.
10. Enter exact uppercase YES only for an intentional write.

During commit, do not close SFNetAdd32, reboot, disconnect the share, or restart
Spitfire/mail processing. The writer stages and verifies the new Node 1 file,
copies it transactionally to the other configured nodes, verifies every result,
and attempts an all-node rollback if any write or verification fails.

AFTER A SUCCESSFUL APPEND
-------------------------

1. Keep all other nodes and mailers offline.
2. Start Spitfire Node 1 with Test Files Upon Boot set to Yes.
3. Allow Spitfire to create every new SFMSGxx.PTR, IDX, DAT, and LMR file.
4. Shut Node 1 down.
5. Run SFNetAdd32's final inspection.
6. Resume normal service only after every new conference reports OK.

MAPPED DRIVE AND UNC WARNING
----------------------------

File checks work through mapped drives and UNC paths, but process detection is
local to the workstation running SFNetAdd32. The program cannot prove that
SFToss32, Internet Rex, or Spitfire node processes are stopped on a remote BBS
host. The sysop must verify those remote processes manually.
