Computer Science — Chapter 4

Software & Operating Systems — System vs Application, Windows, Linux and Utilities

Why this chapter matters: Chapters 1–3 taught you the machine — its history, its devices, its memory. This chapter teaches you what makes the machine do anything: the software. The papers ask this family in a very particular way — usually as “which type of software is this?” or “which of the following is an operating system?” — so the whole chapter is built around telling the two families apart at a glance. Our verified banks hold 26 questions matching this chapter directly by question text (software types 9, operating systems 13, utilities 4); many more hide in option lists, which is exactly why the distinctions below, not the count, are what earn the marks. The MS Office detail behind the “packaged software” example lives in Chapter 5 (MS Office); the browsers and search engines behind the “application” examples live in Chapter 6 (Internet & Networking).

How this chapter relates to the rest of Computer Science: the software section of Lecture 3 (Section 9) and its GUI/booting section (Section 10) are taught here, in full. Nothing from Chapters 1–3 is re-taught: hardware, memory and data units are assumed, and the BIOS abbreviation from Lecture 3’s rapid-fire list is filed with the abbreviations in Chapter 7.

1. What software is — and the two families

Software is a set of instructions given to a computer for a specific task. Without it, the hardware of Chapters 2–3 is a dead box: software is what tells the CPU what to do. There are two types, and the papers test the split constantly:

The capsule’s own question nails the definition: “which type of software manages hardware, controls system operations, and provides a platform for application software?” → system software. And “the software that behaves like a traffic police” (directing everything, controlling the flow) is the operating system — the bank’s own image for the OS’s job.

2. Application software — custom-built vs packaged

Application software comes in two kinds (Lecture 3’s distinction, asked directly):

• Custom-built — made for one specific user or business. The lecture’s example: a sweet shop’s billing screen, with samosa and chicken-roll buttons fixed on screen — the counter man just clicks “5 samosas” and the receipt prints. No typing, no general purpose: it fits one shop and nobody else.
• Packaged — made by one company for all users. The example: MS Office by Microsoft — MS Word, MS Excel and MS PowerPoint are all packaged software, sold to everyone in the same box. When a paper asks “MS Access is which type of software?” it is testing this same family: Access is part of the packaged MS Office suite.

Two further application labels the papers use:

• Horizontal market software — the most commonly used software in industry. Asked as “most commonly used software in industry / horizontal market software” → choose horizontal (not vertical). Horizontal software serves many industries (a word processor, a spreadsheet); vertical software serves one industry (a hospital system, a bank system).
• Free software = public domain software. Asked repeatedly, in both wordings. The capsule’s version: the software licence type that is free of cost with no copyright restrictions is public domain software. Do not confuse it with shareware (try-before-you-buy, still copyrighted) or freeware (free to use, but the copyright stays with the author).

3. System software I — the operating system

The operating system (OS) is the most common type of system software, and the papers’ first question about it is always its function: what is the primary function of an operating system? → it manages the computer’s hardware and software resources and provides the platform on which applications run. Its jobs, in the order the papers imply them:

1. Process management — deciding which program runs when (and what happens when two programs want the same resource at once — that jam is a deadlock: processes waiting on each other in a circle, so none can proceed).
2. Memory management — giving each program its share of RAM (Chapter 3) and taking it back.
3. File management — organising storage into files and folders you can find again.
4. Device management — talking to the keyboard, printer, disk and screen through drivers (Section 6).
5. User interface — giving you the desktop or the command line to work through (Section 5).

The kernel is the part of the OS that does the most fundamental control: the bank asks “which part of an operating system is responsible for the most fundamental control over all the computer’s hardware devices?” → the kernel. Think of it as the OS’s core — everything else in the system talks to the hardware through it. Checkpoints are the OS’s safety snapshots: points at which the system’s state is saved, so work can be recovered after a failure instead of restarted from scratch.

Types of operating system the papers assume you can recognise:

• Single-user — one user at a time (classic desktop Windows is the textbook example; Windows 95 is keyed as a single-user OS).
• Multi-user — many users at once (Unix and its family; servers).
• Real-time — deadlines must be met, on time, every time (industrial control, flight systems). The bank contrasts hard real-time (a missed deadline is a failure) with soft real-time (a missed deadline degrades, but does not break, the system).

4. The operating systems that get asked — Windows, Unix, Linux

Windows (Microsoft)

