Farb

I assume so as well. I filed an issue with them for Atari 800 compatibility including correct memory size and behavior.

I don't have access to an actual 800 at the moment so have been using an EclaireXL in OS-B mode and a PAL 800XE with a custom OS-B mode for testing. I swear when I was tweaking drive timings I had those titles running in the Eclaire's OS-B mode but it's possible it had reverted to XL mode and I didn't notice. At any rate, the disk protection checks are passing in XL mode so the SDrive seems to be behaving properly

Universe isn't copy-protected so you are having some sort of other issue there. I got it to boot just fine but didn't do too much with the game. Keep in mind that ATX write support is not implemented right now so that may be a potential issue. Temple of Apshai requires BASIC so make sure you don't hold down OPTION while booting. I also got that one to load just fine. Blue Max requires OS-B so it won't run on an 800XL. Also tested and working here with OS-B firmware.

Interesting, I went back and re-tested based on this. I have been testing everything with OS-B and was running into the "remove custom o.s." errors on the EA titles I mentioned. I switched over to the XL O.S. and Archon, Archon II and M.U.L.E. all seem to work just fine. Strange. EDIT: I got hopeful on the troublesome Databyte titles like Boulder Dash II and Spy vs. Spy II. No luck there.

I'm not necessarily looking to create a generic 810 profile, but I would like to confirm how close we can get the SDrive timings to coincide with a real 810 even if it is not representative of ALL 810s. Then it would hopefully be a matter of tweaking various timing attributes to support different flavors of drive (e.g. 810-A, 810-B, 1050, etc.) Right now I can't even be sure why things are failing when they do because the timing of certain elements may be way off. I hadn't looked at this in a while and didn't realize it had drive information in there - thanks for suggesting it. I see Avery has specs for an idealized 810 drive so I've gone with those values for now. I just checked in some additional timing changes to Github. I've confirmed that A.E. (which we believe will only run on an 810), Agent U.S.A, Boulder Dash and Bruce Lee all seem to work. Sadly, none of the Archons or M.U.L.E. work now so something is still off

Take a look at the page for the Age of Adventure Side A dump on the website: http://a8preservation.com/#/software/dump/80 The CRC of the file you provided does not match that page. So this is either an older dump we did and have since corrected or not ours. Our dump was generated using Kryoflux and a8rawconv 0.92.

Appreciate it. The new code is already checked-in to the v08 on Github so you are welcome to give it a try. The timing code has an impact to disks that use duplicate sectors for protection, so I was using a few titles such as Boulder Dash, Bruce Lee and Agent U.S.A. for testing. At this point I need access to a real 810 drive in order to measure timing behavior and refine the SDrive code further. I'm currently going by measurements I've seen posted to the forum or flat out guesses :-P I'm trying to see if someone can bring an unmodified 810 to the Fujiama next weekend here in Germany...

FYI, I am in the process of refactoring the timing code so things that are working now may or may not work with the new code. I just wanted to make sure people are aware so no one wastes time compatibility testing right now :-)

Which protected ATX files work with SDrive is very much on topic here. I wanted to avoid going down the rabbit hole of the merits of copy-protected vs. hacked images since it's not particularly relevant to this thread. Depends how you define "many". Probably 50 or so acquired over 7-8 years.

I don't want to take this topic too far off track since it is, after all, specifically about running copy-protected disk images on the SDrive Max. But, yes, I only had original software so the "retro thing" to me is non-cracked.

Yep, I'm aware of the Mega since I used it in my original SIO2Arduino project. I asked the project maintainer that exact question a few months ago. It seems like the current SDrive codebase has dependencies on the Atmega 328 chip used in the Uno so updating it for the Mega is not an easy task. It's important to keep in mind that this project originates from the legacy SDrive codebase that was written for custom hardware that used the same or a similar microcontroller to the Atmega 328. It does not use any Arduino libraries so is not going to be easily portable between different Arduino hardware.

I can't say for sure since I haven't been involved with the touchscreen code at all... only the ATX support. What I can say for sure is that we're dealing with an extremely resource limited device (Arduino) that we're already pushing to its limit with the current capabilities that are in place. So I wouldn't be too hopeful. Sadly, the thing that makes this device so inexpensive is also the thing that will limit how fancy it can become. Correct, I do not use a diode and the device works fine.

