Denial

And there it is: the fork system call: Enough for today…

%p A version written in C would be nice because TDD in assembly isn't… Got a little bit tangled up with the banking but that also went well. IO23 is always there (each process has its own copy) to catch KERNAL I/O calls and the rest is in BLK1. That's enough trouble if apps can use that too. Am wond...

You're welcome. We all ended up with about the same solution. Any turbo loading planned?

OK, here's the first part with BLK5 piggy-bagging another self-extracting PRG with the rest: prg_start = $11ff prg_sysaddr = $120d .zeropage s: sl: .res 1 sh: .res 1 d: dl: .res 1 dh: .res 1 c: cl: .res 1 ch: .res 1 .code main: jmp start blk5: .incbin "blk5.bin" blk5_end: prg: .incbin &quo...

*coffee*

You write a loader that's got the uncompressed BLK5 and an exomized binary with the rest in it. That thing you exomize too.
When it starts it copies BLK5 and relocates the exomized binary with the rest and launches that. You probably need to relocate the copy loop to relocate the latter. %p

Yeah! This should stay small. The egg-laying wool-milk-pig with power outlet nose and peeing gasoline here is the deque (doubly-linked list) on a (256 byte page) with byte pointers to previous/next elements. Multiple lists can share a page and removal/insertion ist really fast and happens at constan...

AndyH wrote: ↑Mon Mar 18, 2024 4:56 am

Code: Select all

exomizer sfx $1c00 maintape.prg 0400.prg -t55 -o tape.prg

You need to decrunsh in two parts, e.g. by putting an exomized prg into another.

The first executable starts with BLK5 decompressed which you copy to its place. Then you relocate the other exomizer binary you appended and run that.

This is so simple, one could actually do an entertaining 6502 programming book about it. (Am feeling elated.) TUNIX development is done tests first. The rest is only sketched code to get the big picture which is fun really with a brain-to-computer interface like VI (keyboard, not mouse). Test-driven...

It's been in the works for a while. :roll: So here's the plan if no deadline gets in the way (the literal one). # Planned system calls Downcase letters denote byte values. ## General * "SX" kill all processes and drivers and return to plain BASIC. * "SN" stops multi-tasking. * &q...

Thanks mate! Arukanoido is already much better than anyone could ever have hoped for! So if this is the "final version", so be it. Here's hoping for better times. VIC-20 coding should be for fun :D That would really be a pity as it's all there and up and running, ready for development in ...

I've added directories "archive" and "arukanoido"; the latter containing your desired binaries. My brain refuses to work on this any longer. Eviction notices for my neighbours didn't change that. And they threw me back financially and every other way for a couple of months, so I ...

Desired changes have to come along in the form of Github pull requests.

Should you care about premature source code, it's to be found here: https://github.com/SvenMichaelKlose/ing ... x/main.asm

It even has a vanity comment at the top. I'm secretly expecting this one day:

It is what it is: https://github.com/SvenMichaelKlose/arukanoido Does a full release build with all levels and bugs included. See 'download-and-install.sh' to get it up and running on whatever Linux. Please use one of those great online resources to resolve questions on Linux. "In The Making&qu...

Talking UltiMem: For the latest revision of INGLE there's a new kernel design. cc65's code generation unfortunately does not allow to use C as a macro assembler without taking all the fun away. Macros to the rescue and the fun is back. Key ideas: No assembly syscall table . Device #31 handles its do...