Slashdot Mirror
Retrieving Data From Old Amstrad Floppies?
Jeppe Utzon writes "Back in 1987, when I was a teenager in high school still, I spent most evenings, nights and weekends writing small programs in BASIC on my Amstrad CPC 6128. Some of these programs were simple games, some drew graphics, some could help me with math or train me in French — and most were utterly pointless. But I never had as much satisfying fun as when writing those programs — even if no one in my family understood any of it when I proudly displayed the fruits of three sleepless nights of labor. Now, 20 years later, I still have a sealed pack of about 15 disks with all my work on them (along with a few of my favorite games) and I was wondering if it was possible to get the data out somehow so that I could run it in emulation on my Mac. I know of the emulators, but have no clue what would be needed to extract the data — or if it is even extractable after all these years. I realize the chances of the data still being intact are quite low, but I'd like to give it a shot. So if anyone has any pointers it would be greatly appreciated."
A large hurdle will be finding a drive to read the Amstrad disks at all.
I'm sure that will be the problem. Unless you search on Ebay or Craigslist for someone with one in their basement....good luck. I have a 5 1/4 floppy drive and some disks set aside for the exact same reason.....someday I'll want that info and then I'll be all set.
WTF? Over?
My first programming was on punched paper tape, which I can still read. I am not saying I have a machine that could read it, but at least I can look at the punches and figure out what the characters were.
When I was in grad school, there was some data stored on punched paper tape, stored fan-folded. The tape had dried out and cracked where the folds were. (The cracks would be in the middle of a byte, especially a high one, as they would have more holes punched in them.) They wanted to save the data, so they hired a under-grad to spend all summer sending the tape through a reader, one 4 foot section at a time, figure out what the byte was where the crack was, type that in, and then proceed to the next 4 foot section. I still think that that must have been the worst IT job ever.