[ Phillip Heller is a member of the Prodigy Preservation Project. Here, he writes about his progress since Part 1 in January. –Benj ]

Reverse engineering Prodigy is not without challenges. Though the patent describes the communications protocol and the TBOL language well, it lacks detail of the application protocols – that is, the communications between the Reception System and the server-side applications like Logon, Enrollment, Messaging, and so on.

The progress made last time was to implement the communications protocols and to get the reception system to think it was connecting to the server. Now, we need to move beyond that.

After several months on other projects, I’ve freed up some time, made some significant progress, including successful Reception System login, which I’ll detail below.

[ Continue reading Reverse Engineering Prodigy, Part 2 » ]

[ Please welcome Phillip Heller, VC&G’s newest contributor, who is a member of the Prodigy Preservation Project. Phillip will post more updates on his progress here in the future. –Benj ]

Beginning in the mid 1980s, there were a number of online “walled gardens”. Among them were CompuServe, Genie, Delphi, Quantum Link (later PC-Link, AOL, etc), and Prodigy. The latter two were interesting in that they relied on specific client software to access the service.

Quantum Link was certainly novel for the fact that it furnished a graphical online experience for the Commodore 64, and Prodigy was novel for its use of the NAPLPS graphics standard, client-side P-Code virtual-machine, and hierarchical caching. In the early 2000s, some folks nostalgic for Q-Link set out to reverse engineer it, which was a success with Q-Link Reloaded launching sometime in 2005.

It’d be interesting to do a similar thing with Prodigy: To reverse engineer the client and rebuild a mock server with enough functionality to enable those interested to relive another one of the experiences of the early commercial online world. This is the first in a many part series about doing just that.

[ Continue reading Reverse Engineering Prodigy, Part 1 » ]

After promising this for years, it’s time to finally release the Prodigy Preservation Project’s reverse-engineering tools. They’re not much, and they’re written in Python, but this code is the means by which I’ve been extracting fossilized Prodigy pages from STAGE.DAT files for the past few years.

I have been delaying announcing their availability because I was hoping Jim Carpenter, the author of these tools (and my partner on the Prodigy Preservation Project) would have more time to add more functionality and documentation, but he has not made any changes to the code since late 2015.

Yeah, I know that was almost two years ago. I’m sorry — things move slowly in ProdigyLand.

So here it is, everybody. Have at it. I hope you can help us improve them.

https://github.com/jim02762/prodigy-classic-tools

Just let me know what you find, and I’ll add it to my Flickr galleries.

Just a few minutes ago, I released the first group of images from the Prodigy Preservation Project on Flickr. They’re screenshots from MadMaze, a vintage online game that ran on Prodigy Classic between 1989 and 1999.

Specifically, they’re all the graphics from the Place of Power instances in the game. I believe most, if not all, of the artwork was done by Al Sirois, a Prodigy staff artist. Al Sirois did some of the artwork, but Sirois says that most of it was created by other artists (see comments below). They originated as NAPLPS vector graphics (scalable to any size) and were captured into a raster format for display on the web.

Of course, you can play a re-creation of MadMaze yourself on this very server right here. And you can read more about that re-creation (and report bugs you may encounter) here.

If you’d like to support the Prodigy Preservation Project and all of my history work, please consider submitting a pledge on Patreon. Any money I get from Patreon helps a ton toward giving me the extra time to work on history projects like the PPP.