Free A-Level Computer Science guide

Operating systems and memory management

An operating system coordinates shared hardware and offers useful services to programs. Memory management lets those programs use addresses safely without each controlling the physical RAM directly.

Content owner: Michael Print · Written for A-Level learners · Checked against official specifications

The idea to start with

The OS manages processes, memory, files, devices, user interaction and access control. It allocates resources, protects processes from one another and provides interfaces that applications can use.

Paging maps fixed-size virtual pages to physical frames; segmentation divides memory into variable-size logical regions. Virtual memory provides a process address-space abstraction; demand paging can keep some pages in secondary storage until needed.

OCR H446 · 1.2.1(a–b), (e–h)

Before you start

Useful foundations

RAM, persistent storage and memory addresses
Processes as running instances of programs

By the end, you should be able to

Explain OS responsibilities with examples
Compare the five named OS categories
Translate a paged address and explain page faults
Compare segmentation, paging and virtual memory
Distinguish BIOS, drivers and virtual machines

OS services: one manager for shared resources

A process needs CPU time, memory and access to files/devices. The OS coordinates those resources and enforces permissions.

Applications request services through defined interfaces. For example, opening a file lets the application use file contents without knowing the disk’s physical geometry.

A service returns a result or an error after permission checks and hardware coordination.
Abstraction does not remove resource limits: permission failure, full storage and disconnected devices still need handling.

What does the OS manage?

Processes → CPU time: Schedule runnable processes so applications can share the processor.
Memory → allocation and protection: Allocate memory and protect one process from another.
Files → organisation and access: Organise directories/files and check permissions before an operation.
Devices → drivers and queues: Coordinate hardware through drivers. A print queue keeps two applications’ output from becoming interleaved.
Users → interaction: Offer a command-line or graphical interface.

OS categories: match the requirement

These categories can overlap. A controller can be both embedded and real-time; a desktop can support multitasking and multiple users.

Five categories, five questions

Embedded: a dedicated device?: A washing-machine controller has a specific purpose and often tight power/memory constraints.
Real-time: a deadline?: Predictable responses must meet deadlines. A late braking-control response may be useless despite a fast average.
Multitasking: several tasks?: Time slices and/or several cores share processing between active tasks.
Multi-user: separate users?: Protected files, separate sessions and fair resource allocation support several users.
Distributed: one coherent system?: Coordinate resources across connected machines, rather than simply run unrelated networked programs.

Match OS requirements to a scenario
Scenario	Relevant type	Why
Interactive desktop	Multitasking	Several applications remain responsive
Shared institutional server	Multi-user	Separate identities and controlled shared resources
Safety controller	Real-time, often embedded	Bounded response time and dedicated purpose
Integrated cluster	Distributed	Coordinates resources across machines

Paging: pages in virtual memory, frames in RAM

Paging divides a process’s virtual address space into equal-sized pages. Physical RAM is divided into frames of the same size. A page table records the mappings.

Pages of one process can occupy non-neighbouring frames. The OS does not need one contiguous physical block for the entire process.

Page tables and translation require resources.
Protection bits can prevent a process reading or writing another process’s memory.

Replace the page number with its mapped frame number

Virtual address → page number + offset: Split the address using the page size given in the question.
Page number → page-table lookup: Find the physical frame mapped to that virtual page.
Physical address → frame number + same offset: Replace the page number with the frame number. Preserve the offset because page and frame sizes match.

Use the stated size: exact page sizes depend on the implementation.

Segmentation: divide by logical purpose

A segment table records each logical region’s base address, size and permissions. An offset must be within that segment’s limit.

Systems can combine segmentation and paging. The comparison below shows the distinction when each method is considered separately.

Fixed size or logical region?

Paging: Equal-sized virtual pages map to equal-sized physical frames. The final page may be partly unused: internal fragmentation.
Segmentation: Variable-sized code, stack and data regions reflect program organisation. Gaps between allocated regions can cause external fragmentation.

Virtual memory and the page-fault process

Virtual memory provides a process address-space abstraction. In demand-paged systems, some pages can remain in secondary storage until needed.

For a valid, permitted access to a non-resident page backed by storage, a page fault makes the OS load it before continuing. An invalid address or forbidden access instead needs error handling.

Secondary storage is much slower than RAM: frequent page faults can cause severe slowdown or thrashing.
Virtual memory does not make physical RAM faster or guarantee unlimited memory.