• Made by Microsoft — the papers key it to Bill Gates (Microsoft’s co-founder), so “Windows → made by Bill Gates” is the bank answer.
• The version line (the papers test which names are real and which are not):

• Windows 9 was never made — the single most asked Windows trap: “which Windows is not a Windows?” → Windows 9. (Windows 96 is likewise not a version — a cancelled codename, Nashville, is sometimes mistaken for it.)
• Before Windows, the PC world ran on MS-DOS (Microsoft Disk Operating System) — a command-line OS, introduced by Microsoft for the IBM PC in 1981, and the first widely installed PC operating system. The bank asks exactly this: “in 1980, IBM chose which company to provide the operating system for its upcoming PC?” → Microsoft.
• Open-source operating system? The bank’s question — “which of the following is an open-source operating system?” — is answered by the next section, not by Windows: Windows is proprietary (closed, paid, Microsoft-owned).

Unix

• Made by Dennis Ritchie and Ken Thompson at AT&T Bell Labs (begun 1969, first released 1970; rewritten in C, the language Ritchie created, in 1972–73). The lecture’s hook: Ritchie is “the C-language man”.
• A multi-user, multitasking system built for stability and for servers — the ancestor of the whole family below. The bank’s deeper Unix question (“in Unix, which system call creates the new process?”) belongs to specialist papers; for one-paper purposes, Unix = Thompson + Ritchie + Bell Labs + multi-user is the complete answer set.

Linux ★

• Made by Linus Torvalds — announced 25 August 1991 while he was a student at the University of Helsinki, as a free operating-system kernel for the 386 PC.
• Linux is, strictly, the kernel — the core. A complete “Linux system” is that kernel plus GNU utilities and other software, packaged as a distribution (Ubuntu, Debian, Red Hat and the like). The papers simplify this to: Linux = open-source operating system.
• Open-source means the source code is free to use, study, change and share (under the GNU General Public Licence) — the opposite of Windows’ proprietary model, and the reason Linux powers most servers and, through Android (developed by Google, built on the Linux kernel), most phones. The bank asks “Android OS [was] primarily developed by?” → Google.

5. How you talk to the machine — GUI, command line, booting

• GUI = Graphical User Interface. When Windows opens and you see icons — My Computer (later “Computer”, now “This PC”), Recycle Bin, Control Panel — that icon-and-mouse world is the GUI. The bank asks “GUI stands for?” more than any other expansion in this chapter.
• Command prompt (CLI) — no icons; you type the instructions. The first generation of computers worked this way, and MS-DOS is the classic example.
• Booting = the process when you start a computer. The bank’s version: “a computer cannot ‘boot’ if it does not have the…?” → the operating system (loaded from disk into memory at start-up; without it there is nothing to run). Spell it B-O-O-T-I-N-G — the papers ask the spelling as well as the meaning.
• Recycle Bin — deleted files go here first, and can be recovered from here. The lecture’s warning, worth repeating because it has cost marks: in one Assistant S&GAD paper, “Recycle Bin” was not among the options — and the correct answer was “none of these”. Read the options before assuming your first instinct is listed.

6. System software II — utilities and language translators

Utility programs are the helpful programs that keep the machine running. The lecture’s list, each item asked in some paper:

• Antivirus — protects against viruses and malware. McAfee is an antivirus (and Dr. Solomon’s is another bank-named one). The trap, asked as “which is NOT an antivirus?” → Oracle — Oracle is a database company, not an antivirus.
• Compression tools — WinZip, WinRAR — shrink big files for storage or sending, and expand them back on opening. The bank asks “which software is used for file compression?” → a compression tool.
• Disk management / disk cleanup / disk defragmenter — tidy the disk, free space, and reorganise scattered file fragments so the disk reads faster.
• Backup software — copies data elsewhere on a schedule (the lecture’s example: the 2 a.m. WhatsApp backup into email/Google Drive storage). The bank’s Windows 10 backup question sits here too.
• File management system — the organiser behind folders, copying, moving and deleting.
• Drivers — the translators between the OS and each hardware device (printer, graphics card); without the right driver, the device cannot talk to the system.
• Language translators — because the CPU understands only machine code, human-written programs must be translated:
  • Compiler — translates the whole program at once: its input is source code, its output is machine/object code (both phrasings are bank questions). A compiled program then runs without the compiler.
  • Interpreter — translates line by line, running each line as it goes.
  • Assembler — translates assembly language into machine code (the middle step between human-readable and machine code).

