Part S-02 · Course file SM-FTP-5
Step 2 — Working out whether your computer can run it
Step 2 of 5
This is the step that saves the most wasted time, because it is answered before anything is downloaded and it is answered with facts rather than hope. By the end of it you will know what your computer actually contains, what a system requirements table is telling you, and whether the machine you have is in the conversation at all.
| Part number | S-02 |
|---|---|
| Position | Step 2 of 5 |
| Reading time | About 10 minutes |
| You need | The computer in question, and ten quiet minutes |
| Ends with | Checklist S-02 |
| Last reviewed | 12 October 2026 |
First question: which kind of computer is it?
Before any numbers, there is a yes-or-no question that decides whether the rest of the step is worth doing: what operating system does the machine run, and is it a desktop or a laptop?
Operating system first. Most PC games in this category are published for desktop Windows. A growing number also run on Linux. A smaller number are published for macOS, and many are not — the example title used in this course, Crossout, is one that its publisher lists for desktop Windows and Linux only, with macOS not supported. If the only computer in the house is a Mac, that particular title is out, and no amount of specification-checking changes it. Other titles in the same category do publish Mac versions, so this rules out one game rather than the whole idea.
Desktop or laptop matters for a different reason. A laptop of a given age is usually slower than a desktop of the same age, because it has less room to get rid of heat, and it often shares memory between the processor and the graphics. A laptop is not disqualified; it simply tends to sit lower against the same requirements table than its price suggests.
What this step is not
Nothing here scans your computer, tests it, or tells you that something is wrong with it. There is no tool to run and nothing to install. You are going to read four numbers that your operating system already knows and write them on a piece of paper.
Finding your specifications, step by step
Four facts are enough for almost every requirements table: the operating system and whether it is 64-bit, the processor model, how much memory is installed, and the graphics hardware. Here is how to collect them without installing anything.
On Windows
- Open the Start menu, type About your PC and open the result. Write down the Windows edition, the version number, the processor line exactly as it appears, the installed RAM figure, and whether the system type says 64-bit.
- Press the Windows key together with R, type dxdiag and press Enter. This is a reporting tool built into Windows; it changes nothing.
- In the window that opens, choose the Display tab. Write down the name of the graphics adapter and the amount of display memory.
- Close the tool. You now have all four facts.
- Open File Explorer, select This PC, and write down the free space on the drive you would install to — usually C:, but not always.
On Linux
- Open a terminal window.
- Type lscpu and press Enter. The Model name line is your processor.
- Type free -h and press Enter. The total figure on the Mem line is your installed memory.
- Type lspci | grep -i vga and press Enter. The line returned names your graphics hardware.
- Type df -h and press Enter, and read the available column for the filesystem you would install to.
- Note your distribution and release as well; some publishers name the distributions they have tested.
Keep that short list somewhere you can find it again. You will use it for every game you look at from now on, and it saves you repeating the exercise each time.
Reading a system requirements table
Publishers normally print two columns: minimum and recommended. They are not two opinions about the same thing. They describe two different experiences, and understanding the difference is most of the skill.
| Column | What it generally means | What it does not mean |
|---|---|---|
| Minimum | The game is expected to start and run on this hardware at low settings and a low resolution. | That it will feel smooth, or that it will stay smooth when many players are on screen. |
| Recommended | The experience the publisher has in mind, usually at a common resolution and middling settings. | The best the game can look, or a guarantee of anything on your particular combination of parts. |
The advantages and the drawbacks of aiming at the minimum
Running a game on minimum hardware has real advantages. You find out whether you enjoy it without spending anything on equipment, you keep an older machine useful, and if the answer is no you have lost only the download. For a game you are merely curious about, that is a sensible trade.
The drawbacks are equally real. At the minimum, a game is usually running at low detail and a reduced resolution, and online games are at their heaviest exactly when the most is happening, which is when you most want them to be responsive. An older computer may also run hot and loud. And a poor first impression caused by hardware is easy to mistake for a poor game.
The practical rule: if you meet the minimum comfortably on three of the four facts and fall short on one, it is usually worth trying. If you fall short on memory or on the operating system version, stop — those two are rarely negotiable.
Disk space, download size and your connection
The storage figure in a requirements table is the space the installed game occupies. It is not the whole story. A drive that is completely full behaves badly in general, so leave headroom beyond the stated figure rather than exactly meeting it. Patches also accumulate, and a game that installs at one size often grows over a year.
Then there is the connection. In Australia a great many households are on plans with a monthly data allowance, and some are on mobile broadband where every gigabyte is counted. A first download of a large game plus a month of patches can be a noticeable share of a modest allowance. Before you start, look at your plan — the figure is on your bill or in your provider's app — and decide whether the download should wait for any off-peak or unmetered period your plan includes.
It is also worth downloading when nobody else in the house needs the connection. A large download will take whatever bandwidth it is given, and the complaints that follow are a poor start to a household's relationship with a new game.
Graphics drivers, and where to get them
A driver is the software that lets your operating system talk to a piece of hardware. Graphics drivers are updated often, and an old one is a common reason for a game running badly or refusing to start on hardware that should be fine.
There is one safe source for a graphics driver: the manufacturer of the graphics hardware, or, on Linux, your distribution's own package repositories. Websites offering driver update utilities, "driver packs" or one-click updaters are a long-standing route for unwanted software, and the Australian Cyber Security Centre's general advice on keeping software up to date — install updates from the vendor, automatically where possible — is the right habit here. You can read that advice at cyber.gov.au.
Nothing about this means your computer is currently at risk or that anything is wrong with it. It is ordinary maintenance, done once before you install a game and then left to update itself.
Worked example · The household
The spare-room desktop turns out to be running 64-bit Windows, with a processor line nobody in the house recognises, eight gigabytes of memory and a graphics adapter that shares memory with the processor. Free space on the main drive is forty gigabytes. The internet plan has a monthly allowance that the adult has, for the first time, actually looked up.
Comparing that with the requirements table for the game in question, they meet the operating system and the processor, sit exactly on the stated memory figure, and are plainly below the recommended graphics. They decide the honest expectation is low settings, and that forty gigabytes of free space is enough today but not enough to be comfortable in a year. The decision is: try it, at low settings, and clear some space first. Whether they enjoy it is not something the example claims to know.
Before you move on
You should now have four facts about your computer written down, plus the free space on your install drive and your monthly data position. You should be able to open a publisher's requirements table and say, within a minute, whether you are above the minimum, between the two columns, or below.
If you are below the minimum on memory or operating system, the course ends usefully here for that title: you have saved yourself a download and a disappointment. If you are somewhere between the columns, carry on to Step 3, which is about the account — the part that outlives any particular computer.
Checklist S-02 · Your equipment
- I know which operating system this computer runs, and whether it is 64-bit.
- I have written down the processor model exactly as the system reports it.
- I have written down the installed memory figure.
- I have written down the graphics hardware name.
- I know the free space on the drive I would install to, with headroom beyond the stated requirement.
- I have checked whether the title is published for my operating system at all.
- I have looked up my internet plan's data allowance for this month.
- My graphics driver comes from the hardware manufacturer or my distribution, and nowhere else.
- I have compared my four facts with the published minimum and recommended columns and formed an honest expectation.