The 305 RAMAC — First Commercial Hard Drive 244
Captain DaFt writes "Snopes.com has an article that gives an interesting look back at the first commercial hard drive, the IBM 350. Twice as big as a refrigerator and weighing in at a ton, it packed a whopping 4.4MB! Compare that to the 1-4GB sticks that most of us have on our keychains today."
Storage costs... (Score:5, Interesting)
Re:Insightful! (Score:4, Interesting)
Funny story ... (Score:5, Interesting)
So, he was telling me that he figured he could get 2 GB of RAM and 500GB HD for $150. At first, I didn't believe him; then I checked prices, then I almost fell over.
Having personally paid $600+ for 16MB of RAM (and thinking it was a good deal) the fact that for less than $200 you can buy that much stuff shocks me.
Having had computers whose memory was measured in K, that didn't have hard drives, and whose CPU speeds were measured in single-digit Hz
Every now and then when I stop to realize how far we've come it just bakes my noodle! =)
Cheers
funny thing is.. (Score:2, Interesting)
Like all old IBM gear, it was fun to watch (Score:5, Interesting)
It only had a single head, so it basically move in two dimensions. It would retract all the way out from the stack of disks then zip quickly to another disk and insert itself to read the other disk. During the visit I briefly saw it "vibrating" crazily back and forth on one of the disks. It was explained to me that it was copying a file.
They all had those great big lighted buttons; separate on and off buttons, no push-on-push-off nonsense. the "on" button was always slightly recessed, while the "off" button always projected slightly, so that any one accidentally bumping against the machine would be turning it off rather than on...
Re:Storage costs... (Score:4, Interesting)
Now be nice and don't make any "soviet Russia" jokes about this comment, ok?
-mcgrew [slashdot.org]
Re:Where are my $20 Hard Drives (Score:3, Interesting)
Give it another few years. You can get a 10gb hard drive housed in a computer fof fity, including monitor, mouse, and keyboard. Used, of course, but you know what they say about begging and choosing.
-mcgrew [slashdot.org]
Re:Yeah, but, but ... (Score:5, Interesting)
My initial response to this was "of course it does, stop being a troll" like many others commenting with this over-played cliche.
I then thought about it harder and realized there aren't many distros that run in less than 5MB. There are distros that do it, but not many unless they're hardware router disks. This gave me the gut feeling that the answer may be yes, but then I remembered... this is well before x86 architecture became mainstream.
I then looked into the architecture of the 305 RAMAC and found a decent wikipedia article [wikipedia.org] on the subject. Among the interesting things about the architecture is that characters were only 7 bits! FTLA:
Programming heroics. (Score:5, Interesting)
The drum memories I used had one head per track, as did the head-per-track disks. In that case, seek time is zero (for head movement.) One need only wait for the latency time for the bytes you want to rotate under the head. Depending on rotation speed, latency could be as much as 5 to 15 milliseconds.
The amusing part, when I think back on it, was the way that the hardware design influenced the programming. Suppose you had a clause that looked like: IF X THEN A ELSE B ENDIF. To make your program run as fast as possible, you would arrange it so that the instructions for A and for B would reside on two different tracks at the same azimuthal angle, (right behind the instructions to evaluate IF X.) That way, no matter whether the branch evaluated true or false, one didn't have to wait for additional memory latency to read the next instruction.
We also didn't have room in RAM (core memory or registers at that time) to store data or calculated results. We had as few as 24 bytes of RAM. Thus, each data value also had to be assigned an address on the drum or disk. The location of that address relative to the code which accessed the value had a dramatic impact on program speed.
Therefore, to optimize programs for running speed, we spent more time devising optimum ways to store the code and data fragments on the drum or disk, than we did designing the functionality of the code. What language and OS did we use? No language, just program the instructions one bit at a time. No OS.
So what fancy apps did we do with this spaghetti software? We did real time control of power plants, both conventional and nuclear. We made flight simulators. We supported the Apollo project to send a man to the moon.
Despite the fact that the computers of those days were as much as 10,000 to 100,000 times slower than today's hardware, the real time applications were only 10 to 100 times slower and/or of lesser scope compared to today's apps. It was because of the extreme squeeze-blood-out-of-a-stone coding methods we used in those days.
For a really good story, get someone to write about how they streamed instructions sequences from earth to the Lunar Excursion Module for Apollo 11. Not streaming video, not music but streaming the code to execute. Buy the time one machine instruction would finish, the next one would be received and read to go. It was just-in-time delivery of the next instruction. That way, they needed no onboard mass storage of any kind. In my book, that was programming heroics that any slashdotter should appreciate.
I saw one "live" (Score:3, Interesting)
At Perot Systems where I worked most of this year, there's a courtyard containing many historical computer artifacts including one of these 305 disk cabinets. For contrast the curator of the "museum" placed a 40GB iPod (with the cover removed) within the case and there's a side by side comparison chart at the base of the cabinet. I forget all the statistics but it compared weight, cost, power consumption and of course, amount of data stored: 305 = 1 song, iPod = 2,000 songs. The actual character storage was extrapolated to provide more impressive numbers as well.
It made me curious whether or not it would run if it were connected today. I'd wager it would, but it would take some of the other machines in the museum to talk to it.
We built 38" removable platter prototypes for IBM (Score:4, Interesting)
While I was working for an AeroSpace Sub-contractor in 72/73 we built prototype 38 inch removable HD platters for IBM.
These were built using different core materials (mag V honeycomb) and various bonding materials/techniques.
I don't know if they ever went into production, since I joined the Army before the project was finished.
There I learned to operate a 258lb portable computer - powered by a towed generator - that had 12k of core memory and a 8-level paper tape reader.
"Total domination is bad. The Microsoft dominance already badly misled people about how to choose systems. Instead of 'what tool do I use for the job' it's 'well it was shipped with the box'. Linux is a tool, Windows is a tool and so are numerous other systems. It's really important people go back to looking for the right tool for the job. That will never always be Linux. No single tool can do everything well." Alan Cox
Re:Programming heroics. (Score:3, Interesting)
the fastrand ii was, of course, the next generation or so after the 305 ramac. transistors instead of tubes, it was a 90 megabyte drum that wieghed 2.5 tons. so storage went from 5 MB per ton in 1956 to 35 MB per ton in 1968.
http://www.fourmilab.ch/documents/univac/fastrand.html [fourmilab.ch]
Re:Storage costs... (Score:3, Interesting)
Oh, you mean how many physical cards could you fit in that space? :-)
Well, according to IBM, "Assembled with covers, the 350 was 60 inches long, 68 inches high and 29 inches deep." Pausing to convert to metric, that's 1524mm x 1727mm x 737mm, for a total volume of 1,939,745,676 mm^3. A MicroSD card is 11 x 15 x 1mm (LWD), or 165 mm^3. So you could fit 11,756,034 cards in the space occupied by that cabinet, and they would hold 25,245,890,780,332,032 bytes (22 petabytes.)
Since you're spending all the money, though, why not go for SanDisk's 8GB MicroSD, which would yield almost a hundred petabytes? That's a storage density 11 orders of magnitude higher than the original, in only 50 years.
Moore's Law, you rock!