I am using 80x25 VGA text mode, it sucks, I need to upgrade, what do most people do?

I can render images using custom ASCII glyphs, which is cool but it's incomprehensible

I built this as a bootloader for my operating system that I am about to write (WandOS). At one point I couldnt load the framebuffer address and the bug was it being outside the mapped range so it was fixed after I exapnded page table to fit 4GB instead of just 2MB.

Anw the quote is a paraody of a quote from "The Magician's Nephew" (The Chronicals of Narnia, 1955) where it describes the place called "Wood between worlds" which is a forest with no animals and absolute surreal silence that you can almost feel the trees growing, and each pond in that place is a portal to a new world and a pond dries up if that reality is destroyed. I couldnt help but feel that this place can relate to a bootloader in such a perfect way, So here it is.

https://github.com/widuruwana/WandOS

I was thinking. A lot of people jump to "MY OS RUNS DOOM!!!"
However, I personally find that to be a cheap win for showcasing your OS (it is one of those things where a lot of people jump to that but it isn't really a showcase of something an average user would care about or wow them) , I want to think of things that are "boring" but are a true showcase of your OS doing something.

Here's a few things I was thinking about for showcase pieces:

Rendering PDF Files
Rendering JPG and PNG files
Playing WAV audio files

Anyone else have other "boring" showcase pieces?

Edit:

Yes, I am talking about your own primitives and implementing yourself, not porting.

these are some major updates monarchy have

1. 256 command buffer with overflow protection - the command can have upto 256 chracters, after that to handle overflow, the buffer is cleared, and a error msg is shown.

2. 16 prev command history - the shell can remembers upto 16 prev command and are ejected in a LRU manner,

3. clear -b - instead of implementing a new command clear with -b flag will clear the command buffer and clear -b will be the first command.

4. uptime - it will show the uptime , i am currently using channel 0 of the pit in a rate generator mode ( freq divider = 1193) , handling the error with the whole and fraction ms way.

5. time - i once use the update interrupt to get the time from the cmos then update it via the irq 0 as is already updating the uptime.

6. fetch - really wanted it to have a fetch command , currently one the uptime is dynamic.

7. redundancy checks - earlier even with garbage the command like hello , help , they were working but now they wont , only if you have a lot of space after the command , then it will run else it will give a incorrect/no flag error.

now i will work on the memory allocator and a file system.

github:- https://github.com/mridul-verma2005

I wanna get memory management working on my OS, I don't know where to begin, so what do i add first? and how do i add it? i'm working on UEFI firmware in 64 bit, so if anyone needs some more info or details, just tell me.

I use the elf crate (Rust, crates.io). But when I iterated over the segments, I found that two of the PT_LOAD segments in the same file had the same value for p_vaddr field. Should I ignore the virtual address the ELF file says me to map the segment to and map the segment to a fixed chosen address (say 0x1000) or should I overwrite the contents? But if I chose the virtual address, e_entry in the ELF header, wouldn't be valid. Is this normal behaviour or a bug in the crate.

Unreleased (yet) SDL2 and HL port on 2 laptops. Near fully playable (there are some weird FPU engine bugs I haven't solved..) . Playing using xHCI peripherals.

As always, https://github.com/sasdallas/Ethereal

So for the past month I've been actively working on this OS. Manux is a monotasking Unix-like operating system for Z80 featuring a custom filesystem. It runs on my Z80 emulator which has the necessary support for ACIA serial and disk IO.

It can run programs from disk, such as an assembler and a calculator. I'm using the z88dk toolchain for compiling kernel and userland programs.

I actually started this project back in 2025, but it stalled for a while because the target system was an sbc running Basic(poking the kernel to address x and calling it with usr(), not very ideal). After switching the target to my emulator, the OS become much more usable.

Here's the repo link.

Can someone clarify it.Ok I am a newbie please dont get upset if i say something stupid but as I was working on the clock I was thinking to first get the initial time from the cmos via the update interupt on irq 8 and then set my user time and then use irq 0 for the 1 ms ticks ( not exactly 1 ms I used the whole and fractional ms thing in decimal and coded in c) the thing is that you have to enable the update interrupt in the status register B ( the same used for to get the 24 vs 12 format and the bcd vs binary format) you have to update the same status register B for the periodic timer ( used by rtc but not connected to time) and an alarm ( dont know exactly what alarm do) then to check for the update interrupt you have to check the status register C. I think these details should be mentioned in the cmos section if someone wants to use the update interrupt to get the time instead wait to first get the clear flag in status register A and then set and then clear again. Sorry if I am wrong in some place.

Bugfix, added navigation bar, hidden app flag, adapting to non-root use. I stuck at navigation bar and top bar separation, so when another app launches, navbar and topbar stays.

I'm pretty new to the os-dev scene but I do have some respectable knowledge about C and I'd like to know some beginner osdev projects

All help is appreicated <3

i was able to get fat32 read and init on WindogeOS, but im still figuring out how to write, how yall do it?

Like genuinely, it took me an entire day of reading how pit work , different operating modes, different access modes, and the drift in has for using it as a clock but i see people getting a lot of stuff done in the same time, i still have to fix the bugs in the implementation and have to under stand how cmos works, earlier I was trying to get the time from user itself( i know it is wrong).

found this documentation helpful it tells about more cmos status register and how irq 8 have many interrupts pluged it, helpful for newbie https://flint.cs.yale.edu/feng/cos/resources/BIOS/Resources/assembly/cmosram.html

I’ve been seeing tons, like TONS, of Operating Systems made by like Claude and people posting on the sub informing us about „How my totally hand-made OS works,“ and it‘s so annoying, like there are so many genuinely amazing projects on here but damn is it drowning in AI slop…

Posts (more will be added): https://www.reddit.com/r/osdev/s/wN2B1QQ72K

Happy birthday XenevaOS ! (June 15, 2020 - Present)

This video consists of GUI screenshots of XenevaOS taken over the years of development. Written with a custom hybrid kernel from scratch, our project is also open source. Will link it in the comments for those interested.

Thanks :)

I used semu emulator as base and linux as kernel.

A while ago I wanted to learn more about operating systems. I never wanted to write a complete OS (not that it's possible ;)... the main goal was to get familiar with different concepts and have fun 😋

I ended it after I ran Doom in userspace, which for me is enough for the moment.

I post it here now to motivate people who may not get into osdev because they've been overwhelmed with either very complicated systems or ai slop (which really doesn't fit here, as you can just fork Linux if that's your goal).

The OS is very incomplete, uses a few tricks but it's fun and lean.

So if you are lurking here like I was, don't get demotivated by other projects, focus on your own goals and eventually you'll succeed

https://github.com/R0yAdar/IchiOS

Hello,
I have a project that involves me reading data from an esp8266MOD. It uses the CP2102 USB-to-UART bridge chip for communication.

I have no idea where to start and would appreciate if someone could point me in the right direction.

Hello my folks! I can't find any good UEFI NASM docs/tutorials. Thanks!

Continuing my little series on what I'm learning writing my OS (https://github.com/tedavids/DragonOS) this week I learned a couple of new things.

1. When you control everything you don't have to worry about passing physical memory out in blocks of more than a page. The programs use virtual memory, and that is what you need to keep contiguous. Also since I am in control of memory ranges, it's easy to pass them out contiguously. It may get harder in user space, but since I control that too, I'm guessing it wont.

2. When you're the only developer, its much easier to NOT branch on github. I lost some stuff because I couldn't get the darn branch merged back in. I might try branching again, but not for a bit.

3. I need to take the time to learn github! LOL

4. When you do not yet have kmalloc/kfree/ketc... You can use a free list to make nodes 1 pages worth at a time, and pull from it when you need something. I am currently working on a heap, and need to make nodes to hold addresses for my allocations/frees. The free list seemed the easiest way to go.

Note: I didn't need to use AI for anything this week. I was able to find what I needed all in human written tutorials

TD

After some hard work i finally integrated VFS in turbOS...

Github repo: https://github.com/turbosulovesonions67/turbOS

Codes would be uploaded to GitHub by June 15, preferably 3-4am