kelli217

The actual Linux kernel? I think if you stripped it down to the core, sure you can probably fit the basic task scheduler and core API in the 2MB memory space of an X16. Whether or not it would be able to do anything useful is anyone's guess. And at 8MHz it would run like a pitch drop experiment. There are other multitasking systems that are more suitable for the speed and the memory space available. Lunix, GeckOS, Contiki, picoOS...

Sorry, oops. I seem to recall having read somewhere that the XP release was originally supposed to have been based on the Longhorn project and got scaled back to being a bunch of interface changes to Windows 2000, thus XP was 5.1 to W2K's 5.0. But my recollection is probably quite muddled at this point, 21 years or so down the road.

Make sure that you are using the correct version of the emulator for the program. I seem to recall there being a thread elsewhere on this site about which version it was written for — subsequent versions have changes to the ROM and changes to the hardware addressing that break the game.

If something goes wrong inside the subroutine, you might not want the program execution flow to return to the calling GOSUB (or, more specifically, to the statement following it). You might want to do some error-handling, such as outputting an error message.

The functional changes are always being tweaked. It's why we're on ROM version 41. As far as comments go, Michael probably started with copious comments but he's been over it so much by now he could probably recite any given KERNAL or BASIC function's code from memory.

Yeah, I know why. Something got jumbled up somewhere. The order of registers for making a SYS call is A, X, Y, SR for $30C through $30F; Tom's original post has them all rotated.

I'm a bit familiar with the PLOT function. I may have mentioned it here on this forum once or twice... But the keyboard stuff is quite interesting. I've seen it done many times; rarely have I seen an explanation.

Is the Atari one... trying to play "Rhythm is a Dancer" by 'SNAP!'?

I vote for start-of-file just because there's less setup calculation involved.

Maybe someone could write an APL interpreter and/or compiler, and thus of course an APL keyboard would be a necessity—not to mention that the APL character set would also have to be supported...

Colemak?

I've included the tokenized BASIC program. There's something odd about it. If you load this, list it to make sure it's okay, then run it, then list it again, you should find new lines added to the program. In fact, I've loaded the program, and just made some edits to it (like changing the color specified by D to something like D+127 or whatever) and not even run it, and listed it and gotten new lines added. If I type it in manually, it works fine. Something about the loading process is wreaking havoc. Here's the source: 10 SCREEN 128 40 X(1)=159:Y(1)=0 50 X(2)=0:Y(2)=199 60 X(3)=319:Y(3)=199 70 X=X(1):Y=Y(1) 80 D=RND(1)*3+1 90 X=X/2+X(D)/2 100 Y=Y/2+Y(D)/2 110 PSET X,Y,D+2 120 GOTO 80 SIERPINSKI.PRG

Usually they have alternative services available for international viewing. Keep checking. When Discovery was on CBS All Access at first, this service was also unavailable in other countries than the US. But the show was made available on Netflix in those places.

It seems as though something is trashing BASIC pointers. I loaded a program and ran it and then listed it, and there were new lines in the program with seemingly random content. The program doesn't try to hit hardware, and uses the BASIC routines exclusively. I have a dump file... dump.bin

Well, I guess I should have read the docs more thoroughly.