6A. Process management in depth & security — the OPC fold-in

This section is the One Paper Cracker Computer Science fold-in (Arslan Malik; 62 pages fully OCR-read, hidden_files/final-notes-intake/cs-opc-full.txt, 62/62 pages, no failures): the OS depth the lectures and capsules leave thin — process management, the deadlock conditions, the startup sequence, DOS and file systems, and the malware/security family. Bank-evidence note (read this before claiming a mark): no 🔁/⭐ mark is claimed for this section — nothing here meets either 🔁 limb. What the banks do show, counted by script hidden_files/goldmine-notes-count-cs-opc.py over 608 files / 58,098 questions, is a small, recent cluster: deadlock asked in 2026 PPSC computer-operator papers (“which is a necessary condition for a deadlock?”, “deadlock occurs when?”); firewall in three 2024–25 papers; public/private-key cryptography in 2026 computer-operator papers; virtual memory in 2026 papers; macOS’s maker in one 2019 paper. Those stems are counted separately here and are not folded into this chapter’s bankCount of 26. Everything else in this section is OPC/standard-reference material, taught unmarked — the same honest rule as the rest of the chapter.

6A.1 What the OS is for — the OPC framing, in standard terms

• The primary purpose of an operating system is the efficient use of hardware — the OPC one-liner that answers the bank’s “primary purpose of an operating system” question (asked in 2023–24 papers) in its shortest form. Section 3’s longer definition (manage resources, provide the platform) is the same answer expanded.
• The OS tells the computer how to use its components, and it creates virtual computers from physical hardware — the virtualization idea in one line: one physical machine, presented to each program as if it were its own machine. The bank’s virtual-memory questions (2026) sit here too: virtual memory extends RAM by using disk space, so programs larger than RAM can run; its primary purpose is letting more programs run than physical memory alone would allow.
• Mechanism vs policy: the OS separates mechanism (how something is done) from policy (which decision is taken) — a two-level implementation. Papers key this as the OS design principle, not as a function: do not list it among the OS’s jobs in Section 3.
• What is NOT a core OS function (exam framing): housekeeping tasks — compression and defragmentation — are performed by utilities, not by the core OS; and networking is not counted as a core OS function in this framing. Both traps exist because the Section 3 job list (process, memory, file, device, interface) tempts you to add them.
• System resilience is the ability to remain operational during failures — the OPC one-liner for the “why checkpoints exist” idea in Section 3, now named.

6A.2 Multitasking, single-tasking, and real-time — the three modes, completed

• Multitasking is the ability of an OS to run more than one program at the same time (desktop operating systems support it). It is the mode behind Section 3’s process management: the OS switches the CPU between programs so fast that they appear to run together.
• MS-DOS is command-driven and single-tasking: it cannot run more than one program at a time. That is the DOS contrast to multitasking, and the reason DOS belongs to the single-user, single-task era in Section 4’s table. Older PDA operating systems are keyed in the OPC notes the same way — generally not supporting desktop-style multitasking — which is exam framing for the PDA era, not a claim about modern phones.
• Real-time, completed: a real-time OS responds within very small time intervals — Section 3’s hard/soft distinction, now with the OPC examples: process-control systems and medical devices run real-time operating systems, because a late answer there is a failed answer.

6A.3 Deadlock, in full — the four Coffman conditions

Section 3 defined deadlock as processes waiting on each other in a circle. The 2026 papers go one step further and ask for a necessary condition. All four must hold simultaneously (Coffman, 1971 — verified against standard references):

• Prevention = break any one condition. That single rule answers every “how can deadlock be prevented?” variant: you never need to break all four, only one.
• Process queues, corrected: processes wait in queues (the ready queue and device queues) — but the PCB (process control block) is not a queue. The PCB is the per-process record the OS keeps (identity, state, resources held); queues hold the processes themselves. The OPC trick — “PCB queue does not belong to process queues” — is testing exactly that category error.
• Paging and fragmentation, paired: paging transfers data between secondary storage and main memory in fixed-size blocks (pages/frames), and increasing the page size increases fragmentation — specifically internal fragmentation, the wasted space in the last, partly-filled page. Fragmented files slow the computer down (Section 6’s defragmenter exists for this), and that slowdown is the symptom papers attach to fragmentation.

6A.4 The startup sequence — BIOS, POST, booting, login

