A method for when something just stopped working.
79 guides in Technology
Offline is the computer's opinion, not the printer's. Three questions that place the fault precisely — in the printer, on the network, or in the queue — and the underlying cause of the ones that keep coming back.
A short sequence that tells you within minutes whether the fault is the line, the router or one device — and stops you resetting things that were never the problem.
Working through cable, port, power and file system in order, and knowing when to stop and get the data off.
Isolating whether it is the charger, the port, the battery or the software, in that order.
Get it on the network first, then add it — and why the manufacturer's software is usually unnecessary.
Dust, soft surfaces and runaway background processes — the three causes, in order of likelihood.
Working through charging faults in order — cable, adapter, socket, port — and the lint in the port that causes most of them.
The column that is pegged tells you the fix. Reading the four resources properly turns "my computer is slow" into a specific, solvable problem.
The escalation from closing one app to a forced restart, in the order that loses the least work.
Reading the symptom to find the cause — streaks, banding, smudging and fading each point somewhere different.
Storage, connection and stuck files — the causes of a failed update, and how to clear each safely.
A general troubleshooting method that works for almost any device — isolate the variable, change one thing at a time, and know when to stop.
Pairing conflicts, interference and battery — why Bluetooth drops, and the reset that fixes most of it.
The two ways to wire a television to a soundbar, which socket it has to be, the setting that has to be on, and the order to work through when the bar stays silent.
A structured check from power supply to screen that separates a flat battery from a genuine hardware fault.
Phone printing relies on discovery, and discovery breaks in specific, predictable ways. The five network arrangements that hide a printer from a phone, and how to print anyway.
The queue, the connection and the driver — a fault-finding order that resolves most printer problems in under ten minutes.
The first five minutes that determine whether the device survives, and the popular advice that makes things worse.
Most printers estimate ink rather than measuring it, and the estimate is deliberately cautious. How to tell a bad estimate from a genuine chip fault, and how much printing is actually left.
The output device is nearly always the answer — plus the handful of other checks worth making.
The setting that turns a stack of separate image files into one document, on a flatbed and on a feeder — plus what to do when your scanner refuses and you have twenty files already.
Identifying the common connectors by shape, and the more important point that two identical-looking cables can do completely different jobs.
The signs arrive in a rough order, and the window for getting data off narrows as you go. Which symptoms mean act now, and which mean act today.
How to recognise a swelling battery before it becomes obvious, why it must never be punctured, and the safe sequence for isolating and disposing of the device.
Product and option comparisons with explicit criteria, rather than a single recommendation.