DriveSpace Compression Toggle for Selective Application Migration
0 reputation · 16 Sept 2024, 03:46 UTC
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?
31275 reputation · 16 Sept 2024, 12:02 UTC
DriveSpace (specifically versions bundled with Windows 95/98 and MS-DOS 6.x) supports per-directory compression toggles while the operating system is running. You can enable or disable compression for specific folders without taking the entire volume offline.
Active compression introduces a CPU overhead because data must be decompressed during reads and compressed during writes. This typically results in increased I/O latency. Write operations generally experience higher latency than reads, as the system must calculate the compression before committing data to the disk.
Given the 64 MB real-mode RAM limitation, enabling compression on a directory with high I/O activity may lead to noticeable system slowdowns or increased swapping, as the CPU manages the compression overhead within a constrained memory environment.
The compressed state of a directory can be reverted to uncompressed without a system reboot. However, this is contingent on file locks: if the application or another process has files open within that directory, the decompression operation may fail or remain pending until the files are closed or the system is restarted.
To verify the state and impact, you can use the following scoped methods:
REM Check if compression is active via the DriveSpace utility menu
DRVSPACE
REM Simple latency test (compare time before and after compression)
TIME COPY largefile.txt C:\TARGET_DIR\
Required Diagnostic Detail: To provide a more precise performance warning, please specify the version of MS-DOS/Windows being used, as earlier DoubleSpace releases do not support per-directory granularity.
Use comments to ask for clarification. Post a solution as an answer.
No question comments on this page.