{"id":1063,"date":"2014-07-14T13:17:43","date_gmt":"2014-07-14T18:17:43","guid":{"rendered":"http:\/\/www.vintagecomputing.com\/?p=1063"},"modified":"2024-09-18T10:08:49","modified_gmt":"2024-09-18T15:08:49","slug":"bringing-prodigy-back-from-the-dead","status":"publish","type":"post","link":"https:\/\/www.vintagecomputing.com\/index.php\/archives\/1063\/bringing-prodigy-back-from-the-dead","title":{"rendered":"The Prodigy Preservation Project"},"content":{"rendered":"

\"Prodigy<\/a><\/p>\n

[ Major Update: 4\/12\/2017<\/strong> – Keep an eye on my Flickr account<\/a> where I will be posting galleries of Prodigy screenshots and other artwork. ]<\/em><\/p>\n

[ Major Update: 6\/6\/2017<\/strong> – Our Prodigy Reception System reverse-engineering tools have been released<\/a>. ]<\/em><\/p>\n

[ Major Update: 1\/15\/2021<\/strong> – Phillip Heller has begun reverse-engineering<\/a> the Prodigy client. ]<\/em><\/p>\n

[ Major Update: 8\/6\/2022<\/strong> – I wrote the first new Prodigy content<\/a> in 23 years. How is that possible? Phillip Heller has reverse-engineered the Prodigy Client\/Server architecture, and you can connect yourself with Prodigy Reloaded<\/a>! Prodigy Reloaded debuted at VCF West<\/a> on August 6, 2022. Finally, the Prodigy Restoration Project is coming to life. ]<\/em><\/p>\n

Since last year, I have been working with Jim Carpenter, a freelance programmer by trade, on hunting down old Prodigy<\/a> data so that we may preserve it, display it again, and perhaps even one day use it to recreate Prodigy itself.<\/p>\n

We’re calling it the Prodigy Preservation Project.<\/p>\n

By now you may have seen my latest piece for The Atlantic entitled Where Online Services Go When They Die: Rebuilding Prodigy, One Page at a Time<\/a>. That article describes the genesis of the project while also diving into the technical back story of the Prodigy service.<\/p>\n

The reason we have any hope of doing something like this is because Carpenter discovered that Prodigy screen data can still be found in the STAGE.DAT and CACHE.DAT files located in used Prodigy client directories.<\/p>\n

Those two files were used as cache files to speed up load times when using the service. When connecting to Prodigy, the client would download page data into the files. Whenever the client last connected to Prodigy, that data got frozen in time. If a vintage Prodigy client install still exists, we can get at the “frozen” data today.<\/p>\n

Here are some screens that Carpenter pulled from a STAGE.DAT I had in my personal archives (these are from a STAGE.DAT file dated October 6, 1996):<\/p>\n

\"Prodigy<\/a> \"Prodigy<\/a> \"Prodigy<\/a> \"Prodigy<\/a><\/p>\n

\"Prodigy<\/a> \"Prodigy<\/a> \"Prodigy<\/a> \"Prodigy<\/a><\/p>\n

We can extract these screens using a series of Python programs written by Carpenter. They read through a previously used STAGE.DAT file, generate a list of pointers to the pages or object data contained within, then direct the Prodigy Reception System client to display them one at a time so we can take screenshots.<\/p>\n

Jim’s code is not ready for release yet, but he hopes to polish it up enough to put up on GitHub soon. It has a long way to go before becoming a turnkey solution to extracting and displaying the data found in STAGE.DAT files. We’re working on it.<\/p>\n

With that in mind, I’ve written the rest of this post in the form of a Frequently Asked Questions.<\/p>\n

<\/p>\n

How Can I Help?<\/h3>\n

After looking around for more Prodigy installations on and off for the past year, Carpenter and I recently decided to go public with our project and ask for your help. If you have any previously used Prodigy client installations sitting around in backups or on old hard drives somewhere, we would love to hear from you<\/a>.<\/p>\n

Can I Provide Financial Assistance?<\/h3>\n

Yes. In fact, I have set up a Patreon campaign that will partially fund<\/a> all of my history-related work, including the Prodigy Preservation Project. Your pledge will give me more time to devote to the PPP.<\/p>\n

What Do You Need?<\/h3>\n

In order for a Prodigy client directory to contain any useful data, that particular installation had to be used to connect to Prodigy at some point.<\/p>\n

This means that we do not need original Prodigy installation disks; they were never used to connect to the service, and thus do not contain any downloaded data.<\/p>\n

So if you find a Prodigy client directory that is sitting on an old hard drive or in an old system backup, ZIP up the whole folder\/directory and send it to us<\/a>.<\/p>\n

How Can I Send You My Data?<\/h3>\n

Carpenter and I are working closely together on this project at the moment, and I am acting sort of like a data secretary for him, obtaining data and organizing it in a shared repository so he can go through it when he gets the chance (he professes to be a perpetually stressed, last-minute deadline programmer that is always short on time).<\/p>\n

I’ll also be using Jim’s software to extract what I can. But his software still needs improvement — it only works with MS-DOS Prodigy clients as of this writing, for example — so this whole project is very much a work in progress.<\/p>\n

If you find any data from any platform, describe what you’ve got in an email to me<\/a> and attach the data in a ZIP file.<\/p>\n

Who Are You and Why Are You Doing This?<\/h3>\n

My name is Benj Edwards and I am a tech journalist that specializes in computer and video game history. For the past nine years<\/a>, I have been professionally researching, interviewing, and writing about tech history with a goal to both preserve and educate. I have also run this blog since 2005.<\/p>\n

I am working on this Prodigy project because I have always been fascinated with online services since I was a kid. I first connected to Prodigy in 1992<\/a> and was amazed. Today, if you look for info on Prodigy online, you will find very little information about it (especially in terms of screenshots), and that is a shame.<\/p>\n

I believe the old Prodigy data is worth preserving as a cultural treasure from the early online era. It was a cultural reference point of an entire computer-using generation that grew up with it, and it is now missing from our cultural heritage. At the moment, no one can go to a library or a website and see what was on Prodigy back in the day, so in future generations, we won’t be able to point to it and say, “See? This is what it was like.”<\/p>\n

Reasons for preserving this data are too numerous to go into here, but they will become more obvious to everyone as people continue look at the past in a search for information on the formative experiences that made them who they are today. (By the way, whole families were founded on Prodigy, with their parents having met on the service, so this inquisitiveness will continue for generations to come.)<\/p>\n

What Are You Going to Do With What You Find?<\/h3>\n

For now, I am planning a gallery of every Prodigy screenshot I have ever found. It may end up on Flickr or this site, so stay tuned.<\/p>\n

As for screens extracted from STAGE.DAT files, so far the only STAGE.DAT that had usable data was the one I found last year in my archives. But in the past few days, I’ve received three more promising Prodigy directories that we will be looking through soon. We will add whatever we find to our Prodigy screenshot gallery.<\/p>\n

In the long term, I would ideally like to create a simulation of Prodigy with a Reception System written in Javascript (so it can run in any browser). It will deliver original Prodigy data to users and allow them to experience what the service was actually like back in the day. That is a potentially huge project that is a long way off, however.<\/p>\n

Less ambitiously (but still ambitious), Jim would also like to create a Prodigy server simulation that can deliver original Prodigy objects to the original Reception System client.<\/p>\n

In the mean time, Jim and I will be going through the data and sharing what we find. <\/p>\n

I Don’t Have a Prodigy Client, But I Have Other Prodigy Information. How Can I Help?<\/h3>\n

Carpenter and I are working on reverse engineering the entire Prodigy service, backend and frontend. If you have any internal Prodigy documents that describe, in detail, how any part of Prodigy worked, we would love to see it<\/a>, as it will be very helpful in our mission.<\/p>\n

I’m also working on a general history of the service, so literally anything and everything can be useful. Personal stories of using the service, documents, photos, software, data, code, internal Prodigy software tools, screenshots, artwork. You name it. All of it will be useful in building a more accurate historical record of this most unique online service. Send me an email.<\/a><\/p>\n

What Happened to The Original Prodigy Data That Was On Its Servers?<\/h3>\n

Good question! I’m currently talking to ex-Prodigy employees about whether that data even exists at all at this point in time. I’ve discovered some interesting tidbits, but it’s too soon to say anything definitive. If you know anything about it, please send me an email.<\/a><\/p>\n

How Can I Search For Old Prodigy Installations?<\/h3>\n

If you want to do a targeted search for old Prodigy data, I have a few tips.<\/p>\n

    \n
  1. Look in your own archives. <\/strong> This is what I did when Jim told me about his Prodigy technique last year. While I didn’t find my original Prodigy client installation from 1992, I did find a backed-up Prodigy client directory from 1996. Obviously, you have to be a bit of a data pack rat for this method to be useful.<\/li>\n
  2. Ask around.<\/strong> Find old Prodigy users, and ask them to look through old system backups, which may be on floppy disk or CD. Or they may simply have their old PCs with intact hard drives still inside. You may have to help them liberate the Prodigy data from various obsolete storage formats.<\/li>\n
  3. Target IBM PS\/1 machines.<\/strong> The Prodigy client shipped with most consumer IBM PCs after the service’s launch in 1988. That means if you find, say, an in-tact IBM PS\/1 of any model from the early 1990s, or some PS\/2s, it is very likely to have a Prodigy directory sitting on its hard drive. If the user of that machine tried Prodigy even once, it should have some useful data in its STAGE.DAT and CACHE.DAT files.\n

    Also, you can target the hard drives that commonly shipped in IBM PS\/1 machines. I determined common models a few months ago, but I need to find my notes and put that info up here later.<\/li>\n

  4. Search Hard Drives in Bulk.<\/strong> Another approach is to comb through bulk collections of old hard drives. PC hard drives under 500 MB (all IDE Parallel ATA drives) are most likely to have a form of Prodigy Classic client on them. I myself have done this, buying up dozens of scrap and surplus hard drives and searching for STAGE.DAT files in them. It is a needle-in-a-haystack approach, but it is faster to search through bulk collections of hard drives than to buy 100 old PCs, move\/ship them, and go through them one at a time.\n

    Obviously, user privacy is of the utmost importance when handling used drives with personal data on them. Luckily, if you scrape out a C:\\Prodigy directory, it’s almost guaranteed to have no personally sensitive information on it. It is your responsibility to then securely discard data on the rest of the drive. Of course, if you do that, you may also lose some other data of historical value on the drive that we don’t even know is important yet. You’ll have to cross that ethical bridge when you come to it.<\/p>\n

    By the way, using this method, I have found no working Prodigy directories (it is, admittedly, a long shot), so I stopped after going through about 100 hard drives. The biggest problem for me is that 90% of the hard drives I could obtain were too recent. I asked around, and most MS-DOS era drives have been sold as scrap and shredded years ago. But it’s still a possible approach if you have access to a stack of old drives.<\/li>\n<\/ol>\n

    The Project Continues<\/h3>\n

    Thanks for everyone’s help so far, including the dozens of ex-Prodigy personnel I have spoken to about their amazing work with the service. I wrote this information out as quickly as possible, so I will likely keep revising it over the next few days. Keep an eye on this blog (and this post) for future updates.<\/p>\n

    [ Edit: 04\/12\/2017<\/strong> – I changed the name of the project from the “Prodigy Restoration Project” to the “Prodigy Preservation Project” to reflect the growing role of our simply collecting Prodigy screenshots and documents for preservation. Re-creating the Reception System in Javascript is still a goal, however.]<\/em><\/p>\n

    —
    \nBenj’s Other Writings about Prodigy:<\/em><\/p>\n

    Classic Prodigy Game Recreation MadMaze-II Updated to Support Chrome and Firefox<\/a> (VC&G<\/em>, 2017)
    \n    Exploring the Lost World of Prodigy<\/a> (PCWorld, 2016)
    \n    Where Online Services Go When They Die<\/a> (The Atlantic, 2014)
    \n    The New Prodigy (Retro Scan)<\/a> (VC&G<\/em>, 2014)
    \n    MadMaze-II Now Hosted on Vintagecomputing.com<\/a> (VC&G<\/em>, 2013)
    \n    Prodigy 20 Years Ago Today<\/a> (VC&G<\/em>, 2012)
    \n    Prodigy Lives! Play MadMaze On the Web<\/a> (VC&G<\/em>, 2006)<\/p>\n","protected":false},"excerpt":{"rendered":"

    [ Major Update: 4\/12\/2017 – Keep an eye on my Flickr account where I will be posting galleries of Prodigy screenshots and other artwork. ] [ Major Update: 6\/6\/2017 – Our Prodigy Reception System reverse-engineering tools have been released. ] [ Major Update: 1\/15\/2021 – Phillip Heller has begun reverse-engineering the Prodigy client. ] [ […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[20,7,35,21,5,10],"tags":[],"class_list":["post-1063","post","type-post","status-publish","format-standard","hentry","category-bbs-history","category-computer-info-and-history","category-internet-history","category-news-current-events","category-vcg-announcements","category-computers"],"_links":{"self":[{"href":"https:\/\/www.vintagecomputing.com\/index.php\/wp-json\/wp\/v2\/posts\/1063","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.vintagecomputing.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.vintagecomputing.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.vintagecomputing.com\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.vintagecomputing.com\/index.php\/wp-json\/wp\/v2\/comments?post=1063"}],"version-history":[{"count":8,"href":"https:\/\/www.vintagecomputing.com\/index.php\/wp-json\/wp\/v2\/posts\/1063\/revisions"}],"predecessor-version":[{"id":3515,"href":"https:\/\/www.vintagecomputing.com\/index.php\/wp-json\/wp\/v2\/posts\/1063\/revisions\/3515"}],"wp:attachment":[{"href":"https:\/\/www.vintagecomputing.com\/index.php\/wp-json\/wp\/v2\/media?parent=1063"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.vintagecomputing.com\/index.php\/wp-json\/wp\/v2\/categories?post=1063"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.vintagecomputing.com\/index.php\/wp-json\/wp\/v2\/tags?post=1063"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}