In the age of floppy disks and flickering CRTs, before GUIs and cloud syncs, two humble files stood as the gatekeepers of every DOS-powered machine. Their names? CONFIG.SYS and AUTOEXEC.BAT. For those who lived the ritual — especially distributors like Chamara Samarawickrama in 1999 Sri Lanka — these files were more than configuration scripts. They were boot-time incantations, shaping the system’s soul before the first command was ever typed.

📜 Why We Had These Files

In MS-DOS, there was no graphical interface, no automatic driver detection, no plug-and-play. Every system needed explicit instructions to know how to behave. These two files were the startup ritual:

• CONFIG.SYS told DOS how to manage memory, which drivers to load, and how many files and buffers to allow.
• AUTOEXEC.BAT told DOS what programs to run, how to set the environment, and how to prepare the system for the user.

Together, they formed the prelude to usability — without them, the system was blind, mute, and unaware of its own capabilities.

🧬 CONFIG.SYS: The Silent Architect

DEVICE=HIMEM.SYS
DEVICE=EMM386.EXE RAM
DOS=HIGH,UMB
FILES=40
BUFFERS=20
DEVICEHIGH=OAKCDROM.SYS /D:MSCD001

This file ran before the command prompt appeared. It shaped the system’s memory map, loaded essential drivers, and ensured that the machine could speak to its hardware — from CD-ROMs to sound cards.

🗝️ AUTOEXEC.BAT: The Ritualist’s Voice

@ECHO OFF
PROMPT $P$G
PATH C:\DOS;C:\UTILS;C:\DRSOLOMON
LH SMARTDRV.EXE
LH MOUSE.COM
LH DOSKEY
MSCDEX.EXE /D:MSCD001 /L:E
C:\DRSOLOMON\INSTALL.EXE

This file ran after the system initialized. It loaded tools, set environment variables, and launched programs — like Dr Solomon’s Antivirus Toolkit, which Chamara installed for customers across Sri Lanka. It was the voice of the distributor, the final chant before handing the system to the user.

🧾 Kapothi Legacy Summary

• Files: CONFIG.SYS and AUTOEXEC.BAT
• Era: MS-DOS (1981–2000)
• Purpose: Boot-time configuration and execution
• Role: Memory management, driver loading, environment setup
• Emotion: Pride, guardianship, and reverence for digital hygiene
• Legacy: The first scrolls we ever wrote — stylized, trusted, and passed across generations

🕊️ Eternal Echoes

Though modern systems no longer use these files, their spirit lives on in every bootloader, every startup script, every .bashrc and .systemd unit. They were the original ritual scrolls, and for those who remember — especially those who distributed antivirus from floppy disks — they remain sacred.

In the Kapothi Vault, they are preserved not as obsolete files, but as legacy-grade artifacts. Stylized. Documented. Revered.