ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #msdos
Load relocatable MS-DOS drivers and TSRs into Upper Memory Blocks with DEVICEHIGH and LOADHIGH after enabling UMBs to free conventional memory below 640 KB.
Learn how MS‑DOS uses CONFIG.SYS and AUTOEXEC.BAT to load drivers and set environment, with a concrete example, trade‑offs, and a safe‑change checklist.
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
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
Goal: Identify the rule that MS‑DOS 6.22 uses to decide which DEVICEHIGH‑loaded device drivers remain in upper memory blocks when the total requested UMB space exceeds the amount available from EMM386. Constraints/uncertainty: The placement varies with the order of DEVICEHIGH lines in CONFIG.SYS, the presence of LOADHIGH programs, the dynamic fragmentation o