From missing page to restarted access

Locate the page
The OS identifies the required non-resident page on secondary storage.
Obtain a frame
Use a free RAM frame, or choose another page to evict.
Preserve changes if needed
Write a modified evicted page back. A clean page can sometimes be discarded and reread later.
Load and map
Read the required page into RAM and establish its page-table mapping.
Restart the access
The process can now access the resident page using its mapped frame.

BIOS: begin the boot process

Traditional BIOS firmware is retained in non-volatile storage and begins before the OS is running. Contemporary machines commonly use UEFI; OCR explicitly names BIOS.

Firmware hands over to the OS loader

Initialise and check
Firmware starts up and initialises/checks hardware.
Identify a boot device
Find the device from which the system will boot.
Begin loading
Start the boot process so an OS loader can take over.

Drivers: connect a general request to a device

An application uses an OS interface instead of programming each printer directly.

The driver supplies device-specific operations

OS request
The operating system asks for a general operation.
Device driver
Translate that request into the operations the particular device understands.
Result or event
Report the device’s result/events back to the OS.

Virtual machines: two uses of machine abstraction

A virtual machine uses software to provide a machine-like environment. Both uses below have overhead and limits to their isolation/configuration.

Guest OS or intermediate code?

System VM + hypervisor: A guest OS uses virtual CPU, memory, disks and devices inside/on a host system.
Language VM: An execution environment runs intermediate code, such as bytecode.

Worked example

Apply the OS categories to five workloads

For a designer editing images while listening to audio, a multitasking OS schedules several runnable applications. Responsiveness depends on scheduling and available resources, rather than requiring all tasks to run at exactly the same instant.
For several students on a shared server, a multi-user OS maintains distinct sessions, permissions and resource allocation. Running several applications under one unrestricted shared account would not meet the same isolation need.
A washing-machine controller has a dedicated purpose and limited resources, so embedded describes its setting. If a safety action also has a strict deadline, real-time describes that requirement; the categories can overlap.
For a factory safety controller, verify the maximum response against the stated deadline. A low average time alone is insufficient because one late response can violate the requirement.
For an integrated compute cluster, a distributed OS can coordinate work and resources across machines as a coherent system. Network delay or a failed node still needs handling. Separate unrelated desktops on a LAN do not automatically form a distributed OS.

Worked example

Translate a paged address

Assume page/frame size 1024 bytes. The example page table maps virtual page 2 to physical frame 7.
If page 2 is not resident, the OS must first load/map it after a page fault. A disk location cannot be treated as a RAM frame.

Virtual 2500 becomes physical 7620

2500 → page 2, offset 452: 2500 = 2 × 1024 + 452.
Page table → frame 7: Virtual page 2 is mapped to physical frame 7.
Frame 7 + offset 452 → 7620: 7 × 1024 + 452 = 7620. The offset stays unchanged.

Example page table
Virtual page	Physical frame	Resident?
0	3	Yes
1	—	No
2	7	Yes

Worked example

Choose services for a shared school server

Separate login identities require multi-user support and permissions, so one student's files are not automatically readable by another.
The server runs authentication, file sharing and printing concurrently, requiring process scheduling and protected memory. Drivers support its physical/network devices.
A guest VM can isolate a teaching environment and run a different OS, but it still consumes host CPU, RAM and storage. File backups and access controls remain necessary.

Original A-Level practice

7 original questions total 24 marks. Attempt each before opening the independently written indicative marking guidance.

Question 1

3 marks

Explain three OS responsibilities using an example for each.

Show solution and marking guidance

Indicative answer

1 mark each for three responsibility/example pairs, such as process scheduling/time slices, memory allocation/protection, file organisation/permissions, device handling/print queues or user-interface/input handling. Repeating one responsibility gains no extra mark.

Question 2

4 marks

Compare the OS requirements of several students sharing one server and a designer running several applications under one account.

Show solution and marking guidance

Indicative answer

The shared server requires multi-user support for distinct identities/sessions (1).
Permissions/resource allocation protect users and their work from one another (1).
The designer needs multitasking to schedule multiple active applications (1).
Several tasks under one account do not by themselves establish separate protected user sessions; categories may coexist on the same OS (1).

Question 3

3 marks

With 512-byte pages, virtual address 1300 uses a page mapped to frame 9. Calculate the page, offset and physical address.

Show solution and marking guidance

Indicative answer

