Denial

I'm also thinking about getting rid of the rune symbols in green that represent Alignment+Sex+Race+Class and the numbers on that line and use power bars to represent hit points and spell units. I was quite attached to the rune symbols because these were inspired by a dream that I had and said dream...

It still blows my mind a little that USR can return a string value.

pixel wrote:If there only was a C compiler that could be easily modified to produce bytecode. Then one could make a VIC desktop without wasting too much time.

C02 has C-like syntax and generates fairly optimized assembly code. But it only supports 8-bit expressions.
https://github.com/RevCurtisP/C02

It seems to me that the VIC-20 was hacked together by mad geniuses, but that seems to be the norm in that era.

I also came up with this mapping of the Screen and Character Memory register bits to memory address as seen by the 6502. VIC Register 9002 E------- 9005 ABCDFGHI 6502 Address High Byte Low Byte Screen Memory !A00BCDE0 00000000 Character ROM !F00GHI00 00000000 Note: A and F only are inverted. Buildin...

Mike wrote: while the VIC has its turn, the colour RAM is disconnected from the lower half of the BDx data bus. Instead, the colour RAM data is read in parallel to the text screen data over four extra data pins (VD8..VD11) of the VIC chip.

Is this why the VIC-20 doesn't hav "bad lines" like the C64?

Mike wrote:Nice! VIC can't read its own registers, or the VIA registers *), or the colour RAM **) for text screen and character data, though.

So the 6502 can read/write them, but the ViC-20 can't. I'll update my document. Thanks.

I combined a couple sources to come up with this unified 6565 memory map. Edit: Updated to include VIA and VIC chip corrections. VIC-20 6560 Memory Map by RevCurtisP +---------------------------------------+ | 6560 = VIC Chip Decoded Address | | Scrn = Screen Memory Location | | Reg 5 Hi Nybble + Re...

It seems this chip was used a few different places. https://en.wikipedia.org/wiki/General_Instrument_SP0256#SP0256-AL2 and here's code from MAME to emulate it https://github.com/MisterTea/MAMEHub/blob/master/Sources/Emulator/src/emu/sound/sp0256.h https://github.com/MisterTea/MAMEHub/blob/master/Sou...

Arghh! looked at this so many times before realising I'd updated the wrong number when changing from VIA 1 to 2. I had changed the second digit to 2 rather than the 3rd. Ie, changed $9118 to $9218 instead of $9128. Hours wasted trying to understand why it wasn't working. I blame my old eyes! If you...

I'll be watching when it hits Netflix.

The reason it doesn't work is because the VIC-20 and C64 use slightly different keyboard matrixes.

Does the C64 one work with x64? If so, it shouldn't be too difficult to convert it to work with xVic.

Ya even the first IBM PC, the 5150 has a cassette port (DB-25 connector and labelled as such) as an option. I haven't yet restored my IBM's, but I managed to get 4 early ones several years ago. They came with no monitor or keyboards, alas. So I cannot speak to how exactly one might use them in prac...

Mayhem wrote:Was a bit surprised by the permissions thing...

When it comes to Windows, the NTFS file system, and permissions, nothing surpises me anymore.

I ran into the same problem when starting to use version 3.1, I basically changed the permissions on the VICE folders I have to be fully admin controlled, and now I can change and save the keyboard mapping settings. Which O/S are you using and what directory was VICE installed in. Did you have the ...