*** M E M O R U M ***

Any issues, problems, ideas do let us know.

It's had a lot of testing, but the more people try it, the more confident I'll be that my changes to the original SDX and FDX code don't do anything silly or unexpected.

I can't vote - there's no "I have one already" option

I'm tinkering with a co-processor design. Currently the idea is the idea is build it in 2 parts. 1) a half width*** Eurocard fitted with a controller rom for the MTX, in and out FIFO ram to facilitate communications, 2x 8 bit status ports one for each CPU. Both really need to be on this board as tha...

Re the crib sheet, a couple of things about the VDP section. The VDP registers for Graphics mode 2 should be Register 3 - FF Register 4 - 03 The TI documentation says for graphics mode 2 the LSB's should all be one's instead of 0. The only valid values for graphics 2 are supposed to be 7F or FF for ...

RST &28 is a an interesting RST call, It has all sorts of utility routines as well as the error handling and floating point. Like RST &10 it uses data bytes embedded in the program code to select the appropriate routine. Values 0-63 generate the appropriate error message. Ie. To halt with an...

I had a look at memory interleaving in the past. it was used on the 6502 quite a lot as that CPU does it's reads or writes in 1/2 a cycle, so it's relatively easy to share accesses, by giving the CPU access on one half of the clock cycle and the video hardware on the other. The Z80's reads and write...

I have 2 items on my wish list: A video board that's memory mapped instead of I/O, the 99x8 series of VDP's might make for easy hardware designs but the data transfer rate is compromised. Simple things like scrolling take a LOT more code and longer to execute than on their memory mapped cousins. The...

1024MAK wrote:Of course, the value that I wanted was in the last bag
Mark

At least they were IN the last bag, it's when they're not, and Maplin closed 10 mins before you get that AAAAGH moment!

Have fun testing, looking forward to some feedback.

I haven't tried FDXB on the Rememorizer. I've not got it on the SD card to test.

However I DO have a partial disassembly, and it looks like FDXB does it's own disc handling (it certainly trashes the CPM low memory) so I suspect the answer is its not compatible.

It's been a LONG time since I had access to a FDX, but from memory, FDXB puts everything on the 80 column screen by default.

Until you do CRVS & VS to do output through the VDP that side of things is just an uninitialised black screen.