Jump to content

ijor

Members
  • Content Count

    2,522
  • Joined

  • Days Won

    2

ijor last won the day on July 31 2011

ijor had the most liked content!

Community Reputation

653 Excellent

About ijor

  • Rank
    River Patroller

Contact / Social Media

Profile Information

  • Interests
    vapi,pasti

Recent Profile Visitors

11,745 profile views
  1. There is still no support for the FDC read track command and data outside the sectors. Note that as I commented already, this is not strictly required for running DiskMaster 1050. It doesn't use it as a copy protection but only for hiding part of the protection when using the program to analyze its own disk. Adding support for gap data at ATX images is not very difficult. But there are significant complications for emulating the read track command accurately, especially at MFM. The extra size required to store all the track data shouldn't be a big problem. Not only that this would be, of course, optional, but also it is possible to store full track data on specific tracks only. It's not top priority for me anyway. There are a few other issues that IMHO, are more important. E.g., we need to add support for weak bits at the header (a weak sector header). This is required for running SuperArchiver.
  2. That image I posted earlier has bad sectors timing. It worked emulating a US Doubler, which is what I tested, but as Phaeron explained it fails if emulating an 815. Attached fixed image. May be a moderator can give me permission to edit post #2? AtariAccountant-Atx-FixedTiming.zip Attached also an image of the Archiver Editor by Spartan for the Happy 810. One of the very few titles that requires full data stored for long sectors. For testing on Altirra enable Happy 810 full disk drive emulation. Again, it requires Altirra version 4.00-test16 or later and and might also require the config option "image.disk.atx.full_sector_support". ArchiverHappy810-Atx.zip
  3. Oops, you are right! I will post a fixed image later. Sorry about that.
  4. Thanks again everybody for the help and contribution.
  5. Attached an ATX image of disk 1 of Atari Accountant. This is a software designed for the Atari 815 disk drive and it is the only known copy protected title in double density. Note that this is a reconstructed image; we don't have a full image of the original disks. Please see this for more information about how the data was recovered: https://atariwiki.org/wiki/Wiki.jsp?page=The Atari Accountant Series Note also that we don't know the exact copy protection that was present on the original disk. We only know that the software attempts to read a specific sector and expects the drive to return an error. I just crafted an image with a track layout that would produce that behavior. The 815 drive, contrary to any other Atari 8-bit drive doesn't invert the disk data. But in this image the data is inverted so that it could be run on other Atari double density drives such as the Us Doubler. The software requires Basic and I've been told it also requires OS-B. I didn't test it thoroughly, only confirmed that the copy protection check passes and the software loads correctly. For running under emulation it requires Altirra version 4.00-test16 or later and with current versions it might also require to enable the config option "image.disk.atx.full_sector_support". This option will probably not be required in future versions. Edit: The image posted at this post has been deleted because it was built with wrong sector timing. An updated image was posted below at post #6 in this thread: https://atariage.com/forums/topic/312312-atx-file-format-additions-and-enhacements/?do=findComment&comment=4652404 Thanks to @jaybird3rd for allowing this edition.
  6. We implemented the following additions and enhancements to the ATX file format. Define additional densities at the file header Implement recording bitrate at the track header Support full content for long sectors Support double density, double sided and other densities Include in the attached zip file is a short document and an updated .H header file. I wanted to polish a bit more the document and build some few more samples but currently I'm short of time. I decided it's better not to wait and post an update if necessary. Thanks to Phaeron and other people for their invaluable contribution. AtxSpecsNews-Set-2020.zip
  7. The field is 16 bits so as you could imagine most values are still free. You might want to choose two letters that resemble the RespeQt name somehow?
  8. For the greaseweazle, you may want to check this thread: For the disk drive, if you are planning to write back images, it is better to use an older 48 tpi drive (40 tracks) and not a 96 tpi one (80 tracks).
  9. I doubt it. But even then, it still wouldn't make much sense because he claims that he had to modify DOS for that reason ... listen to the interview, it's worth
  10. Did you hear to the Atari podcast interview with Charles Marslett who wrote the Percom firmware? If I understand correctly, according to him Percom did have a prototype and a copy of the DD DOS. Actually he mentions that the whole idea of Percom developing a DD drive was precisely because Atari killed their own DD project. Mr Marslett also mentions an issue with the boot sectors being single density that doesn't make much sense to me, but otherwise he seem to remember things quite well.
  11. Beg to differ but, personally I would like this to be configurable. I do realize the convenience of sharing ATR images with the other Atari drives. But, IMHO, this makes the emulation less accurate. A disk that works on the USD should not work in the 815 and vice versa. Conceivable, somebody could make a program to convert 815 disks by inverting the data, and this would fail under emulation. I agree that these are extreme cases and you can say I'm playing the devil's advocate. A slightly (just slightly) more realistic case, though, would be when dumping a real 815 disk to ATR. Or writing back an ATR to use on a real 815 drive. It would fail in both cases with this scheme. Again, this is very exotic I can perfectly understand that the whole thing might not be worth to implement a configuration option. I just thought I should mention the issue.
  12. Probably yes. ST drives normally are jumpered as drive B. You probably need, at least, to change the jumpers for drive A.
  13. I'm implementing this shortly. In the meantime, I would like to compile a list of all the ATX image creators. So everybody that implements a tool that creates ATX images, please record your creator signature here. Remember that this is a 16-bit field in the ATX file header. I'll include the list when publishing the new track definitions for the new enhancements. Thanks.
  14. It is not fixed at the hardware. It all depends on the firmware and we have more than one, now. I don't remember the details in each version, and later versions are highly configurable, so they might even allow you to configure the exact behavior.
  15. It is perfectly possible to use a Gotek or a PC drive externally. The main, perhaps only, problem, is how to adapt the custom ST external floppy connector and powering. You can build your own cables. Or as many do, just adapt a 314 case and reuse the 314 cabling and power. You can even just drop the Gotek inside the 314 without doing any modification if you want.
×
×
  • Create New...