MandelbrotOS VS toaruos

It's not as hard as people make it out to be. It's taken me a year or so of stupidity to write an OS that has the ability to load programs and all sorts of fun stuff (Not complete and whatever but it's something): https://github.com/MandelbrotOS/MandelbrotOS

Some do write OSes based on the Linux kernel, although I find the vast majority don't. But a large group will strive for POSIX compliancy so they get code compatibility but not binary compatibility. I suggest you do some much simpler stuff in C before you write an OS. I learned C by writing OSes and it was a really bad idea. Learn C and it's quirks before doing an OS. Some sauce to peak at (very bad)

It’s probs ok. I have all the ASM working already. https://github.com/MandelbrotOS/MandelbrotOS btw

I had this recently too. I am not sure why it caused it but I learned from here: https://forum.osdev.org/viewtopic.php?f=1&t=27373 that you can just do iretq and it seems to work. You could also just do sti and ret. Also I learned the hard way: do not copy 32 bit dit code to long mode. It always ends up bad. I have a project running that seems to have working interrupts. Use it for inspiration all you want. https://github.com/MandelbrotOS/MandelbrotOS/ Also excuse the bad code on my parts.

Another interesting project to checkout is klange’s toaruos https://github.com/klange/toaruos

In case it's not clear, PonyOS is a joke reskin of my serious OS project, ToaruOS. PonyOS gets a new release every April 1st. All of the libraries and applications in ToaruOS are in-house things I built myself - the whole OS is "built from scratch". PonyOS adds ponysay, which is an external app originally written in Python - and in previous releases of PonyOS I shipped the Python version alongside a port of Python 3.6. This release, though, comes with a port to my own language, Kuroko, which is a dialect of Python - a lot of what went into building the PonyOS release this year was getting ponysay to work well.

There is no correct way to use inline assembly here. You need a stub written in assembly that will save those registers to the stack and pass a pointer to a handler written in C. You may also want to define a struct that matches the stack layout to make it easier to access the stack contents. This is not my code. If you want to use this code in your OS, you must follow the license requirements.

Here's a good example, although it's 64-bit instead of 32-bit.

ToaruOS 2.0\ (5 comments)