• The first instruction on startup comes from the ROM BIOS. The BIOS is stored in ROM in the classic telling and in a flash-memory chip in modern machines — same job, newer storage: do not let the two OPC wordings look like two different things.
• POST (Power-On Self-Test) checks whether the essential hardware devices are connected and working. BIOS then loads the operating system from the hard disk into RAM.
• Booting = loading the OS into RAM; it does not include loading application programs. Applications load after the OS, never as part of booting. Authentication runs after booting and GUI loading — you log in to a running system, not to a booting one.
• Windows startup modes: the default is Normal Mode. Safe Mode loads minimum drivers only (the diagnostic mode). Turbo Mode is not a Windows startup mode — a planted option. Sleep mode reduces power consumption and is for leaving the computer for a short time.
• Firmware and versions, in one breath: firmware is software permanently stored in ROM (the programs stored in ROM are called firmware — the BIOS above is the example); a BETA version is a pre-released version of software; a bug is also called a glitch, and debugging is finding and fixing errors in code.

6A.5 DOS and file systems — the ladder papers still ask

• DOS filenames: maximum 8 characters (the 8.3 rule: 8 + 3-character extension). MS-DOS does not support long file names, and it allows the smallest file name. If the FAT is corrupted by a virus, DOS cannot retrieve data — the file allocation table is the map, and without the map the files are unreachable.
• DOS commands, the pair: external commands require additional files to operate (they live on disk as separate programs); VERIFY is not an external command (it is internal). LABEL is used to name a disk. System files are required for MS-DOS to run at all.
• FXZ is not a valid file system — the planted option in this family; if a file-system question offers FXZ, it is the “not a file system” answer.

6A.6 Utilities, completed — the OPC utility list

Section 6 named antivirus, compression, disk tools, backup, file management and drivers. The OPC list adds the working utilities papers name:

• Spooler — manages and coordinates queued print jobs (print jobs wait in a spool, not in a traffic jam at the printer).
• Windows Explorer — the OS’s file and folder manager; the file manager helps users locate, rename, move, copy and delete files. Disk Cleanup is a utility program; the disk scanner detects physical and logical disk problems. Add or Remove Programs is a utility program; the fax viewer is one too.
• Virus scanning is not a system tool (exam framing) — the OPC distinction: antivirus software is a utility program (Section 6), but virus scanning as a named “system tool” is not counted among the Windows system tools. Learn the pair, not either half alone.
• Software piracy is the illegal copying/downloading of software — the definition behind the antivirus story in Section 6A.7: illegally copied software is how viruses enter.

6A.7 Malware and security — the family, named and dated

• Malware = malicious software. A computer virus is an intentionally disruptive program that copies itself without permission — named for replication and spread, like a biological virus.
• Trojan horse — malware disguised as legitimate software: it looks useful and performs destructive acts. Worm — a self-replicating program that spreads on its own (it stops spreading when memory or disk space runs out, in the OPC framing). Logic bomb / time bomb — malware triggered by a condition or a date; the Michelangelo virus is the time-bomb example (trigger date 6 March). Note the category correction: the OPC notes loosely call the worm and the logic bomb “types of viruses” — in standard terms they are types of malware, not viruses, and this chapter teaches them that way.
• The dated names (standard-reference verified):
  • Brain (1986) — the first computer virus for the PC (MS-DOS boot-sector virus, spread on floppy disks; written in Lahore by brothers Basit and Amjad Farooq Alvi, originally as copy protection).
  • CIH / Chernobyl (1998) — one of the most destructive viruses, overwriting system files and in some cases corrupting the BIOS; named Chernobyl for the coincidence of its trigger date with the 26 April 1986 accident.
  • Melissa (1999) — a famous e-mail virus (Word macro, spread through Outlook address books).
  • ILOVEYOU (May 2000) — the most widely spread virus/worm of its era, arriving as an e-mail attachment and overwriting files while mailing itself to every contact.
