The PowerBook 145 was supposed to be a simple first-power-on gamble. It was clean enough to be tempting, cheap enough to take a chance on, and old enough that I knew better than to assume anything about it.
The first round did not go well. The machine looked promising inside, but it would not chime. I found a torn hard-drive ribbon cable, confirmed that the PRAM battery area was not a disaster, and still had no working computer. At that point I had a clean PowerBook with a real storage mystery and no proof that the logic board was alive.
The replacement adapter changed that.
With the Amazon replacement adapter connected, the PowerBook finally woke up. The screen came on. The startup process moved forward. The keyboard and trackball were usable. The floppy drive became part of the investigation instead of a question I could not reach yet.
That did not mean the machine was restored. It meant the PowerBook was alive enough to start giving me better failures.
The Screen Was Rough, But Usable
The display was the first thing I noticed after the relief of seeing it boot. It has clouding, obvious artifacts, and areas that look like age rather than a simple contrast adjustment. It is not a clean screen.
It was still good enough to work with. I could read dialogs, move around the Finder, open control panels, and keep testing. That distinction matters in a restoration. A part can be damaged and still be useful enough to move the project forward.
The dead pixels look like impact damage to me, but the cloudy uneven look feels like something else, possibly the kind of capacitor or board-cleaning problem I have not learned how to tackle yet. I would love to get this screen clearer. Soldering and board cleaning are still outside my comfort zone, so if anyone knows a good recapping service or has practical advice for this display family, I am listening.
The Hard Drive Was Not What I Thought It Was
Earlier, I treated the drive in the bay as if it belonged to the PowerBook’s SCSI storage path and assumed the torn cable was the main blocker. After pulling the drive and looking at it properly, that was wrong.
The drive inside was an Apple-labeled IBM 750 MB 2.5-inch AT drive. In other words, IDE. Not SCSI.
The connector made the mismatch obvious once I stopped treating the drive as part of the expected PowerBook 145 storage path.
I pulled the drive from the computer. I also pulled the torn cable, because once the drive turned out to be IDE, that damaged cable was not a part I needed to keep installed while I wait on the correct storage path. Whatever story put that drive in this machine, it was not going to become the internal SCSI solution for this PowerBook.
I did find a replacement cable from 1-bit rainbow, and I ordered it. I also ordered a BlueSCSI for the machine. That installation deserves its own follow-up once the parts arrive, so I am not going to pretend this post solves the internal storage problem.
So the PowerBook could boot, but it still did not have usable internal storage.
The Floppy Got Me Into System 7.1
The floppy set I purchased online was confusing. Some disks had Apple labels, some had handwritten labels, and the labels did not all agree with each other. I am not going to pretend I know the full history of the set. What mattered was that one path got the PowerBook into System 7.1.
That was enough to start learning from the machine instead of guessing about it. The floppy drive could read disks. The Finder ran. The trackball worked. Disk First Aid and other small utilities were available. The machine was no longer just a clean shell with a damaged cable.
It also reported something I did not expect.
The PowerBook showed 6,144K of memory. That changed the shape of the problem. With only a floppy boot and no usable internal storage, every disk swap matters. With 6 MB installed, the RAM Disk stopped being a curiosity and became a possible way around the storage problem.
The RAM Disk Became The Temporary Hard Drive
I found the RAM Disk controls in the Memory control panel and tried the obvious thing: make a RAM Disk large enough to hold the System Folder.
Because the machine had 6 MB installed, I created a RAM Disk and copied the System Folder over, and restarted.
The PowerBook booted from RAM.
No internal hard drive. No external SCSI device. No floppy left in the drive as the boot volume. Just a System Folder copied onto a RAM Disk large enough to act like the temporary disk I needed.
The PowerBook was not merely alive. It could run System 7.1 without depending on the internal storage path I still had to repair. In a very limited temporary way.
Booting From RAM Made The Software Search Possible
Once the machine could boot from RAM, I found useful pieces: Startup Disk, Disk First Aid, Calculator, Chooser, desk accessories, and items from the Tidbits disk. The PowerBook started to feel like a limited working classic Mac environment instead of a machine I was just trying to prove alive.
The PowerBook 145 is in a much better place than it was after the first teardown. It powers on with the replacement adapter. The LCD is degraded but usable. The keyboard and trackball work. The floppy drive reads disks and writes files. The machine reports 6 MB of RAM. It boots into System 7.1 from floppy. More importantly, it can boot from a RAM Disk after copying the System Folder over.
The drive I found inside turned out to be IDE, so I removed it. The torn cable is out of the machine too. A replacement cable and BlueSCSI are on order, and that installation will be a separate follow-up once the parts arrive. Disk Copy is still missing from the available disks. Formatting is not working from the current software environment. The display has obvious aging, likely more than one issue, and I would like to understand whether recapping or board cleaning could make it clearer.
Sources
- What a Dead PowerBook 145 Still Told Me
- Apple Service Source: PowerBook 140/145/145B/170 (PDF)
- 1-bit rainbow
- BlueSCSI
- Apple: Obtaining service for your Apple product after an expired warranty
AI Usage Transparency Report
AI Era · Written during widespread use of AI tools
AI Signal Composition
Score: 0.25 · Moderate AI Influence
Summary
The PowerBook 145 was restored to a working state, with the replacement adapter allowing it to boot into System 7.1 from floppy. The machine's LCD is degraded but usable, and the keyboard and trackball work. A RAM Disk was created to hold the System Folder, allowing the machine to boot without internal storage.
Related Posts
Preparing a BlueSCSI Card for My PowerBook 145 with Basilisk II
A step-by-step walkthrough for preparing a BlueSCSI v2 PowerBook card image with Basilisk II: download the pieces, configure the emulator, boot a working classic Mac image, mount the target System 7.1 image, stage tools, and shut down cleanly before moving the image to the card.
How I Keep Up With ISC2 CPE Credits Without Making It a Second Job
Keeping up with ISC2 CPE credits is easier when you treat it like a normal professional habit instead of a renewal emergency. Here is the system I use across CISSP, CCSP, SSCP, and CSSLP, with free and low-friction sources for webinars, books, training, and work-based credits.
When AI Agents Trust the Wrong Tool Description
Microsoft's MCP tool-poisoning research shows why AI agent security has to treat tool descriptions, schemas, and metadata as part of the control plane instead of harmless documentation.
Jamf Was My Mac Evidence Layer for CMMC
How Jamf Compliance helped support the Mac portion of a CMMC assessment, and why I added a small read-only CSV summary script for auditor-ready failed-result evidence.
What I Check Before I Trust a Homebrew Formula or Cask
Homebrew gives Mac admins a useful first-pass inspection workflow before trusting a formula or cask: check the source, checksum, version, tap state, availability, and upstream maintenance story.
When a Local AI Tool Belongs in My Workflow and When It Stays in the Lab
Running AI locally on a Mac has become a real part of my workflow, but only once I stopped treating local models like general-purpose answers and started treating them like constrained components inside a system I can still inspect.
Apple’s WWDC26 AI Story Is About Control, Not Just Models
Apple’s WWDC26 special presentation on Apple Intelligence and Xcode was less about adding a chat box to developer tools and more about making AI part of the platform boundary. Xcode agents, App Intents, Foundation Models, Core AI, and MLX all point toward the same idea: intelligent features need context, permissions, testing, and clear ownership before they belong in production software.
What a Dead PowerBook 145 Still Told Me
I picked up a clean PowerBook 145 knowing it might be a gamble. What I found was a machine that looked promising on the outside, demanded the correct 7.5V power approach, revealed a torn hard drive ribbon cable inside, and still refused to chime. That first teardown ended up being less about a successful revival and more about the reality of vintage Apple restoration.
The CMMC Evidence Collection Guide I Wish I Had Before My Assessment
When I started preparing for a CMMC assessment, I expected to spend most of my time focused on policies, procedures, and the System Security Plan. Those things are certainly important, but what surprised me was how much of the assessment ultimately came down to evidence.
WWDC 2026 Was Bigger Than The Keynote
Most of those conversations eventually landed in the same place. Siri wasn't ready. Liquid Glass was everywhere. There was no new hardware announcement. Depending on who you asked, WWDC 2026 was either disappointing or forgettable.
