Looking for tutorials should be, by now, a well-known mistake. The GDT Wiki page says enough about the GDT. Just use a programmer's calculator (GNOME calculator, Windows calculator in programmer mode...) for calculating bitfields, and it's enough.DeezRamChips wrote:do you know a good tutorial for IDT and GDT (in c if possible)
What does your OS look like? (Screen Shots..)
- BrightLight
- Member
- Posts: 901
- Joined: Sat Dec 27, 2014 9:11 am
- Location: Maadi, Cairo, Egypt
- Contact:
Re: What does your OS look like? (Screen Shots..)
You know your OS is advanced when you stop using the Intel programming guide as a reference.
Re: What does your OS look like? (Screen Shots..)
Not everybody can do that without understanding the basics of GDT.omarrx024 wrote:Looking for tutorials should be, by now, a well-known mistake. The GDT Wiki page says enough about the GDT. Just use a programmer's calculator (GNOME calculator, Windows calculator in programmer mode...) for calculating bitfields, and it's enough.DeezRamChips wrote:do you know a good tutorial for IDT and GDT (in c if possible)
Last edited by Octacone on Fri Jul 15, 2016 1:18 pm, edited 1 time in total.
OS: Basic OS
About: 32 Bit Monolithic Kernel Written in C++ and Assembly, Custom FAT 32 Bootloader
About: 32 Bit Monolithic Kernel Written in C++ and Assembly, Custom FAT 32 Bootloader
Re: What does your OS look like? (Screen Shots..)
I agree with Omar, the GDT OSDev Wiki page looks good to me.
"If you don't fail at least 90 percent of the time, you're not aiming high enough."
- Alan Kay
- Alan Kay
Re: What does your OS look like? (Screen Shots..)
Perhaps we should stay on topic here. To do so, I have attached a screenshot of my OS.
My blog: http://www.rivencove.com/
Re: What does your OS look like? (Screen Shots..)
Nice. It reminds me a lot of my user interface.dseller wrote:Perhaps we should stay on topic here. To do so, I have attached a screenshot of my OS.
(except for the graphics part...)
Project: OZone
Source: GitHub
Current Task: LIB/OBJ file support
"The more they overthink the plumbing, the easier it is to stop up the drain." - Montgomery Scott
Source: GitHub
Current Task: LIB/OBJ file support
"The more they overthink the plumbing, the easier it is to stop up the drain." - Montgomery Scott
Re: What does your OS look like? (Screen Shots..)
Finally enabled VESA.
Running at 1024x768x32.
Started working on a basic graphics library, shapes + gradients + text + bitmaps.
Running at 1024x768x32.
Started working on a basic graphics library, shapes + gradients + text + bitmaps.
- Attachments
-
- vesaGraphics.png (11.04 KiB) Viewed 4229 times
OS: Basic OS
About: 32 Bit Monolithic Kernel Written in C++ and Assembly, Custom FAT 32 Bootloader
About: 32 Bit Monolithic Kernel Written in C++ and Assembly, Custom FAT 32 Bootloader
- DeezRamChips
- Member
- Posts: 132
- Joined: Fri Apr 08, 2016 5:03 am
- Location: atapio.cpp - why won't you work :(
- Contact:
Re: What does your OS look like? (Screen Shots..)
Lol, I made the VESA function ^_^ (But not the text, how have you done that (My bitmap function ?) )thehardcoreOS wrote:Finally enabled VESA.
Running at 1024x768x32.
Started working on a basic graphics library, shapes + gradients + text + bitmaps.
My github page: https://github.com/AlexandreRouma
Meme-deving since 420 Bc !
YouTube: https://www.youtube.com/channel/UCyJnOD ... C8Y7pccc6A
Twitter: https://twitter.com/WhatsTheGeekYT
Meme-deving since 420 Bc !
YouTube: https://www.youtube.com/channel/UCyJnOD ... C8Y7pccc6A
Twitter: https://twitter.com/WhatsTheGeekYT
Re: What does your OS look like? (Screen Shots..)
Thanks for helping.DeezRamChips wrote:Lol, I made the VESA function ^_^ (But not the text, how have you done that (My bitmap function ?) )thehardcoreOS wrote:Finally enabled VESA.
Running at 1024x768x32.
Started working on a basic graphics library, shapes + gradients + text + bitmaps.
Me and my buddy remade the entire system. Now we can use points, sizes, different drawing methods, more shapes, etc.
I am using a bitmap font. You need to draw letters as you would draw pixels. But the pixels you want to draw must be in a specific format.
Last edited by Octacone on Thu May 11, 2017 12:02 pm, edited 1 time in total.
OS: Basic OS
About: 32 Bit Monolithic Kernel Written in C++ and Assembly, Custom FAT 32 Bootloader
About: 32 Bit Monolithic Kernel Written in C++ and Assembly, Custom FAT 32 Bootloader
Re: What does your OS look like? (Screen Shots..)
Successfully implemented TTF support (now I just need a proper fill algorithm)
The simpsons picture is a test for my jpg decoder, just picked a random picture xD
Got a fully working VFS (FAT32 and ISO9660) and a fully working network stack (can ping websites and do http requests to readt heir HTML, js, css, images etc)
Also have a working elf loader to run user files in ring3 (cmd.bin) and a working audio driver so I can play .wav files
Gonna add png and transparency support soon so I can finally work on the GUI.
The simpsons picture is a test for my jpg decoder, just picked a random picture xD
Got a fully working VFS (FAT32 and ISO9660) and a fully working network stack (can ping websites and do http requests to readt heir HTML, js, css, images etc)
Also have a working elf loader to run user files in ring3 (cmd.bin) and a working audio driver so I can play .wav files
Gonna add png and transparency support soon so I can finally work on the GUI.
Re: What does your OS look like? (Screen Shots..)
Now my OS looks really bad compared to yours.Ch4ozz wrote:Successfully implemented TTF support (now I just need a proper fill algorithm)
The simpsons picture is a test for my jpg decoder, just picked a random picture xD
Got a fully working VFS (FAT32 and ISO9660) and a fully working network stack (can ping websites and do http requests to readt heir HTML, js, css, images etc)
Also have a working elf loader to run user files in ring3 (cmd.bin) and a working audio driver so I can play .wav files
Gonna add png and transparency support soon so I can finally work on the GUI.
OS: Basic OS
About: 32 Bit Monolithic Kernel Written in C++ and Assembly, Custom FAT 32 Bootloader
About: 32 Bit Monolithic Kernel Written in C++ and Assembly, Custom FAT 32 Bootloader
- BrightLight
- Member
- Posts: 901
- Joined: Sat Dec 27, 2014 9:11 am
- Location: Maadi, Cairo, Egypt
- Contact:
Re: What does your OS look like? (Screen Shots..)
Ch4ozz: That looks awesome! Care to share more about your OS? Do you have a site/repository/disk image for download?
You know your OS is advanced when you stop using the Intel programming guide as a reference.
Re: What does your OS look like? (Screen Shots..)
Thanks manthehardcoreOS wrote:Now my OS looks really bad compared to yours.
Yours look nice too, how long are you working on it already?
Thanksomarrx024 wrote:Ch4ozz: That looks awesome! Care to share more about your OS? Do you have a site/repository/disk image for download?
Actually I didnt upload it on a repo, but I may do that when I cleaned up the mess
Download Iso: http://coo.bplaced.net/IceOS.iso
Hardware specs for my drivers are:
- SATA Controller with CD/DVD Drive (mounted iso)
- AC97 Soundcard
- AMD PCNet Fast III Network Card (Using Bridge if possible)
Please tell me what you think
PS: Left console has 2 interesting commands:
- mem (Displays memory usage in pages)
- ps (Lists running processes)
Right one has more features, just use help to see them!
Re: What does your OS look like? (Screen Shots..)
Ch4ozz
I tired out you operating system. Booted without any problems. Loading was fairly fast, GUI loaded as expected. As for the speed, GUI doesn't really lag, window dragging could be a bit faster(maybe, not necessary). Cursor is very responsive, I would like to see some DPI settings. I don't understand why are there two terminal windows. You need to add some more user commands. I definitely see a massive potential. By the way: how did you achieve so high resolution?
I tired out you operating system. Booted without any problems. Loading was fairly fast, GUI loaded as expected. As for the speed, GUI doesn't really lag, window dragging could be a bit faster(maybe, not necessary). Cursor is very responsive, I would like to see some DPI settings. I don't understand why are there two terminal windows. You need to add some more user commands. I definitely see a massive potential. By the way: how did you achieve so high resolution?
OS: Basic OS
About: 32 Bit Monolithic Kernel Written in C++ and Assembly, Custom FAT 32 Bootloader
About: 32 Bit Monolithic Kernel Written in C++ and Assembly, Custom FAT 32 Bootloader
Re: What does your OS look like? (Screen Shots..)
Something to keep this topic alive..
After 16 hours of work.
Started fresh because I needed a stable framework to build my OS on top of.
After 16 hours of work.
Started fresh because I needed a stable framework to build my OS on top of.
- Attachments
-
- BasicOS02.png (5.49 KiB) Viewed 3816 times
OS: Basic OS
About: 32 Bit Monolithic Kernel Written in C++ and Assembly, Custom FAT 32 Bootloader
About: 32 Bit Monolithic Kernel Written in C++ and Assembly, Custom FAT 32 Bootloader
Re: What does your OS look like? (Screen Shots..)
Looks good, starting a new project is a good decision usually because you wont do the same errors again.thehardcoreOS wrote:Something to keep this topic alive..
After 16 hours of work.
Started fresh because I needed a stable framework to build my OS on top of.
Im using VESA to draw the stuff, I can even go to 1920x1080 or higher if I wanted to (and if the crappy VESA implementations of the vms would support this).thehardcoreOS wrote:Ch4ozz
I tired out you operating system. Booted without any problems. Loading was fairly fast, GUI loaded as expected. As for the speed, GUI doesn't really lag, window dragging could be a bit faster(maybe, not necessary). Cursor is very responsive, I would like to see some DPI settings. I don't understand why are there two terminal windows. You need to add some more user commands. I definitely see a massive potential. By the way: how did you achieve so high resolution?
Anyways, dragging windows should be really fast because Im using a custom SSE3 implementation for my memcpy.
Which VM did you use?
I was too lazy to add virtual memory support which really depresses me because I'd have to rewrite ALOT of code since then.
Btw, the left console is a ring0 window from the kernel, the right one is a real application compiled as elf file which is stored on the cd drive image.
I need both at the moment because my message queue and stuff does not work 100% reliable yet