Hacker News new | past | comments | ask | show | jobs | submit login
Creating the Commodore 64: The Engineers’ Story (ieee.org)
145 points by rusk on April 3, 2022 | hide | past | favorite | 53 comments



> And outside suppliers were not always reliable. “One provided a power supply for engineering approval,” Ziembicki recalled. “It got approved, and then the supplier changed the design and didn’t tell anybody.”

I wonder if this is why C64 power supplies have a tendency to fail, taking the computer with them?

https://retrogamestart.com/answers/replace-c64-power-supply-...


My first computer was a c64. As a teenager in rural Ireland when my power supply failed it was going to take months to get a new one. I opened up the case and saw the whole insides encased in resin. So with a hammer and screwdriver I started to chip away at the resin until I exposed low voltage dc pins and tested which delivered which voltage etc. I next stole the ac transformer for our doorbell which I remembered had a way to reduce the number of turns and therefore the voltage. Then made a simple rectifier to change it to dc and soldered it to the pins.

Turned on the c64, there was a bang, and a small thick cloud of smoke rose from the back of the machine.

But! It worked and I could play Lotus Esprit Turbo Challenge again until the new power supply arrived.

Never did figure out what the smoke came from. I guess a blown capacitor.


Woah. I've never before heard of a case of the magic smoke leaving a device and it still working afterwards.


Striking similarities between 80's trucks and 80's PCs.


I couldn't believe it!


Heh. Rural Canada here, growing up. Tried to fix one myself, same reason, hard to get.

Ran into the resin, gave up, but your story made me laugh, and brought back a picture, in my mind, of that resin.

Thanks


Seems like implementation would be pretty hard to validate with the whole lot encased in epoxy!


They lacked completely the sophisticated design tools of today’s engineering workstations, but they had one readily available design tool found almost nowhere else in the home-computer industry: a chip-fabrication line on the premises. With this, Winterble explained, a circuit buried deep inside the chips could be lifted out and run as a test chip, allowing thorough debugging without concern for other parts of the circuitry. David A. Ziembicki, then a production engineer at Commodore, recalls that typical fabrication times were a few weeks and that in an emergency the captive fabrication facility could turn designs around in as little as four days.


A solid argument for vertical integration if ever there was one


Only for people, who have not seen dying giants of Soviet industry, which where like large ships - when sink, pull to bottom everybody and everything near them.

Other known problem - "too large to fall" - government try to save such large enterprises so hard, that lead to default.


Same thing happened to the auto manufacturers in Detroit. Used to be one of the richest cities in the world, now one of the poorest and most violent in America.


Most people who talk about the fall of detroit ofter refer to as "bean counters vs car guys" (metrics and commity vs passionate people)and once the company was entirely "bean counters" and all the "car guys" were pushed out it quickly fell.


No. Detroit is the case of overestimate their success, and they just got too much debts.

Usually investors are much more cautious, but in Detroit, used standard scheme of distributed responsibility, where not exists one person, who responsible for bad decision, but these decisions made by committee or by some collegial scheme.

This is also known as one of the biggest problem of democracy - some subject could manipulate others.

In craziest form, one subject could ask other parties with vote power, to jail any other party, and than divide its property between others (who stay free), and repeat this until all others will be in jail, and all property will belong to this creative subject.

In real life, very typical thing, to make mega-projects (which where really created in Detroit), to plunder taxes. BTW this is easy to see, by looking on projects distribution. For example, normal community build lot of cheap projects, but little number of mega projects, and community which is not well enough mature, will attract to mega projects, because they fear to got response of making little things.


You're not wrong on the problems of distributed responsibility.

But Detroit was destroyed by the looting of the American auto industry, which was offshored, outsourced, and automated in the pursuit of efficiencies by people who were well-suited, well-heeled, and not far-sighted. The automakers had been in decline by the 70's, but the manufacturing of automobiles in Detroit sustained that city, and when you remove the chief industry of a city, the results are predictable: the city declines.


Look, in business good CEO estimated as 80% of business value, or if say scientifically, value is depend much more on leadership and on quality of control, than on capital cost.

Detroit before raise of automobile industry was little periphery town, very depressive place like all periphery, so no leadership, no control (in this case, sure mean local government), simply because there where empty place, nothing to control.

In very short time appear automobile industry, which attract capital, but it is unfortunately typical, that business does not care about control, even more - in many cases business struggle against local government.

