Denial

Same with me (C64SD V2 Inf.), and of course I also have the SD2IEC in my FE3. Boray, regardless which one of the SD drives you obtain, you should pay a look which controller chip is being used. The recent firmware upgrades don't fit anymore into the smallest version (32K), you should definitely aim ...

Furthermore, all SD2IEC devices are JiffyDOS-enabled, so if you either have the JiffyDOS KERNAL installed in your VIC-20 or use SJLOAD you get a much bigger speed enhancement than what you get by just putting the SD drive into 1540 mode.

The screenshot and YouTube video look very promising! :D One small remark though: red and blue are a really low contrasting colour pair. Especially on B/W TVs it might become difficult to tell foxes and tree trunk from background. Assuming that red is realised as auxiliary colour, you could try oran...

I got an e-mail from Shaun Bebbington, he has finished the evaluation of the entries. The results are going to be featured in Commodore Free soon (as #72 has just been released without the results, that hopefully means in the next issue).

malcontent wrote:Someone's got to write stuff before you can read stuff.

You are addressing that to the wrong people.

Still nothing about the one- and two-liner competition.

For small ML routines, the range of 673 .. 767 is a good choice. These locations are not used in any way by BASIC. For slightly bigger routines, the tape buffer from 828 .. 1023 is also quite usable. It's however overwritten as soon as a tape operation is done, so it's more useful for floppy users. ...

Unless a custom handler has been installed in the vector of BRK (at $0316), the BRK instruction causes a warm restart of BASIC. This inits I/O and clears the screen (also your 'A' character), leaving you at the READY prompt. You should use RTS instead to return to BASIC from your ML program - and, B...

It's not going to have redefined characters, since I'm not experienced in making them [...] Actually, that's no reason not to use them. It's only slightly more complicated when a +8K or bigger RAM expansion is used. You need to set the BASIC start to an higher address, so the RAM 'below' your BASIC...

Are there other reasons to get 'out of memory' besides actually being out of memory? Yes, there are. FOR loops and GOSUBs are stored on the stack; when there are too many open FOR loops and/or nested sub-routines, even a simple expression evaluation might not have enough spare memory on the stack t...

This is expected behaviour from the cc65 C runtime. It switches to the character set containing both lower- and uppercase letters, so there's a greater overlap in displayable characters between PETSCII and 7-bit ASCII. Anyway, that kind of questions should go into the section ' Emulation and Cross D...

For example, if I want to include #include <myfunction.h> I need to write the myfunction file, with the functions signatures, and teh myfunction.c with the code implementation. The compiler return me an error, because don't find the files myfunction.h and myfunction.c... I'm sorry to write this, bu...

You should be able to cut the JMP $C474 I just tried it out. Sadly, it doesn't quite work. Here's the remainder of SYS, when the return-address of the SYS call is preserved with JMP $C659: .E141 6C 14 00 JMP ($0014) ; call user routine with $E144 - 1 on stack .E144 08 PHP ; <- re-entry point .E145 ...

You should be able to cut the jmp $c474 [...] [t]his was previously discussed here: [...] Indeed, that one would save 3 bytes. Wow, this thread is from 2005! Perhaps the print line could be made shorter and/or easier to type by op[t]imizations specifically targetting the number of escape codes and/...

[...]it looks like an UNNEW. Spot on! :D Here's an assembly listing, without instruction addresses as the code is fully relocatable (which is also the reason SYS256*PEEK(648) works at all): LDA #$01 TAY STA ($2B),Y ; write a non-0 value to the first link-pointer JSR $C533 ; re-chain lines (which ma...