0 Members and 2 Guests are viewing this topic.
Hello,Thanks to geekboy, I can access the forums. Thank you, geekboy.Also, I would like to point a few things out.The problem with the rom is the boot page. There actually isn't one. It just skips and hops its way over to page 00 for now, which is pretty stupid, but whatever.Also, if you guys want a chance to play around with a multithreaded OS, there already is one. It is semi-done, and I've played around with it. It's called BAOS, and you can get it here: http://www.ticalc.org/archives/files/fileinfo/398/39863.html.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.I tried KnightOS on hardware the other day, and it worked fine, with the exception of a buggy keyboard driver (O_o).Progress on my other projects is just chuggin along. I made a hex editor with Axe that I'm slowly working on, and I'm working on a floating point math library for Axe off and on. Mosaic is going good, the assembler is fast. The GUI is still non-functional, with a couple exceptions.
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)
yeah I'm really excited for when this becomes a true reality and we can start developing for it on a larger scale then I currently can
Wow, well done The version on SourceForge is actually pretty out of date. I haven't committed code in a while.
svn ci KOS --username sircmpwn -m "Awesomeness"