Thanks for your insight! I think that if your trackloader knows where your interrupts are called/sprites are displayed and does not load there, you can use sprites and interrupts with a 2-bit loader. I should do a routine to display some koala pictures + sprite scroller on the sideborders at some ...

Most drive turbos use normal bus protocol but for the main data transfer. I've never had any other devices in IEC bus than a 1541, but printer has a device number <8 and Star Turbo, for example, checks for this and falls back to KERNAL routines in this case, as well as in another special case from ...

I wasn't able to quit looking at the turbo code.. Having a look at the drive memory wasn't enlightening to say at least, it was very confusing. I couldn't find code like I excepted in the drive mem. Also the turbo copies some data to cassette buffer which is then executed, but also modified by some ...

There are several turbos in http://sta.c64.org/c64utils.html . I disassembled, mostly for curiosity, Star Turbo by Joe Forster/STA (I presume as there is no author mentioned) and found out it uses 2-bit transfer like I described. There is no source code but the code is mostly not too difficult to ...

Hi,

I have read a magazine article about Pink Floyd drive turbo (in Finnish, sorry) a long time ago, and there were two main points considered in that article. First, C64 and drive cpus are running at approximately same frequency, so DATA and CLK lines can be used as 2-bit parallel port, sync can ...

call "cls" "home" "print" "newline" like a vt100 terminal and, asking more, curses lib if and only if it can fit in some kbytes, portable.

Most OSes for 8-bits had these, and more. Curses is an abhorrent abomination. Trust me on this, as an OS developer myself, you do NOT want to deal with the ...

As it is much faster to make a 8-bit tag compare than two 16-bit pointer compares, I think I'll go with 24-bit general datatype at this point, although it will waste some memory I think there will be plenty of it left for data. I have studied Forth a bit, and have more extensively studied some other ...

.
Putting on the asbestos suit..
I hope I don't come across as flaming, but I don't want the obligation to "be nice" to keep us from making our points. I don't want anyone else to back down either if they can see that I still didn't get their point.

Thanks for your insight. I was just trying to ...

Thanks again for these links, I'm going to read them now. Actually R. Kent Dygwig's paper is the one I referred to when I said I've read a paper about Lisp optimization :) I think I will read it once more though. I'm going to use a stack-based approach. There is one other paper I know of, http://www ...

I used to use Turbo Assembler in the '90s for programming the C64. Recently I tried to find a newer version of it as I wanted a native assembler but the old version has some missing features. Guess what? Latest version has been released in 2006 under name Turbo Macro Pro. It is basically the same ...

But then, you want a compiler, not an interpreter...


Thanks for your comments! I will first do just a simple interpreter, as I have read some papers on Lisp optimization, as well as the Dragon Book (Compilers: Principles, Techniques and tools) and the compiler is going to take some time and ...

I just registered, but I have some ideas as well, many of them from some RISC processors. I am not proposing a RISC processor however because that's not what a 65xxx is anyway. It is possible that some think my ideas don't retain the spirit of 65xxx processors but I think they definitely do, while ...

Hi,

Edit: I forgot to mention that if you know any existing Lisp implementation for 6502 I am also interested to have a look at it for ideas, although I'm quite convinced I need to write my own to get what I really want.

I used to program C64 in assembly back in the '90s, writing a few intros and ...