User Activity

  • Posted a comment on ticket #1911 on VICE

    Indeed, this seems to work as it should now (tested in version 3.7.1 r44394).

  • Posted a comment on ticket #1911 on VICE

    I use GTK Vice 3.7.1 on Windows 10.

  • Created ticket #1911 on VICE

    Next (n) in monitor in x128 works like step (z)

  • Posted a comment on ticket #1762 on VICE

    I just tried 3.7.1, and it seems to be working correctly.

  • Posted a comment on ticket #1762 on VICE

    Was I supposed to test this? I don't know how to try some experimental build. Was this change reverted?

  • Posted a comment on ticket #1762 on VICE

    From page 419 of Mapping the Commodore 128, describing the address $D506: "These bits actually determine the RAM block for all DMA (direct memory access) operations, not just for the VIC chip, but the VIC is the only built-in device in the 128 to use DMA. The only other commonly available DMA device for the 128 is the REC (RAM expansion controller) chip in the 1700 and 1750 Memory Expansion Modules. These bits, rather than bits 6-7 of the configuration register, determine which block of 128 system...

  • Posted a comment on ticket #1762 on VICE

    Including example program with instructions.

  • Posted a comment on ticket #1762 on VICE

    Can't seem to edit the ticket. As I'm sure you're aware, $ff00 is a shadow of $d500, and both $d500 and $d506 are part of the MMU. The problem is that on Vice $d500 controls which RAM bank is visible to the REU, when it should be $d506 that controls this.

View All

Personal Data

Username:
framsberg
Joined:
2005-01-31 10:15:03

Projects

  • No projects to display.

Personal Tools

Auth0 Logo