So that's all history - money tsunami appear, and flooded city; local government was not appear, it can't appear so fast, without special measures (I studying community dynamics and local governments for more than 10 years, and I have not found any facts about special programs to raise level of Detroit local government; unfortunately I seen extremely anti-local government measures); this money flood disappear, left debts.

And unfortunately that's typical history, poor cannot become reach just getting money, he should learn, change his mind.


You mean like Boeing


Definitely, NO! Boeing exists on concurrent market.

And its large size not because it could just have some moderate benefits from size, but because it is impossible to build so large objects within small business.

Just imagine, 747 estimated to 500-700 man-years, nobody will wait even 1/10 of so long.

C64 totally different case.


You and I must have different thoughts about how well Boeing is doing in that space vs let’s say, airbus.


I just compare with different base - really seriously ill Russian enterprises - VAZ, KAMAZ.

And in Russia things are so bad, that few years ago there literally stole jail. - One entity won tender, than few months imitate works and sure, received money, and finally declare themselves bankrupts.


LOL Russia


It is really luck for you, if you could see bad habits of other people and use this info to make yourself better.

Not too much people have such opportunity.


In this case it resulted in a toxic site contaminating the ground water: https://cumulis.epa.gov/supercpad/cursites/csitinfo.cfm?id=0...


Do you think that’s because of vertical integration? I’d have thought you’d run this kind of risk with any sort of industrial facility. It seems they had discontinued this by the time this story commences.


The soundtrack for the C64 game Lazy Jones [1] is a pretty good demo for the legendary SID sound chip. When I experienced it, my computer has a bleepy PC speaker, and my cousin's C64 had a much more "adult" sound.

[1] https://www.youtube.com/watch?v=eWxlYYA8yrg


While the Lazy Jones soundtrack is a pretty good demonstration of how early SID music sounded like, it does not even come close to what more recent music players are able to produce - on the same hardware.

If you want to be blown away by the sounds the SID chip can produce, I would recommend some of LMan's work. This is one impressive tune: https://youtu.be/h0qMNfpiLmE

And this is done with the hardware that Bob Yannes designed for the Commodore 64, in his early 20s.


Wow, that's impressive. The tones are remarkably clear, I wouldn't have guessed it was a Sid (apart from the 3 voices)

Edit: on second listen, it sounds like it has a bit of reverb applied? I wonder if it was recorded from real hardware.


i don't hear the reverb, but...it helps to remember the SID ADSR envelopes are a mix of linear and exponential...can't remember which is which. i believe AD are linear and rel is exp? but since reverb decay is more linear than exp, a linear env can sound a bit like 'verb.

one thing im noticing in this is skipped ticks in the player... mysterious brief random pauses in the sequencer, ouch, heh.


Going off on a tangent, if you liked that clip, I can only recommend to check up LMan's impressive remixes at RKO: https://remix.kwed.org/search/lman

Start with Turrican I end titles and go from there.


While I don't know much about the challenges of designing a computer nowadays, I find it fascinating with how much analog stuff the engineers had to cope back then, and what creative solutions they found (or didn't bother finding) for all kinds of analog signal problems. The article gives a lot of interesting insight into this.


If anything that got worse as clocks got higher, but there is more abstraction in terms of things like tooling to help you get around that. An auto-router from the 80's wouldn't stand a chance to route a modern computer motherboard, essentially every trace is a transmission line, so while nominally it is all digital you are deal with the analog parasitic components all of the time unless you have tooling that will take care of that for you.

You could build a 2 MHz computer on a breadboard and expect it to work. The main analog parts in old computers were at the periphery, the sound DAC, the video drivers (the hardware part of that), TV modulator (usually a module to allow for easy NTSC/PAL/SECAM adaptations), joystick interface (ADC, or switches, depending on the model), cassette tape interface and so on.


You are right about how much harder higher clocks made things. PC mother boards got stuck at 33MHz for the longest time even though 50MHz processors were available. It took Intel coming out with the 486DX2 (50MHz inside the chip, 25MHz on the board) to get things moving again.

A key transition was moving from the 1 and 2 layer printed circuit boards of 1970s e cheap 1980s computers to 4 layers like in the IBM PC and Apple Macintosh. The difference a ground and power plane makes in the waveforms is simply amazing.


It's not very clear, but this is a reprint likely from 1985.


'This article was first published as "Design case history: the Commodore 64." It appeared in the March 1985 issue of IEEE Spectrum.'


