SFPACK32 v0.6.0 Beta 1 - Known Limitations
==========================================

1. SFPACK32 does not shut down Spitfire or prevent new caller connections.
   Every node must be offline before /WRITE.

2. The program does not read SFEVENTS.DAT. The sysop must confirm Event M is
   disabled.

3. This version does not automatically warn when SFPCKMSG.COM or the built-in
   Pack Message Base menu option is present. Remove both legacy paths manually.

4. Structural damage is handled conservatively. Conferences with DAT overlaps,
   unreferenced DAT, orphan replies, invalid record sizes, or validation errors
   may be blocked rather than repaired.

5. This phase purges only Deleted=1 messages. It does not implement the original
   /OLD, /SIZE, /POT, /POU, or /PRM policies.

6. Backups are mandatory and are stored below <HOME>\SFPACK32-BACKUPS. The
   backup location is not configurable in this version.

7. A crash can leave MESSAGE\SFTOSS.BSY. Confirm neither SFPACK32 nor SFToss32
   is running before deleting a stale marker manually.

8. Timestamped backups can consume disk space. Keep them through validation,
   then archive or remove older copies manually.

9. /TESTCOPY remains available for isolated copies. It refuses the exact live
   C:\SF location and requires SFPACK32_TESTCOPY.OK in the test home.
