Jump to content

kenjennings

Members
  • Posts

    890
  • Joined

  • Last visited

About kenjennings

  • Birthday 07/01/1966

Contact / Social Media

Profile Information

  • Custom Status
    Me + sio2pc-usb + 70 old floppies
  • Gender
    Male
  • Location
    Florida, USA
  • Interests
    C programming, computer graphics, unix/linux, retro gaming, Atari 8-bits and Amiga
  • Currently Playing
    atasm -- Mac/65 with all the joy and none of the line numbers.
  • Playing Next
    atasm (Mac/65) Is there any better "game"?

Recent Profile Visitors

13,427 profile views

kenjennings's Achievements

Dragonstomper

Dragonstomper (6/9)

471

Reputation

  1. No, my wife's job in Orlando ended this month, so I have been busy moving her and her temporary apartment stuff back home here in South Florida. if you look at GitHub history I have been working on adding more game modes (and some of it is actually working too.) I expect to pick things up again after July 4th.
  2. That's really nice for 10 lines of BASIC. mads says mine is at 24K lines of source. I should probably quit working on this. ?
  3. I've been out a while. (a couple months, actually). Everyone at home was taking turns with the virus of unspecified origins. And then I had to get shot for work and that was worse than having the virus. Starting to ramp up to working on 1nvader again.
  4. Are DLIs actually turned off during I/O or is it just the deferred VBI that is not called? DeRe Atari says the DLI is not maskable. The NMI Handler The OS has an NMI handler for handling the nonmaskable interrupts. Unlike the IRQs, the NMIs cannot be "masked" (disabled) at the 6502 level. All the NMIs except SYSTEM RESET can be disabled by ANTIC. Mapping the Atari says the value CRITIC is set during I/O which stops the system calling the deferred VBI, so OS shadow registers do not get copies to the hardware. (The immediate VBI is still called.) It doesn't say anything about the DLI.
  5. Back to work on this. The MADS maintainers discovered my stupid programming trick that was breaking MADS and have made some updates to mads. (Version 2.1.4 at https://github.com/tebe6502/Mad-Assembler )
  6. It works! Happy to provide my stupid programming tricks to improve mads! ?
  7. Ooo. Yeah. Those commas shouldn't be there. That's not right. (shouldn't it be a syntax error?) Yup. That's what did it. Assembly completes now. THANKS!!!
  8. Nope. 2.1.3: Runtime error 216 at $0000000000417845 $0000000000417845 2.1.4 just downloaded and rebuilt. Runtime error 216 at $0000000000417965 $0000000000417965 I made a bunch of new declarations in https://github.com/kenjennings/Atari-1nvader/blob/master/ata_1nv_gfx.asm A lot of it was similarly named labels for a list of options/menus and I'm wondering if its the similarity or the lengths of similar names that is breaking this. I'll try later commenting out the newer stuff and then try a reassemble, then put back the declarations in stages and see where this finally breaks.
  9. So far I've worked out that the ata_1nv_gfx.asm file is breaking mads. This is where all the screen graphics assets are declared/defined. Something in there is the problem.
  10. I just downloaded from the github site. file size 14,601 bytes. It ran OK here in NTSC and PAL on atari800 4.2.0 (linux) and Altirra 3.90 (PC). My config is running with no cartridge inserted, (and so, no BASIC. ) Though the program was small enough, that didn't really seem to matter. Maybe the size has grown to the point where this is now a requirement. Is anyone else having issues on real hardware or Altirra? Please report config.
  11. Ran head-first into a brick wall. It looks like Mads may be broken due to something in the 1nvader source added in the last couple weeks. i'm getting an error from MADS when trying to assemble the 1nvader game. Compiler 'MADS' output: Runtime error 216 at $0000000000417845 $0000000000417845 This happens from command line or from eclipse/WUDSN. i thought maybe the mads which I had downloaded long ago was out of sync with current linux libraries, so did some updates, got the current source, built a new executable without issues (remarkably), and still get the same error. (At least I have a nice shiny 2.1.3 now). Then I tried the last large game I wrote (Pet Frogger V03) and it assembled just fine from eclipse/WUDSN So, it seems that there's something about the 1nvader source code that's breaking mads. ANY IDEAS? What I get out of google is that this is a memory access error. Most recently, I had been adding some strings for options menus, and commenting out declarations of unused variable. Is there any limit in Mads that I may be hitting -- like file size limit or total number of source lines?
  12. Having some problems with MADS on Linux. i'm getting an error from MADS when trying to assemble the 1nvader game. Compiler 'MADS' output: Runtime error 216 at $0000000000417845 $0000000000417845 This happens from command line or from eclipse/WUDSN. i thought maybe the mads which I had downloaded long ago was out of sync with current linux libraries, so did some updates, got the current source, built a new executable without issues (remarkably), and still get the same error. (At least I have a nice shiny 2.1.3 now). Then I tried the last large game I wrote (Pet Frogger V03) and it assembled just fine from eclipse/WUDSN So, it seems that there's something about the 1nvader source code that's breaking mads. ANY IDEAS? What I get out of google is that this is a memory access error. Most recently, I had been adding some strings for options menus, and commenting out declarations of unused variable. Is there any limit in Mads that I may be hitting -- like file size limit or total number of source lines?
  13. Four Players. Four Missiles. That's basically Spacewar .
  14. According to Mapping the Atari if you're not using the Cassette, FP package, or BASIC, looks like memory is free from $3FD through $6FF.
  15. There are directions on the github page for building/installing to run directly on linux.
×
×
  • Create New...