1 mark: page number = 1300 DIV 512 = 2.
1 mark: offset = 1300 MOD 512 = 276.
1 mark: physical address = 9 × 512 + 276 = 4884.

Question 4

4 marks

Explain why an integrated compute cluster may use a distributed OS, and give a limitation. Contrast this with a dedicated washing-machine controller.

Show solution and marking guidance

Indicative answer

The distributed OS coordinates resources/work across connected machines (1).
It presents those resources as a coherent system rather than merely unrelated networked programs (1).
Communication delay/node failures require management, or another correctly connected limitation (1).
An embedded OS serves the dedicated controller with appropriate resource constraints; embedded describes the device setting rather than distribution across machines (1).

Question 5

4 marks

Compare paging and segmentation, then explain the cost of a page fault.

Show solution and marking guidance

Indicative answer

1 mark: paging uses fixed-size pages/frames; segmentation uses variable-size logical regions.
1 mark: paged process memory can occupy non-contiguous frames; segment allocation can create external fragmentation.
1 mark: a fault occurs when an accessed page is not resident and needs loading.
1 mark: secondary-storage access, possible eviction/write-back and restart add delay.

Question 6

3 marks

Distinguish the roles of BIOS, a device driver and a language virtual machine.

Show solution and marking guidance

Indicative answer

1 mark: BIOS initialises hardware and begins booting before the OS takes over.
1 mark: a driver implements OS/device-specific communication.
1 mark: a language VM executes intermediate code using a software execution environment.

Question 7

3 marks

A factory controller must react within 8 ms and runs inside one machine. Which OS descriptions are relevant, and why is an average of 3 ms insufficient evidence?

Show solution and marking guidance

Indicative answer

1 mark: embedded describes its dedicated device context.
1 mark: real-time describes its required deadline-bound response.
1 mark: a 3 ms average may conceal occasional responses exceeding 8 ms, so worst-case/deadline evidence is needed.

Specification and references

This guide addresses OCR H446 1.2.1(a–b), (e–h). Check your examination year and the complete specification for the assessment scope.

These are independently written explanations and practice questions. CompSciTutoring.co.uk is not affiliated with or endorsed by an examination board. The marking guidance is indicative; always check the syllabus for your examination year.

Found an error? Email a correction.

Need help applying this to unfamiliar questions?

Use the free examples first, then explore one-to-one tuition if guided practice would help.

Explore tuition Email Michael

Free A-Level Computer Science guide

Operating systems and memory management

An operating system coordinates shared hardware and offers useful services to programs. Memory management lets those programs use addresses safely without each controlling the physical RAM directly.

Content owner: Michael Print · Written for A-Level learners · Checked against official specifications

The idea to start with

The OS manages processes, memory, files, devices, user interaction and access control. It allocates resources, protects processes from one another and provides interfaces that applications can use.

OCR H446 · 1.2.1(a–b), (e–h)

Before you start

Useful foundations

RAM, persistent storage and memory addresses
Processes as running instances of programs

By the end, you should be able to

Explain OS responsibilities with examples
Compare the five named OS categories
Translate a paged address and explain page faults
Compare segmentation, paging and virtual memory
Distinguish BIOS, drivers and virtual machines

OS services: one manager for shared resources

A process needs CPU time, memory and access to files/devices. The OS coordinates those resources and enforces permissions.

Applications request services through defined interfaces. For example, opening a file lets the application use file contents without knowing the disk’s physical geometry.

A service returns a result or an error after permission checks and hardware coordination.
Abstraction does not remove resource limits: permission failure, full storage and disconnected devices still need handling.

What does the OS manage?

Processes → CPU time: Schedule runnable processes so applications can share the processor.
Memory → allocation and protection: Allocate memory and protect one process from another.
Files → organisation and access: Organise directories/files and check permissions before an operation.
Devices → drivers and queues: Coordinate hardware through drivers. A print queue keeps two applications’ output from becoming interleaved.
Users → interaction: Offer a command-line or graphical interface.

OS categories: match the requirement

These categories can overlap. A controller can be both embedded and real-time; a desktop can support multitasking and multiple users.

Five categories, five questions

Embedded: a dedicated device?: A washing-machine controller has a specific purpose and often tight power/memory constraints.
Real-time: a deadline?: Predictable responses must meet deadlines. A late braking-control response may be useless despite a fast average.
Multitasking: several tasks?: Time slices and/or several cores share processing between active tasks.
Multi-user: separate users?: Protected files, separate sessions and fair resource allocation support several users.
Distributed: one coherent system?: Coordinate resources across connected machines, rather than simply run unrelated networked programs.

