Inside the case: a few different jobs
The CPU executes instructions. RAM holds data in active use. A hard drive or SSD stores files for longer. A network interface communicates, while the motherboard and buses connect the parts.
Think of memory as a workbench and storage as a filing cabinet. The analogy has limits: a CPU is not a thinking person, and modern computers have multiple cores and other processors, such as GPUs, that share work.
Opening a photograph involves reading its file, using memory while processing it, decoding it, and presenting the result on a display.
Take this with you · Free disk space is not the same as available memory for running applications.
Power on: a chain of handoffs
After power is applied, firmware such as UEFI initializes hardware and finds a boot option. A boot loader helps load the operating system, which starts services and the login interface.
The entire operating system is not stored inside a tiny boot sector. For now, follow the handoff from firmware to a loader to the system. A failure at one step can stop the computer before a desktop appears.
A computer that lights up but never reaches the desktop has a different problem from an application that won't open on an already running desktop.
Take this with you · Report which screen you reached, the exact message, and what changed beforehand.
The operating system coordinates the work
An operating system manages files, schedules processes, and communicates with devices through drivers. Windows, macOS, and Linux offer different interfaces but share these basic responsibilities.
A program is stored code or an executable. A process is a running instance. One application can start several processes, and closing a window may leave background work running.
Task Manager or Activity Monitor shows running processes. Deleting a desktop shortcut removes an entry point, not necessarily the installed application.
Take this with you · Give AI your operating system when asking for instructions, and distinguish a file from a running process.
From stored code to a running program
To start a program, the system maps or loads the code and data it needs into memory, then executes instructions. It need not copy the entire program into memory at once. Think of it as preparing a workspace before doing the work.
A visible change is not automatically a saved change. Text in an editor or tasks on a page may exist only in memory. Keeping them for later requires writing to a file, browser storage, a database, or another persistent destination.
Your new task appears immediately. But if the program only changes memory, reloading the page may lose the task.
Take this with you · Seeing a change and saving a change are two separate things to check.
What happens when the workbench fills up?
Open a few example applications and watch the memory blocks. Restart and compare what disappears with what remains on disk.
Opening apps uses memory without automatically deleting stored files.
The blocks and slowdown threshold are teaching aids, not predictions of real device performance.
Slowdowns, scheduling, and restarting
The system schedules many tasks. A single core can alternate between them, while multiple cores can work in parallel. Memory pressure may cause more disk swapping; busy processors, slow disks, network problems, and software defects can also cause delays.
Restarting rebuilds the running state and may clear a stuck process or a temporary problem. It does not add memory or repair every software or hardware fault. Save important work first.
“It slows down with video editing and twenty tabs open, then improves when I close the editor” is more useful than “my computer is bad.”
Take this with you · Record when the issue occurs, what it affects, and which actions change it.
A webpage keeps your new task only in memory. What is most likely when you reload it?
Choose an answer before reading the explanation.
A friend says their list disappears on refresh. Help describe the observation so AI can explain possible causes.
Think first, then uncover help as needed. Later chapters expect more complete descriptions and clearer checks.
Bring this chapter's context to your AI. Going deeper is optional; you can keep reading without it.
Explain memory and storage with a desk and filing cabinet, including the limits of the analogy.
One approach you can make your own
I'm learning computers and AI-assisted programming from scratch. In this chapter I learned: Computer：Distinguish temporary memory from saved files；Connect startup, processes, and running a program；Describe a slowdown using observations rather than a guessed cause Explain memory and storage with a desk and filing cabinet, including the limits of the analogy. Check my understanding first. Explain one small question at a time with a concrete example and the limits of any analogy. Ask a scenario question, then adapt to my answer. Distinguish facts, guesses, and uncertainty; suggest hands-on ways to check. Confirm the version before giving tool-specific advice, and don't invent features or references.
Complete this chapter
Mark the sections as read, finish the experiment, and pass the scenario check to record completion. You can visit the next chapter at any time.
Read the original references
This is an introduction. These official resources help you check details and explore further.
Linux kernel · Memory management conceptsThe hardware and operating system are ready. Next, discover how a person expresses an idea as a program.