I love being quoted. ;-)

I don't know, ever since getting an Android phone and seeing how it's run on many different physical phones, I've been interested in seeing OSes be very portable.

I like the portability approach

True, but I'm thinking unless we get some standardization among the OSes and what programs they run, with all the OSes we are getting, it's going to be a mess.

Oh I meant the fact he wants his OS to be easy to port among all z80 devices, even non-calc ones. But I agree that it would be best if ParteOS and KOS, for example, had some compatibility or converters so people don't have to write games and programs for 3 different calculator OS platforms.

I'm actually working on a way to standardize stuff. But that's a secret project for now. ;-)

Cool to hear, that would be awesome

It would suck if the community was split, otherwise. Fewer people would play certain programs because they would use an OS that won't run them. Kinda like Linux vs M$ a few years ago.

Yeah, I know what you mean there.  The idea is to make OSes have the same core (Much like KOS does).  With the delay of KOS, I'm wondering if it would be possible to... Oh, that gives me a great idea, dj!

A compatability layer (kinda like Wine) is very feasible.  I've been playing with ways to do this with TIOS<->KOS compatability.

Actually, I'm thinking of something different, involving precompilation.  It would allow TIOS asm to run on KOS, and possibly the vice-versa.  It would also allow PartesOS and KOS compatibility.

This is what I'm thinking of:
Copy the program data twice into RAM.  In the first copy, scan it to find all the calls and all the lds.  If the call lies within the program code, modify it appropriately so that it will call the correct address (for instance, if its a TIOS program that is $200 bytes long, and the calls address lies within $9D95-$9F95, its an internal call).  For loads, change the address (if internal) to the second copy, or (if external), compare it with some SafeRAM values for the original OS and modify the pointers to match areas in RAM set aside to mock up the SafeRAM in the original OS.  Then keep a jump table that leads to routines that are similar to commonly used routines in the original OS.  Modify all external calls/jps matching one of these addresses to call your imitation jump table instead.
It wouldn't be perfect by any means, and there could be problems with SMC, but it could potentially run some programs across OSes.