Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by RevEng

  1. Been looking at this from the 7800 side. I reached the earlier conclusion here about alphanumeric not supporting proper URL encoding. I think it's questionable that all QR readers would turn these into proper links (since URLs are case-sensitive, i anticipate many not bothering) v3 29x29 doesn't seem out of question. With the aspect ratio of the 2600 and 7800, you'd need 6.89 lines vertical for perfectly square pixels based around 2600 PF pixels or 7800 characters. If you drop that to 6, you get a 32x32 display, with 15% distortion. IMO that's good enough. People use monospace fonts to embed QR codes in reddit posts, and those are nowhere near square.
  2. When sprites aren't perfectly aligned in a zone, the zone graphics are incorrectly aligned. Some lines appear as if they're missing, other lines appear to be duplicated.
  3. Short story, Maria doesn't do processing it might otherwise do for graphics at rom below $9000. See the "Note" at the end of the incgraphic section of the manual.
  4. Can you run the following, and advise? ls /home/x/7800basic ls -la /home/x/7800basic/7800basic*
  5. I'm not familiar with that tool. I use my stand-alone program 7800header from the 7800AsmDevKit which can add/strip headers.
  6. It depends. If you're using a front-end or CLI, you can skip the CRCs. Something like "mame64 a7800 -cart /path/to/my.a78" works.
  7. 7800basic uses some stable-but-undocumented opcodes, to speed up it's sprite routines. This broke some of the emulators without complete 6502 implementations.
  8. Yep. It's a known issue with bankswitched games. If the "incgraphic" happens later in the cart, the plotmapfile command doesn't know what palette you assigned it. The work around for now is to stick the plotmapfile in the last bank, and gosub to it if necessary. Sorry, less than ideal, but it's a bit of a tough issue to sort out.
  9. RevEng

    Get Lost!

    One more thought... you could run the "Cart Integrity Test" in the 7800 Utility Cart rom, to see if your CC2 is giving up the ghost. 7800 Utility Cart (20161210).bin
  10. Despite not using pokey, it looks like BonQ writes to a "pokey" at $4000. This destroys the rom at $4000, if it's actually a ram cart. Does this one work any better? BonQ (Final AtariAge) No Pokey Init Hack.a78 The game still has a bug where it tries to write to $FFFF, but even if it does that it would just mess up the IRQ vector, and there's no source of IRQ.
  11. RevEng

    Get Lost!

    Maybe the freeze is a different situation. It would be good if you setup the canary and brk protection that I described earlier, so we at least know more than the fact that the game froze. Bonus points if you can output the stack values to the screen in that situation.
  12. RevEng

    Get Lost!

    Yep, dying 8 times advances the stack 16 bytes, in the debugger. There's an unmatched jsr/rts, or similar. The dying is the key, and that bat routine is likely just the victim that happened to try and use the stack. That hi byte is hard-wired into the 6502. Setting the stack pointer to $ff is correct start-up, and will place it at $1ff. jsr puts 2 bytes on the stack. For sure, that's the whole idea behind the canary. it's a protector to alert you that your memory is about to be overwritten by unrestrained stack growth. Even if you're not using that memory, the canary will also protect against stack wrap around.
  13. Actually, try again. It's playable, but you need to press a button or press reset (one of those, I forget which) to skip the auto-play.
  14. RevEng

    Get Lost!

    Reproducible in emulation. It appears to require a high number of deaths. The trace file of the crash is attached, John. It doesn't have the whole session in it (it took about a gigabyte's worth of tracing before it crashed) but the file I attached does have a very substantial portion of play leading into the issue. Start at the end of the file, with all of the BRK+RTI opcodes, and backtrack until you see where it went off the rails. getlost-trace.txt.gz (spoiler, it looks like an indirect address write took out a subroutine's return address on the stack)
  15. I think it's just the general lack of availability of entertainment devices, due to increased demand and competition for fab capacity. Keep at it. It's worth pointing out that the de10-nano is a dev kit that's subsidised to encourage development on this FPGA platform, and you're getting a very substantial discount on the hardware you're actually receiving. Some day they may remove that subsidy, or discontinue the nano entirely.
  16. The A8 Memo Pad starts out in upper case, but I didn't implement the A8 caps keys. Technically the xegs keyboard reports capitals as unshifted, and lower-case as shifted. Meh, gotta leave something for the kickstarter stretch goals. Also, congrats on being the first to report the April Folly Easter Egg - xegs keyboard support!
  17. It was gently pointed out to me that this bug may have already been known to some. (though I'm not sure the description is entirely correct). The title of the first post has been amended for accuracy.
  18. [rainbowed for emphasis] This guy gets it! Clearly a Memo Pad power-user, and shame on me for not highlighting the networking and team-based aspects of Memo Pad.
  19. Memo Pad 7800 has 100% bomb diggity. By which I mean the very small amount of bomb diggity it actually contains is 100% pure.
  20. Yes, most definitely we'll hit that 2024 target, maybe. Any expectations are your own, and don't represent legally binding agreements.
  21. Thanks for all of the interest! I'll be launching a Kickstarter for Memo Pad 7800 soon, to get you those desired carts, and to help defer some of the large R&D costs involved in producing this software.
  22. Atari Memo Pad has long been recognised as a landmark application in computing history, and now it's finally been ported to the Atari 7800! Memo Pad is an ephemeral messaging and note-taking app. Like everyone else, you've scribbled, doodled, and left messages for friends, with a pen and pad of paper. At first glance, Memo Pad seems to just be a fancy replacement for these physical tools. But looks can be deceiving. Memo Pad brings the power of the digital age to the mundane paper-based pad. To begin with, Memo Pad requires you to tediously enter your information in, one awkward character at a time. There's no quick and frivolous doodling to be found here. Memo Pad demands that only your most compelling notes are worthy of the huge effort to record them. Even better, there is no save functionality! Memo Pad conveniently ties up your whole system, until you decide that you want to play a game more than you value your displayed information. Will you stop and smell the digital roses, or will you keep that note? The answer to that question will shine a light on how worthy your oh-so-special thoughts are! Finally, your Memo Pad notes have an innovative 960 character limit, enforcing brevity of thought. Long-time Memo Pad power-user (and Twitter CEO) Jack Dorsey heavily borrowed from this feature. Always remember that Memo Pad did it first, and Memo Pad did it best. Discover the transformative power of Memo Pad today, with Atari 7800 - The Choice Of The Experts! ^--This one took a while! How long will it be until I break down and play some Food Fight? Atari7800ProsystemMemoPadTheChoiceOfExperts.bas.a78 Atari7800ProsystemMemoPadTheChoiceOfExperts.bas.bin manual.pdf source.zip
  23. While running a test to probe some other Maria property (for the MiSTer 7800 core work) I happened across what appears to be a Maria silicon bug. It *seems* that if you to write to a Maria color register on the exact cycle it's fetching a byte from the scanline buffer for display, it shifts the displayed byte by one Maria clock. I've put together a demo with the effect. It's easiest to see with a composite display, since the vertical lines in the demo will change artifact color when shifted. MariaBug.bas.a78 MariaBug.bas.bin Kudos to @Kitrinx who had theories and suggestions that were key to nailing this down. This is just another curiosity. It's not particularly useful, and in practise this isn't something you'd need to intentionally avoid either - you probably wouldn't notice it if you did trigger it. The demo makes the bug obvious by using composite artifacting *and* hitting the color register over and over for the entire visible display.
  24. Very cool demo! Inaccuracies are likely due to a scanline length of 113.5 1.79MHz cycles (not 114 cycles like the A8), and the clock slowdown affecting Pokey whenever you access TIA and RIOT.
  • Create New...