[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Help me get my childhood Apple //e running again
- Subject: Help me get my childhood Apple //e running again
- From: Tom Moertel <tmoertel@gmail.com>
- Date: Sat, 28 Apr 2012 15:01:03 -0700 (PDT)
- Complaints-to: groups-abuse@google.com
- Injection-info: glegroupsg2000goo.googlegroups.com; posting-host=98.111.198.82; posting-account=q5Fe7QkAAACxp4qGskxoqrkPnijbgtxF
- Newsgroups: comp.sys.apple2
- Organization: http://groups.google.com
- User-agent: G2/1.0
When I read the recent Wired story about recovering the original Apple 2 source code for Prince of Persia, alarm bells sounded in my head. I was sitting on a bunch of old 5.25-inch floppies, many containing programs I had written as a kid, and they were rapidly fading away. If I wanted to save them, now was the time.
So I called up my parents and asked if they still had my old Apple //e in storage. And they did! So I met with them one evening and picked it up.
When I got home, I couldn't wait to unbox it. Here are some photos:
https://plus.google.com/photos/103957126301745359889/albums/5735897279553029889
After I got everything set up, I flipped the switch. For the first time in nearly three decades, I heard the familiar beep and the Disk II's ker-chunka-chunka-chunka recalibration. It was exciting! But then I discovered that something was wrong.
When I tried booting from a ProDOS disk, I got a relocation error. And then when I tried other DOS 3.3 disks, the programs on them would seem to load but then fail. When I tried a program that displayed HiRes graphics, I could see some vertical glitches on the screen.
Darn!
It's a //e enhanced, so I tried the built-in diagnostic. The problem is, I seem to be getting unreliable results. Sometimes, when I power on with the open and closed Apple buttons held, the diagnostic never completes. When it does complete, I get differing results. So far I've gotten these results:
RAM 1 0 1 0 1 0 0 0
RAM 3 1 3 0 2 0 3 0
RAM ZP 0 0 0 0 0 0 1 0
The last one I seem to get more frequently.
Any ideas about how I can figure out what's really wrong and fix it? Here's what I have:
* My original enhanced //e (upgraded from a ][+)
* A spare //e I picked up for parts (doesn't work)
* Extended 80 col card
* RAMWORKS 512K card
* Two Disk II drives and controller card
* Super Serial Card
* Monitor ///
Both computers have socketed RAM, not soldered-in RAM.
Thanks for any help and/or pointers you can provide.
Cheers,
Tom