Jump to content

kelli217

Members
  • Posts

    308
  • Joined

  • Last visited

  • Days Won

    4

Everything posted by kelli217

  1. I'll note that the post with the reference to the Monarch HW project has been edited and the link removed. And it was the HW project that I thought was the potential problem anyway. (I might not have made that clear in my earlier post in this thread.) My concerns are now fully assuaged.
  2. What are the ramifications of this project with respect to this forum's Rule 5? Obviously the OS is 'just' an alternative to the existing ROMs. It could easily just be another page in the ROM banks. But the HW, if it has the memory banking system, and especially if it has a register-compatible video output system, to the point that it's supposed to be able to run software written for R39... this is very much a clone system.
  3. @BruceMcF has a FORTH for the X16. Or should I say, "X16 FORTH BruceMcF has"...
  4. You should play a MIDI file of "Louisiana Fairy Tale" by Fats Waller.
  5. I wonder if there's a market for custom cabinets in which to mount a modern TV with those sorts of beveled panels and round columns and other such things.
  6. With SID replacements like SwanSID, PLA replacements like PLAnkton, and the new VIC-II replacement being developed in Kawari, there are fewer and fewer original parts necessary to build a 'new' C64. (Of course, part shortages and supply chain issues are affecting everyone.)
  7. Ben Heck's portable Apple I clone is a fun little 'hardware demo' thing.
  8. The way a lot of old C64 programs did it (other than using $C000) was to move the top of BASIC down so that variables and garbage collection won't trash your code and then put the ML routine up there via a BASIC loader.
  9. Combine multiple sources of pseudo-randomness and the results should be a little less deterministic (i.e., 'more random').
  10. Until and unless this is implemented, I'd recommend using the PLOT routine in the KERNAL. It isn't that difficult to call it from BASIC. I wrote a comment about this quite some time ago.
  11. BLEAK Well, you can tell it was developed in the 2020s.
  12. ME was released when they thought that the big plans they had for XP (then 'Longhorn') would take too long to bring to market, and they needed a stopgap version. But then XP came out the very next year after they scrapped a lot of their more ambitious ideas. Then they proceeded to sell XP for six years while working on Vista. So I would never have made ME in the first place.
  13. The 4 and 400 are so close to being acceptable for everyday use, at least when you have a maxed-out 8GB RAM version.
  14. I think you might have conflated the numbering scheme for the 8-bit data bus version of the 68000 (68008) with the 8-bit address bus version of the 65C816 (65C802).
  15. It's a level of computing that I can wrap my head around without having to undertake serious study. I have enough ADHD-like traits that study is difficult for me; if I don't learn something super easily and quickly, I'm probably going to take a long time getting fully conversant in the subject. So, 8-bit computing is that point for me. The more primitive CPU architectures and the more primitive operating systems, anyway. Using SYS to invoke a KERNAL routine after having loaded locations 780 through 783 with register values... that's close to the upper bounds of dealing with complexity that I'm willing to do. Throw GEOS at me and I balk, even though that's 8-bit computing. The X16. to me, represents an incremental approach, rather than a shifting paradigm.
  16. I would combine an Ensoniq ES5503 with a Yamaha YM2608.
  17. There's a limit to how sophisticated these things can be, given speed and size constraints of retro or retro-like systems.
  18. Don't forget that you can use the COLOR command to control foreground and background text colors, too. It's a bit more versatile than reverse video.
  19. It's certainly in the running for the best 8-bit CPU ever. I don't think an OS like OS-9 could have been written on anything else.
  20. Built from what? You're WAY ahead of the actual state of things. The only X8 is in David and Frank's possession. The VHDL files and emulation code are not available in any publicly accessible repository. David asked the community if they wanted the X8 released as a product, but the community voted against it. That's a different question than yours. The premise of your question is set in a universe where the X8 is already available as a product, and then asks us if we would buy it. But we don't live in that universe.
  21. In some ways this reminds me of what geoLaser did. The C64 had just enough power to compose the PostScript code to be sent to the printer, and then the printer itself was responsible for turning that into a 300dpi raster on the printed page. In these days of GDI printers that don't have that kind of computing horsepower because it's expected that the PC will take care of that, then offloading the rasterizing to a Raspberry Pi seems perfectly reasonable. Technically, a page of US letter paper, edge to edge, at 300dpi, is 'only' 1051875 bytes in monochrome, which would easily fit in the available memory of a 2MB X16. But the dual hardships of USB and multiple incompatible manufacturer-specific GDI printer control protocols mean that it just isn't feasible to do it from the X16 itself.
×
×
  • Create New...

Important Information

Please review our Terms of Use