• How viruses enter, and what does not spread them: viruses can enter through illegally copied software (Section 6A.6’s piracy line). A plain-text e-mail body alone cannot spread a virus — the danger travels in attachments and executable content, not in plain text itself. CD-ROM stopping is not a normal virus symptom — a planted symptom; slowness and file damage are, a stopped drive is not.
• The defences, each in one line: a firewall prevents unauthorized network access (asked in 2024–25 papers); hacking is unauthorized access to another system; cryptography secures data against attacks — the 2026 papers ask its public/private-key form (one key public, one private = asymmetric cryptography); encryption is scrambling data into unreadable form so only authorized users can read it, and a cryptosystem is used to secure messages; authentication is verifying a user’s identity (username-and-password checking is its common form); passwords are the most common access-control method; biometrics uses fingerprints and retinal scans; security patches fix operating-system weaknesses; spyware (Spybot in the OPC notes) secretly collects and sends user information; identity theft is collecting personal data by impersonation; a DoS (Denial of Service) attack blocks access using fake traffic. The OPC notes add that most computer crimes are committed by insiders — taught here as the notes’ exam framing, not as a measured statistic.

6A.8 The other operating systems and the Windows desktop, completed

• macOS (Apple): Mac OS was an early GUI-based desktop OS, and modern macOS is based on Unix — the Unix family of Section 4, with Apple’s desktop on top. The bank asks macOS’s maker (2019 paper) → Apple.
• IBM produced OS/2; Windows 2000 is suitable for client-server networks; Windows 3.1 does not support networking; P11 and Windows 9 are not operating systems (Windows 9 joins Section 4’s never-made list; P11 is the planted name beside it). .NET is Microsoft’s entry into the programming arena.
• The Windows desktop, named: the area containing My Computer, My Documents and Recycle Bin is called the Desktop; the desktop background is called wallpaper; the title bar appears at the top of an open window; right-click opens a shortcut menu; underlined menu letters are called hotkeys; icons are graphical symbols representing files or folders; the Run command is used to start programs; the Quick Launch toolbar is on the left side of the taskbar.
• Control Panel jobs: the system date and time can be changed from the Control Panel, as can user accounts, and the Add New Hardware option lives there. DIR does not show the full path of files; the Help menu is available from the Start button; in Windows 7, gadgets display weather, date & time and news (the Recycle Bin is not a gadget); WIN.INI stores Windows settings (legacy concept, exam-oriented).
• Application examples, corrected to their families: Microsoft Word is application software (Section 2); AutoCAD is application software used for architectural design; SPSS (Statistical Package for the Social Sciences) was developed by IBM; QuickTime is a media player and Windows Media Player is entertainment software; multimedia software combines text, graphics, audio, video and animation; Adobe Acrobat converts files into PDF format; Adobe Flash Player and Shockwave Player (1995) are multimedia software.

7. Master table — the whole chapter in one view

8. Rapid-fire one-liners

• Software → set of instructions given to a computer for a specific task.
• System software → manages hardware, controls operations, provides the platform; bridge between hardware and applications.
• Application software → the user’s task: Word, Excel, PowerPoint, browsers, games.
• Custom-built → one user/business (sweet-shop billing); packaged → one company, all users (MS Office).
• Horizontal market software → horizontal; free software → public domain software.
• OS primary function → manage hardware and software resources, provide the platform.
• Kernel → most fundamental control over hardware devices.
• Windows → Microsoft / Bill Gates; Windows 9 never made; Windows 8 has no Start button.
• My Computer → introduced in Windows 95.
• MS-DOS → Microsoft, IBM PC, 1981; command-line.
• Unix → Dennis Ritchie and Ken Thompson, Bell Labs, 1969; multi-user, multitasking.
• Linux → Linus Torvalds, 1991; open-source kernel; Android (Google) built on it.
• GUI → Graphical User Interface; command prompt → type, no icons.
• Booting → starting the computer; needs an operating system.
• Antivirus → McAfee; Oracle is NOT an antivirus.
• Compression → WinZip, WinRAR.
• Compiler → input source code, output machine code; interpreter → line by line.
• Section 6A rapid-fire: OS primary purpose → efficient use of hardware; virtual computers → one physical machine, presented as its own machine to each program; multitasking → more than one program at the same time; DOS → single-tasking, command-driven.
• Deadlock needs all four Coffman conditions: mutual exclusion, hold and wait, no preemption, circular wait — break any one and deadlock is impossible.
• PCB is a record, not a queue; larger page size → more internal fragmentation; paging → secondary storage ↔ main memory.
• Startup: ROM BIOS → POST → OS loaded into RAM; Safe Mode → minimum drivers only; booting excludes application programs.
• File systems: DOS → FAT16; Windows 95 → FAT32; modern Windows → NTFS (New Technology File System); DOS filename max → 8 characters.
• Malware: virus → copies itself without permission; Trojan → disguised as legitimate; worm → self-replicating; Brain → first PC virus, 1986; ILOVEYOU → most widely spread, May 2000; CIH/Chernobyl → 1998, BIOS corruption.
• Security: firewall → prevents unauthorized network access; hacking → unauthorized access; cryptography public + private keys → asymmetric; piracy → illegal copying/downloading.
• macOS → Apple, Unix-based; OS/2 → IBM; Windows 2000 → client-server; Windows 3.1 → no networking; P11 and Windows 9 are not operating systems.

