DKONGsr

Hi there, I am fairly new user here, but did use my Atari 800XL quite intensely back in the 80s. I have a question relating to atarixfer on x86 PC with an FTDI dongle - hope this is the correct topic - if not I am sorry. So I have actually started playing around with it and so far was pretty succesfull, everything seems to be working and I had some fun time programming Basic, like it's 1984! Also the atarisio set of tools let me recover most of my old disks using atarixfer (I only had a 1050 stock drive) and was able to use those on a self programmed SIO device using an atmega pro micro. So all i s good to perfect - thanks a lot for the great programs. So I can confirm that they work as advertised, without kernel driver and cheap dongle. atarixfer with dtr, atariserver without any handshaking. Now I wanted to make my SIO device a little bit more user friendly (I know there are tons of nice options out there, but for me the fun part is basically understanding how it works and not really using it in the end....) so I thought it should be possible to use atarixfer to get data to my SIO emulator, just to make debugging easier an not having to hook up the Atari for that - this however does not work at all, so maybe someone can give me a pointer what goes wrong I have a few Ideas after going through quite some research of the SIO protocoll. Some very old manual I found (Atari Home Computer System Serial Input/Output Interface User's Handbook) had the timings but claimed (in a flowchart) that an 'N' is sent when the device is wrong (I suspect that would cause trouble if every hooked up device tries to do that prertty much at the same time the correct device tries to send 'A'...) - so I was not too sure how reliable the information is. Then the Altirra manual has a nice section with pretty much the same timing information abou the rest. So going from here I think the timing should be like: (A: Atari, D:Device) A: pulls down command, sends 5 bytes and raises CMD within 650-950µs (the OS however is qicker but cmd should go HIGH again) , then some time (1-16ms) ist left for from D: to reply As far as I can tell that is already where the communication goes wrong. If I am not mistaken, atarixfer does not raise the command again - I can log several tries with a command 4E and then several for a status byte - however I loose all timing information, since my only point of reference is the starting point of pulling cmd low - the serial port from the atmega has a buffer, the rest could have arrived any time after that. I did not do a very thorough investigation, but an LED at the cmd line turns off, then the data comes and after the atarixfer times out with two failure messages (percom and status) the LED lights up again. So I suspect that maybe using the DTR from the FTDI as command does not even allow correct use as command? I am just a little bit stumped why the original Disk Drive works like that?? (now unfortunately I have one more source of uncertainty, I transferred my disks from a different computer and now had to compile atrixfer again using the latest release - but have no acces to a 1050 any more... but I have tried atariserver from the same package with the real Atari and that still worked fine) Anyways nothing depends on this I am just curious, so if someone has an idea, woud love to hear it. One little thing I noticed: Maybe add the hint in the README that ATasm needs to be installed, I tried apt-get install build-essential libncurses5-dev zlib1g-dev But failed first - all I had to (Debian) do was also to apt-get install ATasm Thanks again to HIAS for the great work.

Hey Guys, pretty new member here - but long time Atari user. I have just started trying out the emulator and it seems pretty impressive - I have fiddled with atari800 but want to attach a real 1050 and also make a real paddle (or at least a rotary potentiometer) work - from what I read this should work much better with atari++, but I will still have to try that. Anyways so far: Great work, thanks for all the effort and sharing! Compiling on my Laptop (Debian 9) worked "out of the box" - so "./configure && make" did the job! However the PI challenged me slightly, so I thought I share for others. The compile process also worked with a few warnings. However I could not start the executable. After long time trying different releases and a lot of googling, I found this post and that finally got me in the right direction! Just wanted to confirm that for running atari++ on the Raspberry Pi (I tried on a 3) I have to provide ./atari++ -FrontEnd SDL -Sound SDL Maybe that would be helpful to include in the Manual section of the atari++ homepage? (The same with the download for 1.83 from official page and also tried with the file provided in last post) But now to my question - since I do not have a mouse on my raspberry, I encountered the next obstacle (- nothing too bad and I think I can work without the gui and only use commandline options): Once I start the menu, I can navigate with the cursor keys and one time I seem to be able to use RETURN as mouseclick. However after being in a sub menu only moving the mouse cursor works with keyboard but I cannot not confirm any selection anymore - so basically leaving me stuck and helpless ;-). Is there a trick to do that or is this maybe a bug? Thanks again, stay safe!

Thank you so much - now it worked like a charm. Very impressed by the project. Keep up the great work

Hi again, tried with more roms - 64kiB worth and also a whole bunch ~700 something kiB but same effect, blue screen in endless loop. I checked my firmware is 1.1.0 wifi 1.7.4.0 I even renamed all roms to have only 8.3 chars. Any other suggestions?

Ah cool - thnx for the quick reply, will give that a try!

Hi everyone, Brand new user here - just received my pluscart and what can I say that hasn't been said before: awesome project! Biggest respect for all contributing folks! Works perfectly, could play a lot of well remembered games and even more forgotten ones. Just one problem on my side maybe someone can point me in the right direction: I have signed up for the plus store, have my Nextcloud space setup - the card is connected, I have the mirrored files on my PC, I can play all online Games, I can also see games I put in the "My Roms" folder and play them - so I think the connection is all correct. When I have no roms in the Offline folder no option to download is shown, when I add some (I put 2x2k roms in there to try) the "Download offline ROMs" gets visible! But then when I activate this - sometimes the screen flashed a little sometimes not - everytime I get stuck in a blue screen with that turning symbol in endless loop. I even let it run for 2 hours straight but I guess it shouldn't take that long. I even tried to tar the two files first but no difference (also not sure if tar only or gzip....) Having offline games obviously is not the most important thing, but I would still like a few just in case I end up in place with no wifi but the need to play like it's 1980.... So any hint appreciated, but that doesn't make the cart any less impressive. Thanks, Ralph