SFTOSS32 v1.05 - INSTALLATION AND UPGRADE
=========================================

FRESH INSTALL
-------------
1. Back up the complete Spitfire MESSAGE directory.
2. Create a directory for SFToss32.
3. Copy SFTOSS32.EXE and SFTOSS32.CFG into it.
4. Edit SFTOSS32.CFG with the real Spitfire, mailer and FTN values.
5. Confirm WORKDIR points to the directory containing SFWHOSON.DAT.
   The default is CONFDIR\WORK.
6. Take every Spitfire node offline.
7. Run:

       SFTOSS32.EXE -check

8. Do not proceed until -check passes.
9. Test inbound processing:

       SFTOSS32.EXE -toss

10. Test one outbound echomail message:

       SFTOSS32.EXE -scan

11. Confirm the mailer transfers the resulting bundle and verify the message
    on another connected system before automating the commands.

UPGRADE
-------
1. Back up the MESSAGE directory.
2. Keep the existing working SFTOSS32.CFG.
3. Rename the prior executable as a rollback copy.
4. Replace only SFTOSS32.EXE.
5. Run SFTOSS32.EXE -check with all nodes idle.
6. Run one inbound and outbound smoke test.

AUTOMATION
----------
SFToss32 itself verifies node state and uses SFTOSS.BSY, but scheduled tasks
should still avoid times when callers are normally online. The maximum wait
for busy nodes is finite; a run aborts rather than touching a live message
base indefinitely.

BACKUPS AND PACKING
-------------------
SFPCKMSG does not create a backup. Before packing a conference, back up the
MESSAGE directory and take every node offline. After packing, run -check
before tossing or scanning again.

PASSWORD SAFETY
---------------
Do not share an edited configuration, packet header, or unredacted log in a
public support channel. Packet and AreaFix passwords may appear in them.
