Denial

Marsupial wrote:The diagnostic still reports a bad checksum... How can that be?

That shouldn't be.

Maybe there is an error in the checksumming code of the diagnostics, like out-of-bounds accesses. You should put an inquiry to nbla000 in the corresponding thread.

This bodge wire is ex factory and connects the cartridge port pin Y to the audio amplifier on the first revision of the CR board. It is officially documented in the Technical Manual, page 22: https://dateipfa.de/.Public/denial/images/schematics/Audio_In_Pin_Y.jpg Later revisions of the CR board inco...

https://sleepingelephant.com/ipw-web/bulletin/bb/viewtopic.php?t=10999&start=5 Footnote: MrSterling I follow your struggles with Vector graphics with intense interest. I don't contribute to your threads because I don't know enough to make a real sensible contribution, but I think like myself ma...

I currently run the motherboard with a clipped bodgewire until I find where the issue is, but running the same poke-peek command still returns 0. Not sure what that does tell me... It IS supposed to return 0 on a working machine! Would there have been mirroring by VA11 stuck-at-0 - the way I presum...

Great!

the Poke-peek returns 0. does that mean the mirroring fails? or that it is impossible to get it to something else than 0 (and why it isn't changing to upper/lower) You should be rather glad the sequence returns 0 - you do not want any mirroring here. The check was supposed to find out whether the p...

That had been discussed in the thread " New penultimate-plus-2-cartridge " some time ago already. The PU+2 does do no magic here though: it merely inspects the load address of the file (and tries) to config the RAM from that: unexpanded RAM with $1001, +3K RAM expansion for $0401, full RAM...

I assume you've isolated the keyboard as a cause by trying to switch by software? The diag test in the OP already fails to activate the lower/upper-case character set, which it quite surely does not do with a simulated key press of Shift + C=, but with a POKE to 36869. Very likely something on the ...

You should check whether VA11 on the mainboard is stuck-at-0.

Here is the draft of the first hardware design, should anyone want to replicate the prototype cartridge shown in the introductory post of the thread using a VIC-1210 +3K RAM expansion as carrier: 2716 +----\/----+ 1 -|A7 Vcc|- 24 2 -|A6 A8|- 23 3 -|A5 A9|- 22 4 -|A4 Vpp|- 21 5 -|A3 /OE|- 20 6 -|A2 A...

For completeness, here goes:

• MINIMON firmware, built at $9800. (thread) - *.bin file without load address.

Greetings,

Michael

I do not know if this is supposed to be a pop quiz, but anyhow ... Is the routine for reading the pixel correct? No, it is not. In "ReadPixel:" the instruction "cmp xtable,x" is the wrong one for the job. You could have found this out by yourself already by testing the routine be...

Do you know the VIC that did not like Cheese and Onion? The improvement on the timing logic from 2-prong to DIN/CR had been covered in this thread here: " Anyone know what this board mod is? ", to quote: [...] On the 2-prong, the VR/W signal is simply disconnected from CR/W during VIC fet...

What? %p I can't get my imagery to picture MINIPAINT with a web interface and user accounts. You completely forgot there's already a working native solution for editing graphics, sprite sheets in particular, on the VIC-20. Coders and graphicians already teamed up ages ago to collaborate on game gra...

Mike wrote:MINIPAINT? [...]

pixel wrote:OK... Was only remembering BASIC extension things about it.

You should be very cautious with complaining about 'isolated tools' and 'non-availability of (source) code' in your Manifesto if you otherwise are oblivious of prior art.