Guides · Running a lab

What to do about the instrument PC

It runs Windows 7, it cannot be patched, it holds three years of data nobody has copied, and the vendor says do not touch it. A practical way to make it safe without breaking the instrument.

Reading time
10 min
Licence
Free to copy into your own lab documentation. No signup.

Almost every lab has one: a computer bolted to an instrument, running an operating system that stopped receiving security updates years ago, with a desktop full of folders named after people who have graduated.

It is simultaneously the most important computer in the lab and the one nobody is allowed to administer. That combination produces a standoff, and the standoff usually ends the same way — a failed disk, or a ransomware event that takes the instrument out for a month.

Who this is for

A lab manager, PI or student who has looked at the instrument PC and felt uneasy. It assumes no IT support and no budget. Nothing here requires you to update, re-image, or in any way alter the acquisition software.

Why it is like this, and why that is reasonable

The acquisition software is usually validated against one specific operating system version. The vendor supports that combination and no other. An update can break the driver for a card that is no longer manufactured, and the fix may be a service visit you cannot get quickly or cheaply.

So “do not touch it” is sound advice about the software. The mistake is extending it to the data and the network, which are separate problems with separate answers.

You are not trying to modernise the instrument PC. You are trying to make it not matter if it dies tomorrow.

The three real risks

1. The disk is the only copy

This is the common one and the most expensive. A single drive, often a decade old, spinning in a warm room, holding data that exists nowhere else. Drives do not warn you.

2. It is on the network with no defences

An unpatched machine on the institutional network is a standing invitation. Ransomware does not care that the machine is scientific equipment — and encrypted acquisition data is usually unrecoverable.

3. Nobody knows what is on it

Desktop folders named for people who left. Nobody is certain what is live, what is finished, and what has already been copied elsewhere. That uncertainty is why the disk never gets cleared, which is why it fills up.

What to do, in order

Each step is safe on its own and none of them touches the acquisition software. Do them in this order — the first one is the one that matters.

Making the instrument PC survivable 0 / 9
✓Get a complete copy off it today, however inelegantlyAn external disk and a drag-and-drop is fine. Do this before anything else on the list.
✓Check the copy actually opensOpen three files at random from the copy, not the original. Copies fail silently.
✓Find out whether it is on the network, and whether it needs to beMany only need the network for licensing or file transfer. Some need nothing at all.
✓Ask IT for an isolated VLAN or a firewall ruleThe phrase to use: "an unpatched instrument PC that cannot be updated for vendor support reasons."
✓Set up a repeating copy to somewhere elseScheduled sync to a share or a disk. Anything automatic beats anything manual.
✓Disable USB autorun, and ban personal drivesShared thumb drives are the commonest infection route in an isolated lab.
✓Give the machine one shared login, not five personal onesPersonal accounts create private folders that nobody clears when people leave.
✓Write the vendor and contract details on the machine itselfModel, serial, support contact, licence expiry. Taped to the case. You will need it under pressure.
✓Record what "rebuild this" would involveWhich install media, which licence key, which settings. Even a one-page note is worth days later.
Why we care about this

Step five — the repeating copy — is what woodle.cloud does by watching the folder the instrument already writes to, so files land attached to the run that produced them without anyone remembering. The rest of the list matters whatever you use, and steps one through four cost nothing.

See how instruments land →

Clearing the disk without losing anything

Full disks cause failed acquisitions, and the fear of deleting something real is why nobody clears them. A safer sequence:

  1. Copy everything off first. Not selectively. Everything, including the desktop.
  2. Verify the copy by opening files from it — ideally on a different machine.
  3. Move, do not delete. Shift the old material into one folder named with today's date. Leave it there.
  4. Wait a full experimental cycle — a month or a term. If nothing has been missed, delete that folder.

The waiting step is what makes this politically possible. Nobody has to be sure in advance.

If the instrument PC has already failed

Stop using the drive immediately — continued power-on is the main cause of a recoverable failure becoming unrecoverable. Do not run repair tools on the original disk. Contact the vendor before re-imaging, because acquisition licences are sometimes tied to hardware. And note that professional recovery in most Indian cities costs less than a service visit, and far less than repeating a year of experiments.

The one-page record to keep

For each instrument, one page, kept somewhere other than the instrument PC:

  • Make, model, serial number, and the year it was installed
  • Operating system and acquisition software version — and that it must not be updated
  • Vendor support contact, contract status, licence expiry
  • Where its data is copied to, and how often
  • Who to call when it stops working, in order

This page takes twenty minutes and is the single most useful document in a lab during a failure.

Take it with you

The checklist and the one-page record are free to copy into your own lab documentation. No attribution needed and no signup. If you do only one thing from this guide, do the first line of the checklist.