fosstodon.org is one of the many independent Mastodon servers you can use to participate in the fediverse.
Fosstodon is an invite only Mastodon instance that is open to those who are interested in technology; particularly free & open source software. If you wish to join, contact us for an invite.

Administered by:

Server stats:

8.6K
active users

#corememory

0 posts0 participants0 posts today

Before experimenting with magnetic cores for transient storage, #JayForrester was casting around for other potential electronic devices which might function as fast memory for the real-time #Whirlwind #Computer. The team had discounted mercury delay lines and magnetic drum memory, with their serial access, as too slow for Whirlwind. The team was working on their own implementation of Williams tubes, but these were endlessly problematic and not as fast in practice as theory indicated.

In 1947 Forrester even had briefly considered using interconnected "gas glow discharge cells" in three-dimensional array, for these offered such advantages, at least theoretically, as "high initial breakdown voltage," "...low holding voltage, and low forward impedence [sic] after breakdown..." But investigations were "soon dropped because of the variability of the individual cells with time and from sample to sample."

From the 1967 manuscript "PROJECT WHIRLWIND: A Case History in Contemporary Technology" by Kent C. Redmond and Thomas M. Smith available at bitsavers.informatik.uni-stutt published in 1975 by The MITRE Corporation and republished in 1980 by Digital Press (yes, that Digital) in a gorgeous hardback edition with superbly reproduced black and white photos.

There's little technical information about the development of the computer in the book; instead, the book is about the institutional, systemic and political pressures that gave Project Whirlwind the complexion that it had.

Thanks to a book recommendation by @bert_hubert [1], I went on a tangent learning more about the absolutely fascinating history and workings of core memory (and core rope memory, its read-only version). Some of this also very interesting for #PermaComputing and giving me ideas for future art projects...

Apollo Core Rope Memory (restoration and read out of 50 year old memory from the Apollo Guidance Computer)
youtube.com/watch?v=hckwxq8rnr

Core Memory Explained and Demonstrated
youtube.com/watch?v=AwsInQLmjX

[1] eupolicy.social/@bert_hubert/1

MUDs and the ability to reload new server without dropping connections (a “hotboot”)…

boston.conman.org/2025/02/11.2

…reminded me of an old RSX-11M application from an aeon ago, running part of a state government.

The app was too big for the PDP-11 (a common problem, as 32KW wasn't all that much even then), so the app removed the operating system from the computer, and ran, well, standalone.

Yes, you could do that back then.

That all worked swimmingly until somebody pressed ^C control-C on their terminal session, and the terminal driver then trapped into, well, nothingness.

Since the app code was too big for the PDP-11 it was running on, that smaller PDP-11 was shut down, the bigger local PDP-11 was switched over and re-booted and the app code loaded, and the bigger PDP-11 was then powered down.

The operator then pulled the core memory out of the bigger PDP-11, walked it over to the smaller PDP-11 and plugged it into the backplane, toggled in the address of the app's main loop onto the front panel switches, and toggled “go”, and off the smaller PDP-11 went running its too-big app.

Yeah, you could do a simple form of app checkpoint-restart with core memory, given core was persistent. And yeah, a bigger PDP-11 would have been helpful.

(Yes, SC was a creative administrator of those PDP-11 boxes. Swapping core never would have occurred to me.)

The Boston DiariesI never got the memo on “copyover servers” - The Boston Diaries - Captain NapalmI never got the memo on “copyover servers”
Replied in thread

@mavica_again @cstross @NF6X also lets be clear, @NanoRaptor does "Premium" #Shitpost|s or rather "#NextLevel #Memes" to the point that I'd not be surprised if she makes a #NeoFloppy / #Jaz / #Zip mashup and showcases a nonexistant "vintage" portable SSD with like old #ROM chips or #RAM chips...

  • I mean, the only reason #ODD's and #HDD's ever got built is because #CoreMemory and other storage couldn't scale up faster.

But #WhatIf it did?

No collection is complete without a core memory module. In my case from a Saratov-2 computer manufactured in the USSR.

The individual rings are smaller than the head of a pin, amazing!

As soon as I have a macro lens for my camera, I will take new photos. Additionally I'll add something for scale...

For more information:
rusue.com/cemetery-of-soviet-c
curiousmarc.com/computing/core

In 1972, #core #memory was manufactured in #Dublin by the Irish subsidiary of US-headquartered Dataproducts, trading as "Data Products/Core Memories Ltd."

They made what they claimed was "...the world’s largest core stack, 131K x 80". Judging by the info in the caption, the latter number is the number of bits per word, so in eight-bit bytes, that's 1,310 kilobytes.

I can't imagine that business survived more than a couple more years. Soon the semiconductor manufacturers had set up shop in Ireland.

#vintage #computer #hardware #history #CoreMemory #OtherGeographies #Ireland

en.m.wikipedia.org/wiki/Datapr

Here is a link (cued to the time where it starts) of the best and most clear explanation of how core memory works. Reading & writing a bit has many steps!

Now I want to know how modern memory works with a similar level of detail.

I always felt there was something poetic about how one must destroy this kind of memory in order to read it. Observation is never passive... to observe a system is to change it... #computer #memory #history #coreMemory #cs

youtu.be/AwsInQLmjXc?list=TLPQ