Show HN: MyraOS – My 32-bit operating system in C and ASM (Hack Club project)
github.comi would suggest to providing an iso or co-operating / looking into copy.sh which provides a large number of iso files which you can boot/play around with in the browser itself!
I was just today tinkering around with the ibm iso (exploring ibm) and others too, its always fun seeing new operating system!
I would love if you could, as I said, co-operate with copy.sh/v86 team to also include your iso and also provide iso files in github releases if possible
Source: https://copy.sh/v86/ Their github page : https://github.com/copy/v86
If I were you I'd investigate why it needs so much. Keep in mind how much functionality older OSs had, and how much computing power they needed. Always good to see more OS projects nonetheless, but always remember that efficiency is important.
(I later took that PC home and used it as the test machine for my own hobby OS, which had to run from a 1.44MB floppy because there was no other sane way to transfer the dev images from my desktop)
[1] One of these: https://www.computinghistory.org.uk/userdata/images/large/75...
But as always, it's your project done for yourself, so whatever feels like more fun recording.
I always wonder if there are any techniques to avoid these kind of bugs in huge projects like OSes and browsers, otherwise it can be a nightmare
That said, I’m once again reminded that we sorely need some updated resources for aspiring OS developers in 2025. Targeting 32-bit x86 and legacy devices that haven’t been “the norm” for decades suggests to me a heavy influence from resources like the osdev wiki which, while occasionally useful, are increasingly outdated in the modern world and lead to many questionable choices early on.
I have come to believe (through multiple iterations of my own OS projects) that there’s more value in largely ignoring resources such as osdev and focusing instead on first-principles design, correct layering, and building based on modern platforms (be that x86_64 or something else) and ignoring legacy devices like the PIT and PS2 etc.
I just wish we had good introductory documentation resources to reflect that, and that outdated resources weren’t overwhelmingly surfaced by search engines and now AI “summaries”.
None of the above is intended to take away from OPs achievement, which is fantastic, or from the work done over the years by the osdev community, who I’m sure largely do the best they can with what they have.
Of course, also supporting i386 with legacy BIOS is OK, but it doesn't really get into the meat of what computers are doing now when you power them on.
Finding people with the knowledge, time and willingness to proof-read is also hard - but surely not insurmountable if we collectively decide it’s an endeavour we want to pursue.
Interesting that 128 MB was not enough. What did you do to find this issue and how are you measuring memory usage?
i did something similar when i was 18. got to the point of filesystem and mouse driver.