Jump to content

kelli217

Members
  • Posts

    308
  • Joined

  • Last visited

  • Days Won

    4

Everything posted by kelli217

  1. @Kevin Williams has a form factor specification. I believe he'll also sell you a bare, perforated PCB for wire-wrapping prototype cards. I think the slot spec is done now.
  2. Huh. I guess I took it for granted that the connectors shown in 8BG's latest video was a pretty good list. Did he skip anything?
  3. Tom makes sense when he talks about going through the steps of calling a BDOS function instead of just switching banks. But as hjalfi also rightfully points out, there's no good mechanism for dealing with discontiguous RAM, nor for banked RAM even if it were contiguous. And Bruce's idea of using the banked RAM as a block device is one that many CP/M-80 systems with more than 64K of installed RAM have used before.
  4. I think you meant INPUT. READ is for DATA statements.
  5. That has indeed been previously discussed. Oh, hey, look! I figured out how to Outlook Express-ify the quote mechanism.
  6. Well, no. Its ideal disk drive is the SD card. The IEC stuff is mostly about backward compatibility and being able to 'rescue' the data that's 'trapped' on those old floppies.
  7. Heck, even a 1541 can go 6× faster than the standard C64 kernal routines, just by using a fastloader, so I think it's actually plenty fast enough.
  8. What Jimmy said. Make a slight change to the PRINT statement before you hit Enter the second time. Or print something like a system variable that constantly changes, such as TI (the system timer in 60ths of a second since boot).
  9. There isn't much activity currently; there's a board here, and there's a channel on the Discord, but primarily it's on GitHub, at https://github.com/tomxp411/monarch-os
  10. This seems to be a pet project of a lot of people. There's DOS/65, there's Monarch, there's your project CP/M-65... Yeah, Monarch isn't quite as close to CP/M as the other two, but it's still also designed around a BIOS/BDOS/CCP model. It doesn't call the layers that, though, and it doesn't try to replicate the CP/M API, nor does it try to provide file system cross-compatibility. DOS/65 doesn't call their layers that, either, but as I understand it the OS functionality is otherwise very similar to CP/M. CP/M is a bit tricky to implement on a 6502 (or 65C02), because of the memory-mapped I/O on a lot of platforms taking up so much address space, leaving a small TPA. The relatively narrow I/O channels used on the X16 should help with that. However, it has a rather large ROM that can't be switched out for RAM, which is kind of the same problem in a different guise.
  11. What does the code at $E343 do? Is there anything there that would conflict with being called directly vs being JMPed to at the end of a user-written ISR?
  12. So... what is PETSCHII, then? I am aware of PETSCII, of course.
  13. If you execute a command in immediate mode that doesn't cause the command itself to no longer be on the screen, you can just press the up-arrow key to get to that line again, and press Enter, and it will run again.
  14. You can use Ctrl-R in the emulator to get out of those, but it's closer to SYS64738 than to runstop-restore.
  15. Right now, the state of GEOS is... back-burner. The last version of the emulator that would come close to running GEOS, and would give you a 'deskTop' screen complete with a show of icons, was R38. The quick screencap shown in 8BG's video was done that way (I know because I made the screencap). Later releases don't get to that point. And even then, using R38, the applications don't work. You might occasionally get to the 'Create/Open/Quit' screen that most GEOS apps use when they start. But that's usually as far as you can get. How to do even that much requires that you go find an archive of the original GEOS disks in D64 format, and use the APPS64.D64 file. The official emulator has a secret trick up its sleeve. Instead of an SD card image, you can specify a D64 file on the command line: x16emu -sdcard APPS64.D64 Once you've started the emulator that way, and gotten to the READY. prompt, then just type the command GEOS and it will load the deskTop from the disk image and you can try it out.
  16. Kernal calls should start with a push of the value of $00 to the stack and should pull it back from the stack and restore it to $00 before the RTS. Same with interrupts, the handler should start with the push and should pull it back before RTI. I think this is already implemented in the kernal itself; if not, it's easy enough for a user program to do. I'm pretty sure that the default interrupt behavior is the same.
  17. The person who wrote the X16 version is fairly active on the Discord. They are trying to get it to the point where it requires a ROM image in order to work, at which point they can distribute 'everything else' and the user will have to acquire the ROM on their own. That way they won't be including any, uh, "odnetniN" assets and hopefully avoid trouble.
  18. Not an official one. But someone did make an unofficial 32-bit recompile of it. I think it's mentioned here, in the context of Windows XP? Try the forum's search function.
  19. There isn't going to be a datasette port.
  20. I seem to recall that @The 8-Bit Guy assisted in building an arcade cabinet for PETSCII Robots for some event. That would probably be a good place to start.
  21. Copy and paste works. Just use Ctrl-V and whatever's on your clipboard will be pasted in. (At least, that's how it works in Windows.)
  22. This is why most of the discussion is regarding workarounds, rather than saying, "Oh sure! We can make that last minute change that puts everything back in flux, no problem!"
  23. It looks like the project is sort of (but not quite) a CP/M-ish thing. Rather like DOS/65 but without that project's cross-platform file system.
  24. Are sprites scalable? Or do they have to be displayed in their native resolution? What does a 16×16 sprite look like when scaled to 3x? Is it ridiculously pixelated, or can careful design mitigate the problem?
×
×
  • Create New...

Important Information

Please review our Terms of Use