archive.worldofdragon.org

I do have a scanner and will gladly scan the inlays when I've figured out how many I need to do. I have quite a lot of stuff that needs sifting through and would like to do things on an industrial scale to make the best use of my time. Just to be a rotten tease I would add that I have two copies of ...

And thanks from me as well, Simon.

You said it would cost you. Would you mind saying how much? Is there a way of making a donation?

Writing to $FF02 (CLR $FF02) also causes the same problem under XROAR Yes, CLR $FF02 will cause flicker on both xroar and real hardware, the reason being it reads before it writes. (It's one of the read-modify-write instructions). To safely clear $ff02 it will be necessary to so something like CLRA...

Just to add my own observations: It's possible to get a stable split screen in xroar using both hsync and vsync interrupts if the interrupted code doesn't read locations $ff00 and $ff02, which clear the hsync and vsync flags. It's easy to verify this just by running a loop of instructions instead of...

Same here. No main page: Two computers, different operating systems & browsers.

It may be helpful to disassemble Steve Woolham's GraphText program. I've never seen this before. It works really well. Pretty sophisticated too... it must be hooked into BASIC in a number of places to do what it's doing. The heart of it is fairly simple though: A quick look through the disassembly ...

Surprisingly things are much, much better on the real hardware. I've got to thank you. I would have probably spent a couple of evenings trying to get this to work in xroar. Instead it was just the push I needed to get my D64 out of the loft and fire it up. It still works... yay! So the first thing ...

The main problem seems to be due to the fact that the sync signals can appear anywhere during execution of an instruction but the irq handler cannot begin until the instruction is finished. This means that the screen position is different each time the irq is called. Some instructions are a lot long...

I enjoy a challenge so I had a quick go at implementing a split screen as an irq routine. It nearly works so I'll see if I can do better during my lunch break

Actually, 350°C is not a bad temperature if you're reasonably confident at soldering. It's about picking the temperature that works best for the speed you work at. The key is to maintain a consistent temperature. The biggest problems are encountered when de-soldering. The solder reflows at a higher ...