"First Day" — What is an Operating System?
Your first day as an IT intern at Meridian Dynamics. Before you touch a server, you need to understand what makes a computer actually work.
Why Do Operating Systems Exist?
Imagine a building with no traffic lights, no elevators, no security guards, and no rules about who can use which room. Everyone fights for the stairs, people walk into restricted areas, and two people try to use the same printer at the same time — chaos.
That's what a computer is without an operating system. Raw hardware: a CPU that can execute instructions, RAM that can store data temporarily, a disk that can save files permanently, and devices like keyboards and screens. But nothing to coordinate them.
An operating system (OS) is the software that sits between you and the hardware. It's the traffic controller, the security guard, and the building manager all in one. Every time you open a program, save a file, or print a document — the OS is making it happen.
- Process Management — Decides which programs get CPU time and when. Your browser, your Word doc, and Windows itself all need the CPU, and the OS shares it fairly (thousands of times per second).
- Memory Management — Gives each program its own chunk of RAM so they don't overwrite each other. When RAM fills up, it uses disk space as overflow ("virtual memory").
- File System Management — Organizes data on disk into files and folders. Keeps track of where every byte is stored using structures like the MFT (Master File Table).
- Device Management — Talks to hardware (keyboard, screen, network card, USB drives) through drivers, so programs don't need to know hardware details.
- Security & Access Control — Decides who can do what. User accounts, passwords, permissions, encryption — the OS enforces all of it.
Before Operating Systems: The Dark Ages
In the 1950s and 60s, computers had no OS at all. Programmers loaded programs one at a time using punched cards. If your program crashed, the entire machine stopped. If you needed to print, you wrote code that directly controlled the printer's motors.
This was called bare metal programming — you talked directly to the hardware. It was powerful but incredibly tedious and fragile.
Batch processing came next: an operator would collect jobs (stacks of cards), feed them in sequence, and collect output. But there was no interaction — you submitted your program and came back hours later for results.
The breakthrough came with time-sharing systems in the 1960s. MULTICS (1964) and then UNIX (1969) let multiple users share one computer simultaneously. The OS rapidly switched between users so fast that each person felt like they had the machine to themselves.
The Evolution: From UNIX to Windows
| Era | System | Key Innovation |
|---|---|---|
| 1969 | UNIX | Multi-user, multi-tasking, portable C code |
| 1981 | MS-DOS | Personal computer OS, command-line only |
| 1985 | Windows 1.0 | Graphical shell on top of DOS |
| 1991 | Linux | Open-source UNIX clone, free forever |
| 1993 | Windows NT 3.1 | True 32-bit kernel, protected memory, preemptive multitasking |
| 2001 | Windows XP | NT kernel for consumers, USB plug-and-play |
| 2015 | Windows 10 | "Last version of Windows", rolling updates |
| 2021 | Windows 11 | TPM 2.0 requirement, security-first design, Secure Boot mandatory |
The key insight: modern Windows is built on the NT kernel (designed by Dave Cutler in 1993), not on DOS. Every version of Windows since XP runs on NT technology. This is why Windows is stable enough to run servers with 99.99% uptime — it was designed for enterprise from the start.
The Three-Layer Model
Every computing device follows this fundamental architecture:
Applications never talk directly to hardware. They ask the OS, and the OS talks to hardware through drivers. This isolation is what makes computing safe and stable — one bad app can't crash the whole machine (usually).
Architecture Diagram: Hardware → OS → Applications
Click any layer to explore what lives there and why it matters.
📅 OS Evolution Timeline
X-Ray Mode: What Happens When You Power On?
Watch the boot process step by step. The diagram highlights which component is active while the terminal shows what's happening.
Observation Lab: Your First Day at Meridian Dynamics
winver to check your Windows version. What edition and build number do you see?systeminfo to see detailed system information. Find the OS name, version, and system type.hostname to confirm your workstation name matches what Priya told you.whoami to see which account you're logged in as.ipconfig to check your network configuration. What's your IP address and default gateway?