Match OS requirements to a scenario
Scenario	Relevant type	Why
Interactive desktop	Multitasking	Several applications remain responsive
Shared institutional server	Multi-user	Separate identities and controlled shared resources
Safety controller	Real-time, often embedded	Bounded response time and dedicated purpose
Integrated cluster	Distributed	Coordinates resources across machines

Paging: pages in virtual memory, frames in RAM

Paging divides a process’s virtual address space into equal-sized pages. Physical RAM is divided into frames of the same size. A page table records the mappings.

Pages of one process can occupy non-neighbouring frames. The OS does not need one contiguous physical block for the entire process.

Page tables and translation require resources.
Protection bits can prevent a process reading or writing another process’s memory.

Replace the page number with its mapped frame number

Virtual address → page number + offset: Split the address using the page size given in the question.
Page number → page-table lookup: Find the physical frame mapped to that virtual page.
Physical address → frame number + same offset: Replace the page number with the frame number. Preserve the offset because page and frame sizes match.

Use the stated size: exact page sizes depend on the implementation.

Segmentation: divide by logical purpose

A segment table records each logical region’s base address, size and permissions. An offset must be within that segment’s limit.

Systems can combine segmentation and paging. The comparison below shows the distinction when each method is considered separately.

Fixed size or logical region?

Paging: Equal-sized virtual pages map to equal-sized physical frames. The final page may be partly unused: internal fragmentation.
Segmentation: Variable-sized code, stack and data regions reflect program organisation. Gaps between allocated regions can cause external fragmentation.

Virtual memory and the page-fault process

Virtual memory provides a process address-space abstraction. In demand-paged systems, some pages can remain in secondary storage until needed.

For a valid, permitted access to a non-resident page backed by storage, a page fault makes the OS load it before continuing. An invalid address or forbidden access instead needs error handling.

Secondary storage is much slower than RAM: frequent page faults can cause severe slowdown or thrashing.
Virtual memory does not make physical RAM faster or guarantee unlimited memory.

From missing page to restarted access

Locate the page
The OS identifies the required non-resident page on secondary storage.
Obtain a frame
Use a free RAM frame, or choose another page to evict.
Preserve changes if needed
Write a modified evicted page back. A clean page can sometimes be discarded and reread later.
Load and map
Read the required page into RAM and establish its page-table mapping.
Restart the access
The process can now access the resident page using its mapped frame.

BIOS: begin the boot process

Traditional BIOS firmware is retained in non-volatile storage and begins before the OS is running. Contemporary machines commonly use UEFI; OCR explicitly names BIOS.

Firmware hands over to the OS loader

Initialise and check
Firmware starts up and initialises/checks hardware.
Identify a boot device
Find the device from which the system will boot.
Begin loading
Start the boot process so an OS loader can take over.

Drivers: connect a general request to a device

An application uses an OS interface instead of programming each printer directly.

The driver supplies device-specific operations

OS request
The operating system asks for a general operation.
Device driver
Translate that request into the operations the particular device understands.
Result or event
Report the device’s result/events back to the OS.

Virtual machines: two uses of machine abstraction

A virtual machine uses software to provide a machine-like environment. Both uses below have overhead and limits to their isolation/configuration.

Guest OS or intermediate code?

System VM + hypervisor: A guest OS uses virtual CPU, memory, disks and devices inside/on a host system.
Language VM: An execution environment runs intermediate code, such as bytecode.

Worked example

Apply the OS categories to five workloads

For a designer editing images while listening to audio, a multitasking OS schedules several runnable applications. Responsiveness depends on scheduling and available resources, rather than requiring all tasks to run at exactly the same instant.
For several students on a shared server, a multi-user OS maintains distinct sessions, permissions and resource allocation. Running several applications under one unrestricted shared account would not meet the same isolation need.
A washing-machine controller has a dedicated purpose and limited resources, so embedded describes its setting. If a safety action also has a strict deadline, real-time describes that requirement; the categories can overlap.
For a factory safety controller, verify the maximum response against the stated deadline. A low average time alone is insufficient because one late response can violate the requirement.
For an integrated compute cluster, a distributed OS can coordinate work and resources across machines as a coherent system. Network delay or a failed node still needs handling. Separate unrelated desktops on a LAN do not automatically form a distributed OS.

