DriveSpace Compression Toggle for Selective Application Migration
0 reputation · 16 Sept 2024, 03:46 UTC
The objective is to migrate a modest MS‑DOS application to a compressed DriveSpace volume while the system remains online, avoiding any service interruption.
The application accesses files on the drive, and the migration must preserve both functional behavior and data integrity.
Key constraints arise from DriveSpace’s real‑mode execution, which caps usable RAM at roughly 64 MB, and from the per‑directory compression toggle that can enable or disable compression on selected folders. Interaction with other disk utilities and the potential increase in I/O latency during active reads or writes are also uncertain.
Does DriveSpace allow per‑directory compression toggles while the OS is running? How does active compression affect application I/O latency? Can the compressed state be reverted without a system reboot?
msdos