ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #msdos
Explore the engineering trade-offs of MS-DOS FAT16, specifically how cluster sizing affects disk capacity versus internal fragmentation and slack space.
Avoid silent failures in MS-DOS automation by using COPY /B for binary integrity and explicit ERRORLEVEL checks to ensure your backups actually completed.
Learn how to resolve 'Insufficient memory' errors in MS-DOS by managing the 640KB conventional memory limit using HIMEM.SYS, EMM386.EXE, and UMB relocation.
Describes how the INT 21h API provided a stable interface for file and process services, enabling applications to run unchanged across IBM PC‑compatible hardware.
The goal is to ascertain whether MS‑DOS offers any built‑in means to interpret FAT directory timestamps as UTC or to apply a timezone offset when files are read or written across different regional settings. MS‑DOS stores file creation, modification and access times as local‑time values in FAT entries, derives those values from the BIOS real‑time clock via I
When protecting important files from accidental change on an MS-DOS system, the designer must decide whether to rely on the READ-ONLY attribute set with ATTRIB.EXE or to load SHARE.EXE and use its deny‑write locking mode. The attribute method is simple and requires no resident software, but it is advisory and can be defeated by any program that clears the fl
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 R
When running DOS games or legacy applications that require at least 50 KB of conventional memory, the decision between using DEVICEHIGH in CONFIG.SYS and LOADHIGH in AUTOEXEC.BAT becomes critical. Both directives aim to relocate code into Upper Memory Blocks (UMBs) when HIMEM.SYS and an UMB provider such as EMM386.EXE are present, but they differ in ordering
The BACKUP and RESTORE utilities in MS-DOS 6.22 are used to archive file data and directory structures into sequential .BAK files. While these tools maintain standard file metadata, behavior varies when restoring archives to disks with different FAT sizes (such as transitioning from 16-bit to 32-bit FAT). There is uncertainty regarding how the RESTORE comman