I did wonder when I got the line about production of the C-64 "volume shipments began in August 1982 and have continued unabated". I mean, it was good, but good enough to last 40 years?


> the equations describing how it worked were just plain wrong, Yannes recalls. “They didn’t hang together. No one gave me a chance to correct them.”

> As a result, programs made sound effects you couldn’t hear.

Makes me curious if anyone has tried creating a to-spec version of the SID to see how those games would sound.


Wonder if this explains the "crying baby doll" example in the Commodore 64 manual. No one I knew who typed it in ever got it to work but maybe it worked on the SID chip the person who wrote the example for the manual was using but didn't end up working on production implementations.


arg! I was so frustrated with that. Every few years as I got more skilled, I would re-attempt typing it in, and think that I would correct some mistake I'd made in previous attempts... and fail. all it made was clicks :(


I still think there’s a place and need for such “computer-consoles” even today:

Self-contained devices that boot up within a second out of the box, and let you program right away. In this age of course we’ll need a basic GUI, and an app store as well.


I think these days the Raspberry Pi are a reasonable approximation of this experience.


This never gets old… only us c64 kids are… ;)


I was born before the C64 came out. I might indeed be an old.


> Of the original Commodore 64 design team … Albert Charpentier, Robert Yannes, and Charles Winterble, along with David Ziembicki and Bruce Crocket … left Commodore in the spring of 1983 and formed

what became Ensoniq which became part of Creative Technology and E-mu Systems.

Ensoniq made v cool sampler synths. E-mu made advanced audio peripherals. Creative made “SoundBlaster” audio cards for PCs.

Amazing productivity from the same group.


> spring of 1983

Explains a lot!


This is wild. Knowing the budget was a "license to steal".

> The cost of developing the Commodore 64: No one knows. “I had no formal budget accountability,” said Winterble, “other than Jack [Tramiel] watching me. Jack said that budgets were a license to steal.”

They also had more margin in their process which is always good. Process is so tuned today that innovations are missed because there is no room to play.

> Because MOS Technology’s fabrication facility was not running at full capacity, the equipment used for C-64 test chips and multiple passes of silicon would otherwise have been idle. “We were using people who were there anyway,” said Ziembicki. “You waste a little bit of silicon, but silicon’s pretty cheap. It’s only sand.”

Silicon back then was like bandwidth or storage today, those are cheap and can be used to innovate on but tightened later.

> Although custom chips are usually considered expensive, the C-64 chips were not. Not only were development costs absorbed in company overhead, but there was no markup to pay, as there would have been if the chips had been built by another company. And yields were high because the chips were designed for a mature semiconductor-manufacturing process.

C64 having access to in house chips was key in building what they needed and quality levels they needed.

> “It was a lot of fun,” said Ziembicki. “The design people would pick an English screw. The production end would pick metric. But they went with what they had. Commodore production was very good at making things fit whether they were intended to or not. Their charter was 'Ship ‘em’”

Good product people, designers and engineers hold back until quality levels are acceptable.

> “It takes a very tough person,” explained Charpentier, “to say ‘I’m not shipping these because they’re not as good as they could be’—especially when people are clamoring to buy them.”


I have four C64's, 3 still work. They are 40 years old. Not to bad.


Wow!

I have so many times hear about people too much concentrated on one thing so loose all others! I thought, it is known at least from 1970th (The Mythical Man-Month), but again and again see cases of the same..


Love the subtle use of apostrophe in this story title


Aka correct usage.


Yes, which is novel these days.


Maybe I'm missing something, but what is novel about a plural possessive? There are multiple engineers listed in the text, and it tells the stories of all of them.


Oh I’m sorry, as a native English speaker I am familiar with this form since early schooling but as international English becomes ever more utilitarian I am quite used to seeing apostrophes misused or dropped altogether. I think the reason so that now adays most people that engage with the language are non-native speakers who don’t have time for such nuanced syntax.

I would expect such a headline as this to be rewritten nowadays to avoid the apostrophe, or just dropped altogether as ever since “Eats Shoots & Leaves” copyeditors have been hyper conscious about the impact dropped punctuation can have on meaning.

So it’s just nice to see it here, used as nature intended. In particular that it could be dropped and really not impact the meaning at all!


The novelty being that someone knew how to use a plural possessive correctly.


not only that, but they weren't shy about it. Like, in print in 1984 why wouldn't you use punctuation correctly!




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: