Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


mr-atari last won the day on May 27 2017

mr-atari had the most liked content!

Community Reputation

697 Excellent

About mr-atari

  • Rank
  • Birthday 05/28/1965

Profile Information

  • Gender
  • Location

Recent Profile Visitors

13,019 profile views
  1. Thank you so much, this was easier then I thought. It will help me a lot debugging special hardware. Nice. 🙂
  2. How do I write a custom device? Is there a template I can download/use? I know my way around in 6502, that's about it.... OK, I cut/paste your example of 8k cartridge and changed to this: It does something, any good like this ??? Thanks! --------------------------------------------- option "name": "256b D500-RAM"; Segment ram: { size: 256, source: "d5ram.bin" }; MemoryLayer wina: { name: "D500-RAM", address: $D500, size: $100, segment: { source: ram, offset: 0, mode: "rw" }, cart_mode: "left" };
  3. I have perhaps a very stupid question, but I can not find it or figure it out.... How do I change the memory map? I would like to change D500-D5FF from mode --R to ARW So it can be used as normal RAM Grtz, Sijmen.
  4. Any progress in fixing the 16mb limit? One request, that is pestering me always, is it possible to include a tic-box in the device-list? This to disable or enable devices. That would awesome, when testing software on many different systems... Thanks!
  5. You could order a reset-button from steve. Not sure if it's on sale, or if he has it on stock. But you need to open the cartridge, drill a hole and solder a little PCB onto it. It goes into the JTAG-header, it's a simple soldering job. I tried a few prototypes and they work nicely.
  6. If that would be possible (or at least one specific Hx:), yes please. I did not check for errors (on write), assuming when files are opened correctly, this should not happen. So that went passed me. It had me puzzled for some time, since I was working on video-compression and I could shrink 500+ Mb into 16, lol... Many thanks in advance 🙂
  7. I have an issue with device H: Most likely nobody noticed because of the file-size in "normal" use. But when I output (or throughput) a file, it's output-size is limited to 16Mb. All bytes beyond 16Mb are lost in space... Can you have a look? Thanks!
  8. Move the chip to the far right. Pin 1 to the left, that is correct. That is how I use my programmer. Mine has this symbol: +--+--+------------+ > > > | +--+--+------------+
  9. Better late then never 🙂 Enjoy !
  10. I have one too, from an Atari maintenance guy. He told me it was used in testing 400/800 ports.
  11. For who want to try, LiteDOS 3.b is up. 🙂 http://www.mr-atari.com/Mr.Atari/LiteDOS/
  12. Clowns and Balloons can be compressed nicely, loading time goes from 18 to 14 seconds. 🙂
  13. LiteDOS 3 will be available next year. Still coding on certain routines..... Exporting LiteDUP to a separate file. If you want to try/test, a work-in-progress is available on request if you pm or e mail me.
  14. For the R: handler, just drop a line if you need help. I have send you a couple of version to try. But until now, no feedback. Relocation is a bit of a pita, you have to use MEMLO and update the loaded driver accordingly. Then move it to the position of MEMLO, avoiding overwriting your own code or someone else, then adjust MEMLO to the new values. If BASIC or other software has already booted, they need to be cold initialized to except the new boundaries. I have an ESP8266 R: version that is relocatable, but the buffer is 256 bytes (fixed) and you did not want that. Grtz.
  15. Like I said, "Fake error-message" Any RTS back to LiteDUP with Y negative, will result in Error-(value_Y) message. Cosmetic bug.
  • Create New...