Re: What does your OS look like? (Screen Shots..)
Posted: Mon Jul 11, 2016 1:24 pm
ATA driver and some VFS corruption.
The Place to Start for Operating System Developers
http://f.osdev.org/
Wow, and here I thought you'd be working in assembly forever! What made you decide to move to C?omarrx024 wrote:Preemtive multitasking, after hours and hours of debugging.
The scheduler is not complete yet; it doesn't save the state of a task before switching to the next task, and so always starts execution at the beginning. I have all night to finish it.
When I decided to create an x86 and x86_64 OS mostly from the same code. Porting my OS to x86_64 now would only require changes in the initialization and paging code.cheapskate01 wrote:Wow, and here I thought you'd be working in assembly forever! What made you decide to move to C?
Ah, alright then, best wishesomarrx024 wrote:When I decided to create an x86 and x86_64 OS mostly from the same code. Porting my OS to x86_64 now would only require changes in the initialization and paging code.cheapskate01 wrote:Wow, and here I thought you'd be working in assembly forever! What made you decide to move to C?
Thanks!cheapskate01 wrote:Ah, alright then, best wishes
I wish I was any good at thisthehardcoreOS wrote:Basic 320x200 VGA driver. With 256 (64) colors.
Drawing test: basic "desktop" with filled and outlined rectangles + z order.
Lol really? It isn't that good.cheapskate01 wrote:I wish I was any good at thisthehardcoreOS wrote:Basic 320x200 VGA driver. With 256 (64) colors.
Drawing test: basic "desktop" with filled and outlined rectangles + z order.
I'm jealous.
Yeah. I mean, I can change video modes, but thats about all. I've been trying to tackle basic stuff like gdt idt and keystrokes. at least you have a good system laid by now.thehardcoreOS wrote:Lol really? It isn't that good.cheapskate01 wrote:I wish I was any good at thisthehardcoreOS wrote:Basic 320x200 VGA driver. With 256 (64) colors.
Drawing test: basic "desktop" with filled and outlined rectangles + z order.
I'm jealous.
Yeah, you need to have some foundations. For beginners GDT and IDT aren't easy task. You need to make your OS step by step, you can not have graphics mode right after you start. But once you get something to work, you get an amazing feel of happiness and satisfaction, you know you've achieved something.cheapskate01 wrote: Yeah. I mean, I can change video modes, but thats about all. I've been trying to tackle basic stuff like gdt idt and keystrokes. at least you have a good system laid by now.
I agree, in my last OS, I use the code of someone eslse for the GDT and IDT, but now I'm making my ownthehardcoreOS wrote:Yeah, you need to have some foundations. For beginners GDT and IDT aren't easy task. You need to make your OS step by step, you can not have graphics mode right after you start. But once you get something to work, you get an amazing feel of happiness and satisfaction, you know you've achieved something.cheapskate01 wrote: Yeah. I mean, I can change video modes, but thats about all. I've been trying to tackle basic stuff like gdt idt and keystrokes. at least you have a good system laid by now.
Yeah, there are couple of good ones on YouTube.DeezRamChips wrote:I agree, in my last OS, I use the code of someone eslse for the GDT and IDT, but now I'm making my ownthehardcoreOS wrote:Yeah, you need to have some foundations. For beginners GDT and IDT aren't easy task. You need to make your OS step by step, you can not have graphics mode right after you start. But once you get something to work, you get an amazing feel of happiness and satisfaction, you know you've achieved something.cheapskate01 wrote: Yeah. I mean, I can change video modes, but thats about all. I've been trying to tackle basic stuff like gdt idt and keystrokes. at least you have a good system laid by now.
But it's realy not eazy.
do you know a good tutorial for IDT and GDT (in c if possible)