Worked example

Translate a paged address

Assume page/frame size 1024 bytes. The example page table maps virtual page 2 to physical frame 7.
If page 2 is not resident, the OS must first load/map it after a page fault. A disk location cannot be treated as a RAM frame.

Virtual 2500 becomes physical 7620

2500 → page 2, offset 452: 2500 = 2 × 1024 + 452.
Page table → frame 7: Virtual page 2 is mapped to physical frame 7.
Frame 7 + offset 452 → 7620: 7 × 1024 + 452 = 7620. The offset stays unchanged.

Example page table
Virtual page	Physical frame	Resident?
0	3	Yes
1	—	No
2	7	Yes

Worked example

Choose services for a shared school server

Separate login identities require multi-user support and permissions, so one student's files are not automatically readable by another.
The server runs authentication, file sharing and printing concurrently, requiring process scheduling and protected memory. Drivers support its physical/network devices.
A guest VM can isolate a teaching environment and run a different OS, but it still consumes host CPU, RAM and storage. File backups and access controls remain necessary.

Original A-Level practice

7 original questions total 24 marks. Attempt each before opening the independently written indicative marking guidance.

Question 1

3 marks

Explain three OS responsibilities using an example for each.

Show solution and marking guidance

Indicative answer

1 mark each for three responsibility/example pairs, such as process scheduling/time slices, memory allocation/protection, file organisation/permissions, device handling/print queues or user-interface/input handling. Repeating one responsibility gains no extra mark.

Question 2

4 marks

Compare the OS requirements of several students sharing one server and a designer running several applications under one account.

Show solution and marking guidance

Indicative answer

The shared server requires multi-user support for distinct identities/sessions (1).
Permissions/resource allocation protect users and their work from one another (1).
The designer needs multitasking to schedule multiple active applications (1).
Several tasks under one account do not by themselves establish separate protected user sessions; categories may coexist on the same OS (1).

Question 3

3 marks

With 512-byte pages, virtual address 1300 uses a page mapped to frame 9. Calculate the page, offset and physical address.

Show solution and marking guidance

Indicative answer

1 mark: page number = 1300 DIV 512 = 2.
1 mark: offset = 1300 MOD 512 = 276.
1 mark: physical address = 9 × 512 + 276 = 4884.

Question 4

4 marks

Explain why an integrated compute cluster may use a distributed OS, and give a limitation. Contrast this with a dedicated washing-machine controller.

Show solution and marking guidance

Indicative answer

The distributed OS coordinates resources/work across connected machines (1).
It presents those resources as a coherent system rather than merely unrelated networked programs (1).
Communication delay/node failures require management, or another correctly connected limitation (1).
An embedded OS serves the dedicated controller with appropriate resource constraints; embedded describes the device setting rather than distribution across machines (1).

Question 5

4 marks

Compare paging and segmentation, then explain the cost of a page fault.

Show solution and marking guidance

Indicative answer

1 mark: paging uses fixed-size pages/frames; segmentation uses variable-size logical regions.
1 mark: paged process memory can occupy non-contiguous frames; segment allocation can create external fragmentation.
1 mark: a fault occurs when an accessed page is not resident and needs loading.
1 mark: secondary-storage access, possible eviction/write-back and restart add delay.

Question 6

3 marks

Distinguish the roles of BIOS, a device driver and a language virtual machine.

Show solution and marking guidance

Indicative answer

1 mark: BIOS initialises hardware and begins booting before the OS takes over.
1 mark: a driver implements OS/device-specific communication.
1 mark: a language VM executes intermediate code using a software execution environment.

Question 7

3 marks

A factory controller must react within 8 ms and runs inside one machine. Which OS descriptions are relevant, and why is an average of 3 ms insufficient evidence?

Show solution and marking guidance

Indicative answer

1 mark: embedded describes its dedicated device context.
1 mark: real-time describes its required deadline-bound response.
1 mark: a 3 ms average may conceal occasional responses exceeding 8 ms, so worst-case/deadline evidence is needed.

Specification and references

This guide addresses OCR H446 1.2.1(a–b), (e–h). Check your examination year and the complete specification for the assessment scope.

Found an error? Email a correction.

Need help applying this to unfamiliar questions?

Use the free examples first, then explore one-to-one tuition if guided practice would help.

Explore tuition Email Michael