Jump to content


+AtariAge Subscriber
  • Content Count

  • Joined

  • Last visited

Community Reputation

169 Excellent

About SenorRossie

  • Rank
    Star Raider

Profile Information

  • Custom Status
    Rediscovering the atari 8bit after 30 orso years
  • Gender
  • Location
    Virgo Supercluster, Local Group, Milky Way, Solar System, Earth, Europe, The Netherlands, Flevoland, Almere

Recent Profile Visitors

5,266 profile views
  1. I guess it's in the eye of the beholder. To me the output of the early 2600 systems is a lot better than that of the Jr(s). I do agree that the video output of the 7800 is the worst of all the Atari hardware I own. The video circuit of the 7800 is available to both the 7800 (Maria) and the 2600 (Tia) parts of the system, which seems to be part of the issue. Over in the 7800 section of the forums someone is trying to improve the output of a PAL 7800:
  2. I don't own an 8bitdo adapter, yet, but the mod is supposedly a single wire mod. More info is found here: If the single wire mod is beyond your soldering capabilities, you can also purchase the seagull 7800 adapter, which allows you to plug in your Sega Genesis 8bitdo adapter and connect it to an Atari 2600, 7800, 8-bit or ST! Also available in the 'local' store: https://atariage.com/store/index.php?l=product_detail&p=1079
  3. A random pile of Atari joysticks and a set of paddles...
  4. A (working) collection of 'The Arcade' controllers.
  5. It probably has to to with an unsupported (windows proprietary) codepage. See this link: https://unix.stackexchange.com/questions/251969/how-can-i-correctly-decompress-a-zip-archive-of-files-with-hebrew-names
  6. Use a different tool to unzip the file. The command line unzip program has problems with unicoded filenames, is my personal experience with debian (raspbian) and Ubuntu.
  7. Thanks for this! I've chosen a different path, where I wrote a shell script (Linux) to generate similar disk images straight from the fandal archive (or others if required). The script can be found on github: https://github.com/senorrossie/sh-a8-16mbgamedisk I must say that I have since been spoiled by the SIDE2 loader, where I just copy all executable files to a CF card and browse through them using the loader.
  8. I recall this was discussed in a thread about sic carts, this is probably where the cart image came from.
  9. No problem, I can always flash stock OS/BASIC to a slot, it would be a 'nice to have' though The OS came from AltirraOS-3.20.zip (md5:1b3ddad8229231cfbd5e9ca937f4fdc0). The altirraos-816.rom (md5: ed8d05ad2435cb18a0df4bbc82085259) has a CRC value of C7C1 in ant 1.4. I will flash a different version of the AltirraOS 816 and check if that fixes the issue. Thanks!
  10. No, I am not. Well, I should have checked before flashing, the diamgos3.rom file is 64k and should of course be flashed to a cartridge, apologies for that. Anyway, the anttest3 works fine on almost everything I threw at it. No more glitches, fonts remain readable throughout the program, which is great news! As the Antonia uses an 65C816, why not flash Altirra OS for the 816... Flashing works (also using your own 65C816 XL/XE OS v2.41), but when the Altirra 816 OS (md5: ed8d05ad2435cb18a0df4bbc82085259) is used to start the binary (which I load from the SIDE Loader by FJC), the screen corrupts and I am unable to continue can successfully select a different OS by pressing the correct keys in the correct sequence Loading binary Directly after the application loads (Altirra 816 OS): A bit later I end up with a solid black screen. Until I press keys.
  11. No, I am not. I copied a few ROM files so I could test the new release. As the diamgos3.rom fails to boot, I figured I should try other ROMs as well. I reported the 'issue' for completeness. Not near a system at the moment, but will test the new version later today. I was wondering if it would be possible to add a 'clear' OS and BASIC slot function (as in flash the content from the protected area of the Antonia)? When I flash the same roms via ant, I see the CRC value listed and not the text as when the slot is not updated.
  12. It seems I am getting different results. The anttest2 executable loads from omnimnbe.rom and scans the current roms, during this I notice a short screen glitch, where it seems the font is switched to a memory location not containing a font it does switch back to a memory location that contains a font and continues to the next screen, where I can select the memory configuration and slots. No issues during flashing diamgos3.rom and after a successful flash, the machine reboots to the current os (omnimnbe.rom). I reboot the machine (press the button next to the cf slot on the SIDE2, followed by Reset). And load anttest2 again. Same short screen glitch as during the previous run. The next screen displays fine, but when I select the slot with diamgos3, and press ENTER, the system hangs: As diamgos3 fails to boot completely, I boot the machine with the jumper removed and restored the os to omnimnbe. All other OS's I had installed worked fine, I was unable to crash the anttest2 program again. P.S. The font glitch after starting the application happens with other OS's as well. A small nuisance, if you ask me.
  13. I tried to flash the os I had issues with before. - boot the machine with 'superhtt.rom' CRC 5A47, SIDE2 cart with the xex loader by FJC. (The OMNIMBE.ROM is in the same directory as the anttest binary). - Load the anttest binary and press F, L, X. Select the rom and press RETURN. The load is successful followed by a press of the any key. After which CRCs are recalculated and the slot shows D:OMNIMBE.ROM - Pressing F to flash the slots results in the following screen (sits there until I power cycle the machine, the slots are not updated I forgot that I need to press Y to flash the slots, so tried again: ), pressing Y successfully flashes the slots and reboots the system. A similar screen is shown when flashing a rom while running OMNIMBE.ROM: The anttest version succesfully loads from the omnimbe.rom OS, something previous versions don't do (I tried 1.2 to 1.4): 1.2: Loads and sits at 'Scanning ROMs' 1.3: Crashes (black screen) after showing 'Scanning ROMs' (no progress shown before it 'blacks out') 1.4: Does not seem to load at all. Sorry I can't be of more help. Hope that helps tackling the issue.
  • Create New...