Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!pt.cs.cmu.edu!andrew.cmu.edu!cs4w+ From: cs4w+@andrew.cmu.edu (Charles William Swiger) Newsgroups: comp.sys.apple2 Subject: Re: Backing up old stuff Message-ID: Date: 9 May 90 18:05:10 GMT References: <12782@wpi.wpi.edu> Organization: Carnegie Mellon, Pittsburgh, PA Lines: 42 In-Reply-To: <12782@wpi.wpi.edu> Yes, Copy //+ and Locksmith 6.0 were both able to copy Alien Rain (I've tried) and I would assume Asteroid Field as well. Locksmith can also do a disk repair, but only on more-or-less normal formatting schemes. I don't think Alien Rain qualifies. . . . If I remember right though, it only uses the first $10 or so tracks. Try running the sector editor on Copy //+ and determining which sectors fail the checksum (give a read error.) Try re-reading these sectors a few times, praying vigorously that you'll get a good read :-) If not, disable the checksum check and read the sectors a couple of times, making printouts of the disassemblies. If you know 6502 machine language, try to work with the disassmblies so that you get workable code. If not, fill the damaged area (the one where the disassmbly either changes from read to read, or shows illegal instructions: ???) with NOP instructions ($EA). Praying hard here might help, too. If you are lucky, and only a small number of bytes are unreadable, then perhaps you'll get the program working again, more or less correctly. I've done this before twice (Archon II, by EOA and Ultima IV, by Origin Systems), and got both programs to work, although one had its display scrambled a bit (Ultima IV). Of course, there was only one sector damaged in each case, so I had it easy. If any large area of data is scrambled, then I'd suggest getting a copy from someone else. As to putting the games onto 3.5" disks, its easy if they use ProDOS, harder if they use DOS 3.3 (or a modification thereof), and quite difficult if they use a customized DOS. ProDOS games can be copied fairly freely, once you remove any disk-specific copy-protection, such as syncronized track checking, nibble counting routines, et cetera, ad naseaum majoris. If you can get versions that have been hacked into BRUNable DOS 3.3 files, then they can usually be copied freely onto 3.5" disks. If the program requires multiple files, then you might have to modify the filenames a bit (both in the disk directory and in the program code itself). You may notice that I don't appreciate copy protection much. You can flame me if you like for this, but only if you leave me an Email address that I can _bombard_ with flames back at you. Gotta go, I've got an exam tomorrow. Wish me luck. -- Charles William Swiger cs4w+@andrew.cmu.edu