9. Most-asked facts (from our verified past-paper banks)

• “Which one is / is NOT application software?” and “MS Access is which type of software?” — the software-types family (9 bank questions) is almost entirely this one distinction, asked with rotating examples. If the example serves the user, it is application; if it runs the machine, it is system.
• The OS function questions (13 bank questions): primary function, the kernel’s fundamental control, GUI’s expansion, the open-source OS, the IBM–Microsoft 1980 question, and the Windows 10 backup / Windows 95 My Computer questions. The kernel question and the GUI expansion are the two most repeatable single marks in the chapter.
• Utilities (4 bank questions): file compression and the compiler’s input/output pair, plus the McAfee/Dr. Solomon’s antivirus question. Small count, fixed wording — learn the four lines and they are free.
• What the count does not show: most Windows/Linux/Unix questions in the banks are phrased as “which of the following is…” with the names in the options, so they do not match a question-text count. The version line in Section 4 and the comparison table exist for exactly those questions — revise the names, not just the counted stems.

10. Traps & confusions

• System vs application: the test is who it serves. A word processor serves you (application); the OS serves the machine (system). MS Office is application software even though Microsoft also makes the OS — same company, different family.
• Custom vs packaged: custom = one customer (the sweet shop); packaged = everybody (MS Office). Do not reverse them under pressure — “custom” sounds special, and it is: specially made for one.
• Free vs freeware vs shareware: only public domain is free with no copyright restrictions. Freeware is free to use but still copyrighted; shareware is a trial that expects payment.
• Windows 9, Windows 96: neither exists. Microsoft jumped from 8 to 10; “96” was a cancelled codename, not a release. If either appears as an option to “which is not a Windows version?”, it is the answer.
• Windows 8’s missing Start button: 8 removed it; 8.1 brought it back. The paper asks about 8, so answer “no Start button” — do not let 8.1 blur it.
• Linux vs Unix: Linux is not Unix renamed — it is a new, open-source kernel (1991) built to behave like Unix. Unix itself is the older, proprietary Bell Labs system (1969).
• GUI vs command prompt: icons and mouse = GUI; typed commands = command prompt. MS-DOS is the command-prompt example; modern Windows is the GUI example.
• Oracle is not an antivirus: it is a database company. McAfee is. Papers plant Oracle in the antivirus list precisely because its name sounds technical.
• Compiler vs interpreter: compiler = whole program at once (input source code, output machine code); interpreter = line by line. The input/output pair is asked in both directions.
• Recycle Bin trap: if “Recycle Bin” is not among the options, the answer is “none of these” — not the next-most-plausible option.
• Deadlock’s “necessary condition” question: the 2026 papers ask for a necessary condition, not the definition — any one of the four Coffman conditions is a correct answer to that wording, and “all four hold simultaneously” is the answer to “when does deadlock occur?”.
• Virus vs worm vs Trojan vs logic bomb: a virus needs a host and copies itself into programs; a worm spreads alone; a Trojan does not replicate at all — it deceives. Papers that call all three “viruses” are using the loose OPC grouping; the standard categories above are what you learn.
• FAT ladder order: FAT16 (DOS) → FAT32 (Windows 95) → NTFS (modern Windows). Do not attach FAT32 to DOS or NTFS to Windows 95.
• Plain-text e-mail trap: plain text itself cannot execute code — but an attachment on a plain-text message still can. “Cannot spread a virus” is true of the body, never of the attachment.
• macOS is not Windows and not Linux: it is Apple’s system, Unix-based — so “macOS → Microsoft” and “macOS → open-source Linux” are both wrong, in opposite directions.
• DOS single-tasking vs Windows multitasking: if the question’s system runs one program at a time, it is DOS-era thinking even when the question does not name DOS.

11. Memory tricks (from the lectures, plus clean professional aids)

