WabbitEmu doesn't work? Do you have a ROM? If not, use rom8x to get one.

... stuff ...

Developers should know that KnightOS will require coders to use location-independent code.  This means that using call, jp, and occasionally ld will not work.  However, I have included macros kcall, kjp, and kld for the programmers use, which will run slower the at first, but will run just as fast as the application's life progresses.

Calc84, nice to hear!  I look forward to seeing more about it.

Does anyone know how to set up the system interrupt?  I tried, but it didn't work too well, and looking through the source code from OS2 didn't help too much.

... more stuff ...

Hmm... how does the position-independent code regain normal speed? I'm thinking SMC as the answer there. Would this mean programs must be copied into RAM before they are run? (You never specified one way or the other)

Thanks.

By the system interrupt, I'm assuming you mean the default one.
you'll first want to disable interrupts with di, then change to the shadow registers with exx and ex af,af'. Then, I'll assume you want to see what device triggered the interrupt. Reading from port 04h will accomplish this. Then you'll want to reset the corresponding bit by writing to port 03h so that when you re-enable interrupts the interrupt won't be triggered again. At this point, you can then do whatever you need to. (Run the task switcher, deal with devices, etc.) Because $0056 and a few bytes after that must contain certain data, you'll want to jump elsewhere to run your code (probably after the ex af,af')
Documentation on ports 03h and 04h is available at WikiTI. The ports index is located at http://wikiti.brandonw.net/index.php?title=Category:83Plus:Ports:By_Address
Hope this helps!

Hurray for the feature! I might eventually play this, it looks nice.

That makes three people I know who are heading OS projects (our dear friend, me, and brandonw). I, however, promised myself I wouldn't mention mine anywhere except in my sig until I got at least a demo. (Right now I'm still planning features. I'll create a topic eventually.)
Good like to our dear friend!

I like that one (or maybe just Super Mario Bros 8x, without the "New"). I don't think that sounds like a level.
Or, in the spirit of the version for the 68k calcs, Super Mario z80 (or 8x, I guess)

yeah, it could be, but it would have to 256-byte aligned, like Galandros said. You're looking at a 257-513 byte increase in program size. The table would be where he said or between $9A00 and $9B00, $9B00 and $9C00, or so on.
It's 257 bytes because the i register, or the interrupt vector, serves as the high byte of an address where the lower byte is essentially random. (It has some structure, documented in AsmIn28, but I can't remember it). Because the read address could be anywhere between $xx00 and $xxFF, you need another byte to complete the two bytes it reads in case it reads from $xxFF.

Definitely not a full, patched OS. An oncalc, version-independent patch would be best, IMO.
Of course, if you don't feel like patching it, I think it wouldn't be too hard to just use )s. When I do program in BASIC, I avoid that type of For( loop anyway, or just use a ) for that reason.
But I'm not the only person here, so I wonder what others think should be done.
(Also: finally, a reason to use the OS-revalidator!)

Awesome video, DJ. Where are all these programs? I've never seen them.
And, yeah, for that to happen to Axe, or to any high-quality program, would be terrible.
This is why I don't program in BASIC unless I'm bored and can't be bothered to do it in Axe or ASM.