What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The claim that a paper-saving change to a mainframe ruined a week of work cannot be verified from the available accounts. A 1977 CERN notice does document printer changes intended to save paper, but it reports neither lost work nor a failure. No identified source connects that notice—or the other mainframe stories sometimes found alongside it—to the headline’s alleged incident.
What the 1977 CERN notice actually says
CERN’s Computer Centre published a printer notice on 7 March 1977 describing changes intended to reduce paper use. It said carriage-control characters would remain unchanged. With automatic page eject, printing would continue at 61 lines per page; with page eject suppressed, it could print 64 lines per page. The notice also described exceptions and ways to request the older, larger paper. Read the CERN notice.
As an Amazon Associate I earn from qualifying purchases.
Those details establish a paper-saving printer adjustment, not a mainframe failure. The notice gives no quantified paper-savings result and does not say that a week of work was lost. Its author, David Underhill, should not be credited with a claim about ruined work that the notice does not make.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Other mainframe stories do not establish the incident
Several separate accounts concern mainframe trouble or change, but none supplies the missing link to the headline:
#1 Best Overall
- An InfoWorld first-person account describes a difficult conversion involving a Honeywell Model 120 and says it was completed within a week. It does not connect the conversion to paper-saving printer settings or say a week’s work was ruined.
- A Register account published on 19 April 2024 describes a trainee taking a mainframe storage device offline and a colleague reconnecting it promptly. It is not about paper-saving changes or a week of lost work.
- IEEE Spectrum’s history of IBM System/360 notes that moving to a larger system could require software to be rewritten because old software would not work on a different machine. That is general migration context, not evidence for this alleged event.
Combining these accounts would create a story no source supports: they concern different events, and none identifies the organization, system, change, failure, or losses described in the headline.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What would verify a week of lost work
A reliable account needs to identify the organization and mainframe, explain the exact printer or software change made to save paper, describe what failed and how work was affected, and document the recovery. A contemporaneous incident report, the original publication, or a named participant’s account could establish those details. Without such a source, the headline’s claim should remain an allegation rather than a reported fact.
Quick Recap
Best Value
- Murach's Mainframe COBOL
- Mike Murach & Associates
- ABIS BOOK
Rank #4
Rank #3
Rank #2
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Recommended Free Tools