I'm certainly open to it if we can identify what I'm calling the "static drive values" in that spreadsheet for each of the different drive types. Oh, and I fully realize there may be more static drive values needed... the ones in the spreadsheet are the only ones I'm aware of at the moment. UPDATE: Here are some titles that are known to only work on the 810 from our database: http://a8preservation.com/#/software/dump/16 http://a8preservation.com/#/software/dump/1700 http://a8preservation.com/#/software/dump/2453 Speaking of next steps, I think the best way to confirm that the spreadsheet calculations are valid is to test with a real drive. Does anyone know of Atari software that lets you read a specific track/sector and gives you the timing from the time the request was sent to the time data was received? Ideally, it would allow this to be done for a series of track/sectors consecutively.

The pull request was just created yesterday. It will take time for the repository maintainer (Klaus) to review it :-)

For the benefit of the rest, the command would be: git checkout v08You should be able to build it with a simple "make" command. This will create (currently) three folders for each of the different supported touchscreen hardware types: atmega328-hx8347g, atmega328-ili9329, atmega328-ili9341. Inside each directory you will find an SDrive.hex file. Then, you need to use avrdude to load the SDrive.hex file onto your Arduino just like you did with the released firmware you downloaded prior. The command will vary based on your setup but here is an example from the SDrive Max homepage: avrdude -carduino -pm328p -P /dev/ttyACM0 -U flash:w:SDrive.hex

The timing code so far was all done by Klaus. I am currently working on trying to make it as accurate as possible. Here is a calculation spreadsheet I'm working on to test the algorithm: https://docs.google.com/spreadsheets/d/1CgvwcGul4irS73DAb6qeYFlxed1oJre9J3-trHsCveA/edit?usp=sharing

Thanks for the contribution, R.Cade!

I believe Electronic Arts titles are more sensitive to timing. I have confirmed that Archon, Archon II and Axis Assassin are all working with 0.8b of the firmware which has very rudimentary timing implemented. However, no Databyte titles (which are extremely timing sensitive) I tried are booting so there's still work to do

Wow, thank you, Todd. PM sent!

Currently, the ili9329, ili9341 and hx8347g are the only screen/chips on the supported list.

I'm glad to see people having success with these (between here and the other thread)! And I love the XL-style case. I am going to need to figure out how to get one of those printed here in Germany :-)

I am currently working on a compatibility list for the latest beta version (0.8b) which I manually build from Github. As for 0.7, a few that are known to work (although there are many others) are: Agent USA Bandits Bruce Lee Canyon Climber Goonies (used to test weak bits) Nibbler

See you all there! I will be there with my Kryoflux and Super Card Pro so please bring any original disks that you would be willing to let us dump for the preservation project :-) Sent from my ONEPLUS A6003 using Tapatalk

We have come across three different variants of the original release of Solo Flight (note that this is different from Solo Flight 2nd Edition which is visually quite different). Here is what we have so far: 1. Solo Flight (1983)(MicroProse Software - U.S. Gold)(GB-US)[!].atx We have identical dumps of this with both an early MicroProse 1983 label (with their Caribou Court address) as well as a 1984 white U.S. Gold label. Copy protection includes missing sectors and a phantom sector. 2. Solo Flight (1983)(MicroProse Software)(US)[a].atx Unfortunately, this dump was submitted without a photo of the label but the description submitted indicates it is a 1983 U.S. MicroProse release. Identical copy protection to #1 but significantly different data. Both #1 and #2 seem to work on XL/XE so that doesn't seem to account for the difference. 3. Solo Flight (1984)(MicroProse Software - U.S. Gold)(GB-US)[!].atx We have identical dumps of this with both a newer MicroProse label in 1984 U.S. Gold packaging as well as a 1985 MicroProse flippy-style C64/Atari release. This release appears to use skew alignment protection much like F-15 Strike Eagle so is different from #1 & #2 minimally in that regard. If anyone can provide any insight or opinions into what is different about these beyond what I've stated (and especially whether #1 or #2 is the earlier release), it would be greatly appreciated! Thanks in advance! Solo Flight.zip

I don't generally like recommending clone boards, but these are available all over AliExpress and have the nice benefit of including solder pads for each pin that makes it extremely easy to attach the SIO cable. On a genuine UNO, since the touchscreen covers all the normal pin sockets, you'd have to do some ugly soldering to get the SIO cable connected. The clone board also has the benefit of costing 3 or 4 dollars.