Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

565 Excellent


About Farb

  • Rank

Profile Information

  • Gender
  • Location
    Frankfurt, Germany

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I've tried to document the different known variants here: http://www.a8preservation.com/#/software/title/17 See the descriptions of each release for more info.
  2. Hi all, it long overdue for a new preservation torrent. If anyone is interested in creating and seeding one for us, please PM me. Thanks!
  3. Thanks for the ATX files. Caverns of Mars isn't protected but also doesn't match any dump we have - the sector interleave is different. I am uncertain if this is a legitimate variant or a side effect of the way it was dumped. Choplifter also doesn't match any verified dump we have. The closest match is to our [a] dump but it has data differences in the first two sectors and the interleave of the protection track is different. I'm also not sure here what the cause of the difference might be.
  4. @toddtmw beat me to it. I'd give both sides of Top Gunner Collection a shot since it's already preserved, would test missing sectors, duplicate sectors and whether skew alignment is replicated correctly.
  5. You can certainly try that. Ultima disks are a very trivial example I would expect to work fine since they only leverage simple missing sectors. Just be aware that these old disks will vary in what kind of shape they are in and how many reads they will be able to tolerate before they begin suffering permanent data loss. So it is possible that a test boot or a test dump is the only completely good read you get. I've heard folks in the past disagree with that statement, but I've personally dumped and processed well over 1000 disks and have seen this phenomenon first hand. Update: If you try to dump them yourself, be sure to check the drive head in between each dump to check if debris has accumulated. If so, clean the head before the next dump. The build-up of head debris can easily prevent a good dump and possibly destroy the disk.
  6. @djmat56, it's great to hear from you! I hope you are doing well. Yes, many of the tape images in our archive are yours. Fortunately, we've been able to verify many of them over the past few years with contributions from others 🙂 Thank you for putting the list together. And thanks @toddtmw for cross-referencing the list with the preservation database 👍 As @toddtmw indicated, we often have a better chance of preserving disks if we can do a flux dump with Kryoflux or SuperCard Pro. If you would be willing to send them to me in Germany, I can dump them and return them to you. However, I understand if you don't want to incur risk or cost to send disks, so we'll take dumps made on an Atari drive as a last resort. I honestly don't know the quality of an ATX that Respeqt generates as I don't even own an Atari drive anymore 😛 There will be titles that simply can't be dumped accurately using such a method (not sure if any of yours fall in that category though).
  7. Thanks for pointing out the problems you found. A number had already been corrected in the database and I've fixed the others that I am able to. As @ijor said, some of them are ATX files that were made a long time ago. $74 is the creator for my a8diskutils.
  8. I recall Archon having this behavior as well. I didn't think the floating bus had anything to do with the EA protection but I could be wrong. I know one title whose protection was affected by the A800's floating bus was Coleco's WarGames. I had contacted phaeron about it because the verified ATX worked on a real Atari but not Altirra. As I recall, the floating bus emulation was pretty CPU intensive so was off by default.
  9. I'll assume you meant CRC "5ca7b209" as the preservation ATX. The difference between it and Atarimania's is the starting sector for each track and variations in sector positioning as we would expect from ATX files made from different dumps. The sector data, sector interleave and protection sectors are identical between the two (our criteria for considering two dumps identical). With D : acceleration turned on, the protection check appears to fail on both but it manifests itself in different ways as you have noticed. On our dump, the Altirra A8 machine crashes. On the Atarimania dump, the monsters stop moving and garbage appears at the bottom of the screen. I don't know what behavior a protection failure would manifest on a real Atari. I suspect the differences in sector position could be causing different behavior in Altirra but I have no way of knowing this for sure. Overall, it is not recommended to use D : acceleration when using protected ATX files since many protection checks rely on accurate drive timing. You will find many other examples such as this. I always leave it off and use F1 to accelerate loading if I need to which won't cause protection failures.
  10. Yes, I was using -r and pointing at track00.1.raw. Here is one you can test with: https://drive.google.com/file/d/1Y6e5_Ka_l_x_5G-ickOhHLy__nvlBMAK/view?usp=sharing I tried the -g option but I'm still not sure how I create an ATX/ATR of side 2?
  11. FYI, it seems like the -r option is not working properly anymore in 0.94. It's showing Kryo B sides as blank.
  12. Thank you for continued work on this, @phaeron! It is so nice to see proper enhanced density ATX support!
  13. Good advice here. It's also worth mentioning that if you begin to hear harsh scraping or squealing noise develop during the course of a dump, it likely means the head has become dirty. I generally abort the dump in such situations, clean the head and re-try. If you let it continue, you run the risk of the gunk on the head damaging the disk surface as it continues to read. I've had mixed results cleaning the disk surface with isopropyl alcohol. The most important part is to be gentle -- I've seen the disk material come off with too aggressive a cleaning.
  14. The current tools rely heavily on some Spring libraries so it might be tough. I've been learning the Go language and have started re-writing the tool using that since it compiles to a native executable. If you're interested in collaborating on it, let me know 😁
  • Create New...