Jump to content

Fnord42

Members
  • Content Count

    75
  • Joined

  • Last visited

  • Days Won

    1

Fnord42 last won the day on August 21 2020

Fnord42 had the most liked content!

Community Reputation

55 Excellent

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Okay, having read and thought about this a lot more than I had when I answered the poll, I must admit I changed my mind. I now think very few people here will lose interest in the X16 just because they can have an X8 now, and it will allow Dave to get some money to fund further X16 development while giving the people something to play with and pass the time in return. Regarding compatibility, I don't see why the X8 could not easily be modified to use the X16's Vera addressing scheme, at least optionally. The only thing that I have conflicting feelings about is the speed - it would feel "more right" to me if the X16 was not slower than its little brother. Slowing down the X8 to 8MHz by default might avoid the strange feeling of "not really upgrading" when switching to the X16 later. And it would certainly avoid some porting issues later on. So, my revised opinion is: Gimme the X8 now! (Maybe only 6 or 8 MHz though) Phase 1 X16P Kit next Phase 2 for the non-solderers that still want most of the retro experience and expandability
  2. Speaking of upgradeability - I'm curious: Is there anyone here who does not plan to max out their X16's RAM to 2MB immediately? Leaving the X8 aside for a moment, the availability of an X16 with less than 2MB of RAM could also lead to people developing only for the smallest common platform, couldn't it?
  3. I'd love to be able to buy a professionally-made case for my X16P.
  4. I'd also buy an X8 without thinking twice if it were available(*), but I think the concerns about having two semi-compatible platforms cannibalizing each other's user (and more importantly: developer) base are valid. (*) in addition to the X16 Phase1 Kit, which I still want most.
  5. I think you got the point wrong, or at least incomplete. To appeal to people's (admittedly irrational) love for retro(-like) hardware, the through-hole part is important. Also, it makes the kit version easier to build for beginners. And don't forget the expandability of the X16 which is a very appealing aspect that the X8 lacks. I do agree with your point about the licensing, though. I see the benefits of the current situation, but ultimately I'd love to see the X16 go completely open-source, including the Kernal.
  6. I guess I'll have to retract my earlier criticism about the X16's audio capabilities. This sounds actually quite a lot better than I would have expected. Thank you!
  7. Fnord42

    Modplayer

    Just tried it, and it's awesome! Some effects are still missing, which makes the second half of Lotus2.mod sound really awful but everything else I tried sounded great. Great work!
  8. Nope, not possible. Wouldn't give you much of an advantage anyway, except if you want to copy large amounts of data from one area in banked ram to another. Plus, you'd have to deal with the reset and interrupt vectors which are hardcoded at the end of the 65C02's address space.
  9. I think we are missing the true elephant in the room here. What we should really worry about are people/websites that call short video files "GIF" when they are in fact something else (like MP4 for example). That is just wrong, and they deserve bad things happening to them.
  10. Beautiful! Does the X16 support the middle button/wheel? The scroll wheel is one of the more "modern" UI features that I miss most when working on the Amiga. So although it is a bit of an anachronism on an 8bit system (like VGA and SD cards), I would welcome it. I suspect this is purely a software question, and if the Kernal does not support it, you can always write your own mouse driver. But, assuming there'll be a mouse included with the X16, it would of course make sense to have Kernal support for all its buttons (the wheel usually being up/down buttons from a software perspective).
  11. The X16 design has been very expandable already, so lots of these ideas have been floating around for quite some time now. You probably wouldn't want to use the ATtiny84 for that, though. But I really like the fact that we now have I2C, too. (I'm hoping for KERNAL support here - writing your own I2C bit-banging code was obviously already possible before.)
  12. Ah okay, a quick test shows that ESC and Ctrl-C both interrupt a Basic program, so it's probably mapped to the Stop key in the emulator. Using the WASD keyboard, RUN/STOP, 40/80 (and potentially RESTORE, but how do I check that?) don't work as expected. I suspect there's a reason for it, but is it a good reason? I imagine it might be a pain to get Scroll Lock key presses consistently on all supported platforms, or something like that?
  13. Maybe I'm missing the obvious here, but why not use ESC for that?
  14. True. You'll probably want to start here: https://github.com/ghidraninja/
×
×
  • Create New...

Important Information

Please review our Terms of Use