I got a Toshiba T1200, which has a bad screen, and a dead CMOS battery, and I thought the hard drive was broken too...

but I rebooted it and heard a KTHUNK and a really loud spin-up noise and holy shit, the hard drive works!
and it still has files on it. the newest date is January 1994.
It's a 21mb hard drive, with ~37k of bad sectors.

This fucker is never going to spin up again, so I better go find some serial cables and copy shit off now.
The backlight is fucked so I'm shining a flashlight on it.
without it, it looks like this.
FastLynx has a cool mode where you can use it between two DOS machines and you only have to install it on one of the machines, it bootstraps itself over the serial port to the one without it.
dang it. They're communicating enough to bootstrap, but not enough to actually work in fastlynx mode
ah-ha! It's this "Serial Accelerated (7-wire) Mode".
Turning that off makes it work.
COPYING! starting on the most useless files
I stopped it and reconfigured the serial port.
even with only 21mb, 9600 baud is way too slow
huh, gnu manuals? didn't expect to see that on a DOS machine not touched since 1994
and it's done copying! you can go to your rest, poor old hard drive.
the next computer I'm gonna work on is... another T1200!
This one is fully dead. No error blinks, nothing.
It's a surprisingly simple machine inside. Not super-cramped like a lot of portables.
it's got a cmos battery and a little speaker over here
Which is weird because the system has another battery over here.
neither of which are the main battery!
This one is also the same sort of setup where it's a floppy drive and a hard drive.
You could also get this in a dual-floppy model.
This little add-on here is the hard drive controller.
This was a weird thing. It kinda looks like it'd be a trackpad but it's on the bottom and this machine has no trackpad.
Turns out: it's RAM!
The whole motherboard
The floppy drive is by Toshiba, it's an ND-352S-A, or FDD4271G0W, or even a JAH1058939.
And it looks like a normal floppy drive but it's got the wrong connector. 26-pin IDC, for some reason.
The hard drive is even weirder.
It's by JVC! Yes, that JVC.
It's a JD3824G01-4.

And it has NO DEFECTS, woo!
And it turns out it uses the same 26-pin connector as the floppy drive.
the bottom of the hard drive is interesting
It's some kind of self-parking system.
This one also has something not in the other one:
A modem add-on!
The bottom.
That chip has an interesting pinout.
The sides have 10 pins, but they're arranged as two sets of 5, with a gap.
It's an HD637b05v0f, which is an 8-bit Hitachi microcontroller
Anyway I was hoping to combined these two into one machine, maybe even image the other hard drive?
But sadly I can't get machine 1 to power on anymore.
So I currently have two dead machines.
and I think that's all I'm gonna work on for tonight, so I'll have to hopefully pick this up some other time.
I have a third one in storage, but it makes these two look like they're in good shape
ooh, found a service manual:
https://t.co/E1I5AAzVuh
BTW a fun thing about this system is that the back of the power supply has two power switches.
One of them is for the system, and the other one is for the hard drive!
you can seriously boot up the laptop with the hard drive turned off. it's amazing.
also it has a function called "hard ram", which is why it has so many batteries.
You can set it up so that the expanded RAM is battery-backed, so you can set up a ramdisk that is maintained while the system is off.
Annoyingly the service manual doesn't explain the floppy or hard drive connectors.
It explains random pinouts for things like the display controller, but no hard drive/floppy pinouts.
oh neat. u/ConventionalMemories on retrobattlestations has built a CF-card adapter for these laptops, but it plugs into the expansion slot instead of the hard drive port.

https://t.co/WZXFPtnkGA

More from foone

More from Tech

A common misunderstanding about Agile and “Big Design Up Front”:

There’s nothing in the Agile Manifesto or Principles that states you should never have any idea what you’re trying to build.

You’re allowed to think about a desired outcome from the beginning.

It’s not Big Design Up Front if you do in-depth research to understand the user’s problem.

It’s not BDUF if you spend detailed time learning who needs this thing and why they need it.

It’s not BDUF if you help every team member know what success looks like.

Agile is about reducing risk.

It’s not Agile if you increase risk by starting your sprints with complete ignorance.

It’s not Agile if you don’t research.

Don’t make the mistake of shutting down critical understanding by labeling it Bg Design Up Front.

It would be a mistake to assume this research should only be done by designers and researchers.

Product management and developers also need to be out with the team, conducting the research.

Shared Understanding is the key objective


Big Design Up Front is a thing to avoid.

Defining all the functionality before coding is BDUF.

Drawing every screen and every pixel is BDUF.

Promising functionality (or delivery dates) to customers before development starts is BDUF.

These things shouldn’t happen in Agile.
The 12 most important pieces of information and concepts I wish I knew about equity, as a software engineer.

A thread.

1. Equity is something Big Tech and high-growth companies award to software engineers at all levels. The more senior you are, the bigger the ratio can be:


2. Vesting, cliffs, refreshers, and sign-on clawbacks.

If you get awarded equity, you'll want to understand vesting and cliffs. A 1-year cliff is pretty common in most places that award equity.

Read more in this blog post I wrote:
https://t.co/WxQ9pQh2mY


3. Stock options / ESOPs.

The most common form of equity compensation at early-stage startups that are high-growth.

And there are *so* many pitfalls you'll want to be aware of. You need to do your research on this: I can't do justice in a tweet.

https://t.co/cudLn3ngqi


4. RSUs (Restricted Stock Units)

A common form of equity compensation for publicly traded companies and Big Tech. One of the easier types of equity to understand: https://t.co/a5xU1H9IHP

5. Double-trigger RSUs. Typically RSUs for pre-IPO companies. I got these at Uber.


6. ESPP: a (typically) amazing employee perk at publicly traded companies. There's always risk, but this plan can typically offer good upsides.

7. Phantom shares. An interesting setup similar to RSUs... but you don't own stocks. Not frequent, but e.g. Adyen goes with this plan.

You May Also Like

I like this heuristic, and have a few which are similar in intent to it:


Hiring efficiency:

How long does it take, measured from initial expression of interest through offer of employment signed, for a typical candidate cold inbounding to the company?

What is the *theoretical minimum* for *any* candidate?

How long does it take, as a developer newly hired at the company:

* To get a fully credentialed machine issued to you
* To get a fully functional development environment on that machine which could push code to production immediately
* To solo ship one material quanta of work

How long does it take, from first idea floated to "It's on the Internet", to create a piece of marketing collateral.

(For bonus points: break down by ambitiousness / form factor.)

How many people have to say yes to do something which is clearly worth doing which costs $5,000 / $15,000 / $250,000 and has never been done before.
Still wondering about this 🤔


save as q