• The bridge test: picture system software as the bridge and application software as the traffic on it. If the question’s software is the bridge (manages hardware, provides the platform), it is system; if it crosses the bridge to do your job, it is application. The capsule’s own bridge question makes this the chapter’s master image.
• Traffic police: the OS “behaves like a traffic police” — it does not drive anywhere itself, it directs everything else. When a question uses that image, the answer is the operating system.
• The missing 9: Windows counts …7, 8, then 10. The gap is the answer: any question asking which Windows does not exist is answered by the number that was skipped.
• L for Linux, L for Linus, L for Libre: Linux’s three L’s — Linus made it, Libre (free/open) is its licence, and it Lives on servers and phones. Unix’s pair is R & T — Ritchie and Thompson.
• GUI = you see it: Graphical means pictures — if the question mentions icons (My Computer, Recycle Bin, Control Panel), you are looking at a GUI, and GUI expands to Graphical User Interface.
• PACKaged = PACKed for all: packaged software ships in one pack to everyone; custom software is tailored to one customer like a custom suit.
• MHNC — the deadlock four: Mutual exclusion, Hold and wait, No preemption, Circular wait. Say “MHNC” and check all four are present before calling anything a deadlock — miss one and it cannot be one.
• BIOS → POST → RAM: the startup chant — BIOS wakes, POST checks, RAM receives the OS. Applications arrive last, never during booting.
• FAT16 → FAT32 → NTFS: the file-system ladder climbs with Windows — 16 for DOS, 32 for 95, NT for now.
• Brain, Chernobyl, LoveLetter — 86, 98, 00: the malware years step two years apart — Brain 1986 (first), CIH 1998 (BIOS), ILOVEYOU 2000 (widest spread).

12. Visuals (site build specs)

• DIAGRAM — The two-layer software stack: hardware at the bottom, system software (OS + utilities + translators) as the bridge layer, application software on top, with the user above — the Section 1 table rendered as a stack, placed in Section 1.
• TIMELINE — The Windows line: 1985 (1.0) → 95 → 98 → XP (2001) → 7 → 8 (no Start button) → 10 → 11, with a visible gap where 9 would be, marked “never made” — placed in Section 4.
• COMPARISON INFOGRAPHIC — Windows vs Linux vs Unix: three columns (maker, year, licence, users) from the Section 4 table, with the open-source column highlighted — placed in Section 4.
• DIAGRAM — GUI vs command line: split screen — icons/desktop on one side, typed commands on the other — placed in Section 5.
• DIAGRAM — The deadlock cycle: four processes in a ring, each holding one resource and waiting for the next, with the four Coffman conditions labelled on the ring — placed in Section 6A.3.
• TIMELINE — The startup sequence: ROM BIOS → POST → OS into RAM → GUI → authentication, with Safe Mode and Sleep Mode as side branches — placed in Section 6A.4.

13. Practice this topic

• Practice set: 26 verified past-paper questions in the PPSC + FPSC banks are tagged to this topic’s sub-topics (software types 9, operating systems 13, utilities 4) — the site serves them as this chapter’s practice set, with the IBES Computer capsule questions behind them. Note for the set: most Windows/Linux/Unix questions in the banks put the names in the options rather than the stem, so the served set also draws the option-name questions from this chapter’s tables (Section 4’s version line and comparison table) — revise the names, not just the counted stems. The MS Office function and shortcut questions are not in this set; they belong to Chapter 5. The browser and search-engine questions are not in this set; they belong to Chapter 6. Section 6A’s small recent bank cluster (2026 deadlock and public/private-key cryptography stems, 2024–25 firewall stems, 2026 virtual-memory stems) is served with the set as OPC-fold-in material, counted separately in Section 6A’s bank-evidence note — the chapter’s bankCount stays 26.
• Book mode: ← Previous: Memory & Storage — RAM, ROM, Data Units and Storage Devices · Next: MS Office →

Goldmine Notes · Computer Science · Chapter 4 · Sources: TBT Computer Lecture 3 Sections 9–10 (software, GUI, booting), IBES Capsule Computer (system-software Q354–360), verified PPSC/FPSC past-paper banks, OPC Computer Science (Arslan Malik, 62 pp., fully OCR-read — Section 6A fold-in, filed 2026-11-01). ★ Windows/Linux basics verified against standard references (Windows version line, Linux 1991/Torvalds, Unix Bell Labs 1969, My Computer in Windows 95, MS-DOS for IBM PC 1981); Section 6A’s deadlock Coffman conditions and Brain/CIH/ILOVEYOU history likewise verified against standard references. Standard answers only.