Denial

I found a workaround. In the VIC20 subdirectory of the VICE directory, rename/delete win_sym.vkm, then copy/rename win_sym_US.vkm to win_sym.vkm.

This might be a problem: In xvic, if I choose Settings -> Keyboard Settings... and bring up the Keymap Settings dialog box, then change the Active keymap dropdown from "Symbolic" to "Symbolic (User)" then click the OK button, when I go back in, it's changed back to "Symbolic...

After comparing the various key mapping files in the WinVICE directory on my Windows 10 PC, I have found the following: The win_pos.vkm and win_sym.vkm files in the VIC20 directory are identical. Therefore, specifying either one will result in using the symbolic mapping. In the win_sym_US.vkm file t...

I don't mind constructive criticism, and being corrected here bother me as much as also being chastised in a whole other thread This was really just a quick hack that I came up with while working on another more involved project. When I posted it, it was I'm response to the original thread about the...

Sorry for wasting your time with my ignorance. I'm done posting here.

Schema wrote:Bobbi you need to come to one of our monthly meetings! 3rd Thursday of every month.

http://www.tpug.ca/category/meetings/

So how long has TPUG been around now?

Rather, I pointed to some 'standards' a wedge in the BASIC interpreter has to honor with regard to register usage, flag register usage, RAM usage and other side effects. Any such wedge should in principle behave as if it wasn't there , and from that point on carefully nudge the BASIC interpreter in...

With the rare exception of customized ROMs to fix bugs, I think you can assume that every VIC 20 is going to have the exact same Basic ROM.

So if you want to save those few bytes, I don't see a problem with tracking the register usage.

I'm just not sure it's always worth the trouble.

It just so happens I've been playing around in assembly with the USR function and Floating Point, so I wrote a little program to print the actual binary representation of any floating point number. The program is assembled into the cassette buffer, so load it using LOAD "FPHEX.PRG",8,1 NEW...

So the GeoRAM basically took up both I/O blocks on the C64, then. I need to look at three memory maps again. It seems I'm not as good at mental hexadecimal as I used to be.

Also, I was fairly certain that Geos used the GeoRAM for swapping. I don't know how many other programs supported it.

The I/O areas on the C64 are also 1KB. The GeoRAM design put the 256 byte page at the bottom of the 1k and the two control registers at the top, wasting a lot of space. Of course it was not really meant for direct memory access, but for memory swapping. I'm a bit dubious about the VICE implementatio...

Hey guys, I'm back. Anyway, I somehow got obsessed with the idea of using GeoRAM on the Vic20 using the Masc=uerade adapter, since this configuration is supported by VICE. Anyway, here are the relevant memory locations: 40959 - $9fff - block selection, each block is 16KB 40958 - $9ffe - select a 256...

I LOLed.

I suspect the problem is that unlike other computers, the CBM's don't record audio signals on the cassette.

Thanks for testing, and the quick intro to cc64. I figured that since other people are using it they would have an easier time doing the test than me. As for TCB02, the code in question would be. INCLUDE "HEADER" INCLUDE "CONSOLE" INCLUDE "PRINT" PRINT "HELLO, WORL...