WD1772 16MHz Myth
Read this before anything else on this page. This has been tested more thoroughly than anything published on the subject before it, with a control chip re-verified between every swap and every 16MHz failure re-checked at 8MHz. But it is still a bench test of a few dozen chips over a few days, not hundreds of chips over hundreds of hours, which simply is not realistic for one person to do. Treat this as the best indication available, not as gospel. Some questions below are genuinely still open, and are marked as such rather than glossed over.
WD1772 at 16MHz: the 02-02 myth, tested
For as long as anyone can remember, the accepted wisdom around the Atari scene has been that only the WD1772 "02-02" revision will run at 16MHz for 1.44MB high density support, and that the earlier "00-02" revision simply won't. This page traces where that claim actually came from, what Western Digital's own datasheets say, and the results of a proper bench test of real chips, run to try and settle it.
Where the "only the 02-02 does 16MHz" claim came from
The earliest identifiable source is a text called "Introduction and Notes for adding High density disk drives to the Atari ST", written by someone using the callsign GW6HVA and circulated on UK packet radio via the BBS GB7OSP. It states plainly that the WD1772 "carries a suffix (usually) of 00-02 or 02-02", that the chip is "designed to run at 10MHz" and that "only the 02-02 chip will handle the higher clock speed of 16MHz" – with no mention of heat, duty cycle, or any chip-to-chip variation, and critically, no stated sample size. Nowhere in this text, or in anything that repeats its claim since, does anyone say how many chips were actually tried. For all that is known, it could have been exactly one 00-02 that didn't work and one 02-02 that did, on a single evening thirty-odd years ago, which then simply became accepted fact through repetition. That gap is worth naming plainly, since it is precisely the kind of omission this page is trying not to repeat. It circulated bundled with a formatter utility dated September 1989, so the claim itself predates the web entirely. The oldest surviving online copy is a 1998 Usenet repost, now archived at the Cleveland Free-Net Atari SIG.
The softened version sometimes quoted, that "ST Format said only about 5% of 02-02 don't work", has no located source at all – it is a 2012 forum recollection of an uncited magazine article. No issue number, date or scan has ever been produced for it. Wikipedia's claim that the "WD1772PH02-02" officially supports 500kbit/s HD carries a citation-needed tag on the article itself. And the account given by Best Electronics, a long-standing Atari parts dealer, says the opposite of a purpose-built chip: that Western Digital never designed the 1772 for 16MHz at all, and that Atari simply hand-selected and tested chips that happened to survive the overclock for the TT.
What Western Digital's own datasheets actually say
Both the WD177X-00 and the WD1772-02 datasheets, from the 1986 WD Storage Management Products Handbook, carry an identical Miscellaneous Timing table for the clock input: a duty cycle of 50 to 67 nanoseconds each phase. A 50ns minimum half-period works out at 10MHz, which is very likely where the "designed for 10MHz" line in the original packet radio text actually comes from – traceable to WD's own numbers, not invented, even though both datasheets separately specify the clock as 8MHz ±0.1%. What matters most: those timing figures are the same on both revisions, and 16MHz needs a 31.25ns half-period, nowhere near either chip's 50ns minimum. Neither revision of the WD1772 was ever specified anywhere near 16MHz. That is the strongest documentary evidence against the myth, and it applies equally to both.
Chip markings: what was checked, and what it ruled out
Before any bench testing, a fair amount of effort went into whether the markings on a chip's package could predict anything. None of it held up.
- A second line sometimes seen on the package, such as C026028, is Atari's own part number, applied to chips that went through Atari's own production – not a sign of special testing or vetting. In 1986 the FDC ran at 8MHz exactly as specified, so there was nothing to screen for at the time.
- Date code does not predict the outcome. Two chips sharing the exact same production week gave opposite results at 16MHz.
- Country of assembly does not predict it either, and in this sample is confounded with revision anyway – the 00-02 stock tested happened to be entirely Korean-marked, the 02-02 stock Malaysian and Taiwanese.
- Lot code, the most specific marking available, does not predict it either. A working chip and a failing chip, both 00-02 and both the same date code, were checked right down to the lot code stamped on the underside of the package. Identical, top and bottom. Same lot, opposite result.
So every single thing that can be read off the outside of the package has now been checked, and none of it tells you anything reliable.
Bench test method
All testing was done on the same board and drive, using an external 16MHz oscillator rather than a Shifter-derived clock, and a write-protected reference disk. A known-good chip was re-fitted and re-verified between every chip swap, so that any drift in the test rig itself would be caught rather than mistaken for a chip result. Every chip that failed at 16MHz was then run at 8MHz, to confirm it is a working part that simply won't take the overclock, rather than a dead chip skewing the figures.
| Marking | Date code | Result at 16MHz |
|---|---|---|
| 02-02 | 9427 | OK, two units |
| 02-02 | 9522 | OK |
| 00-02 | 8614 | OK |
| 00-02 | 8618 | FAIL, three units, all load fine at 8MHz |
| 00-02 | 8622 | OK x2, FAIL x1 (loads fine at 8MHz) |
| 00-02 | 8627 | OK, three units |
One 00-02 (8622) that passed a short run went on to accumulate roughly four hours of near-continuous 16MHz operation across several restarts. Deliberately heating that same chip with a soldering iron reliably induced failure, and it recovered fully once allowed to cool, which at least confirms the failure mode is thermal margin rather than the chip simply being dead.
The decisive finding, and why it's an unsatisfying answer
Every marking available – date code, lot code, country, Atari part number – has now been checked against outcome, and none of it predicts anything. A working chip and a failing chip from the same lot are, as far as anyone can tell from the outside, identical. The honest conclusion is that whether a given WD1772, of either revision, will run reliably at 16MHz is not something that can be known without trying it. That applies across the board: this is not a property of the 00-02 revision that the 02-02 doesn't share, it's a property of individual silicon.
What is still genuinely open
- Whether 8618 is a genuinely bad production lot, or just an unlucky small sample. All three units tested failed, and all three share the same underside lot code – which on its own would look like strong evidence of a bad batch. But the lot-code finding above shows lot code does not determine outcome in general, since a working and failing 00-02 from a different date code share an identical lot. So this is a genuine tension in the results rather than a tidy answer: it may be that 8618 really is a bad lot, or it may simply be that three chips is too small a sample and a fourth or fifth 8618 would break the pattern. More 8618 units would need testing to know for sure, and none are currently available to test.
- Whether the 02-02 is actually more reliable than the 00-02 at 16MHz. This has not been shown either way. It is the assumption almost everyone in the community makes, on the strength of the original myth, but that is exactly the myth this page exists to test. Meaningfully more 02-02 testing is needed before any claim about relative reliability could be made, and none has been done yet at anything like the scale of the 00-02 testing above.
- All testing here used an external 16MHz oscillator, not a Shifter-derived clock. Thirty years ago the Shifter's own 16MHz output was simply noted as a problem to avoid, without really understanding why, since it caused sporadic failures that were never pinned down at the time. The datasheet finding above gives a solid reason: WD specify the clock input as needing a clean, free-running 50% duty cycle, and the Shifter's output does not meet that well at all. That is very likely the real cause of a lot of the old, seemingly random 16MHz failures nobody could previously explain. A clean external oscillator is essentially mandatory, and every result on this page depends on having used one.
- Sustained, continuous 16MHz operation over many hours or days has not been tested by anyone, including this project. Roughly four hours is the longest clean run achieved so far. Access-only switching, where the FDC clock only goes to 16MHz while a drive is actually being used, is a different and much lighter load than any of this testing, and is well supported by every chip that passes at all.
Have more information? Or want a chip verified?
If you have a genuine Western Digital document that specifies 16MHz for either revision, a WD1772 you've tested that adds to the picture above, or anything else that would make this page more accurate, please get in touch via the exxos forum. This page will be updated as better information comes in.
Happy to run a chip through the same test rig if you want one verified and send it in, on one condition: it needs to have come out of, or have a solid paper trail back to, original equipment. Chips bought in from China are not usable for this, since so many of them turn out to be re-stamped, and at that point there's no way to know what the original part underneath actually was. A chip pulled from a real ST, or genuine new old stock with a traceable source, is what's needed for a result here to mean anything.
Sources and credit
Datasheet research, myth sourcing and bench testing by exxos (Chris Swinson), 2026. Primary datasheet source: the 1986 Western Digital Storage Management Products Handbook. Best Electronics' account of the Ajax history is on their custom chips page. See also the WD1772 Floppy Disk Controller reference page for the full register and command-level datasheet corrections this project also produced.