What does your OS look like? (Screen Shots..)

SpyderTL · **Joined:** Sun Sep 19, 2010 10:05 pm **Posts:** 1074

klange wrote:

octacone wrote:

You managed to write your own guest additions? =D>

Indeed, and documented it on the wiki.

Wow, nice work! I'm going to start adding VBox Guest Additions support right this moment!

f2 · **Posted:** Fri Sep 02, 2016 3:15 pm

Obsidian OS with some simple apps.

Attachment:

File comment: Obsidian OS - Apps

obsidian_apps.png [ 27.92 KiB | Viewed 6683 times ]

Octacone · **Joined:** Fri Aug 07, 2015 6:13 am **Posts:** 1134

@f2
Obsidian and Redstone you say... (*cough* Minecraft *cough*)
It looks really fancy. :wink:

Octacone · **Joined:** Fri Aug 07, 2015 6:13 am **Posts:** 1134

Attention!
That thing in the bottom right is a CAT.
I don't know how but it is a cat (at least that is what my bitmap array contains).

alexfru · **Joined:** Tue Mar 04, 2014 5:27 am **Posts:** 1108

Schrödinger's cat?

Octacone · **Joined:** Fri Aug 07, 2015 6:13 am **Posts:** 1134

alexfru wrote:

Schrödinger's cat?

More like devil's.

Octacone · **Joined:** Fri Aug 07, 2015 6:13 am **Posts:** 1134

Basic OS Update:
-Added fairly fast bitmap drawing function
-8 bit color support (for drawing wallpapers, no scaling support yet)
Graphics mode itself is 32 bit.
image

Update: also added 32 bit color support (for drawing wallpapers etc, no scaling support yet)
image in here

deleted · **Joined:** Mon Jul 21, 2014 7:23 pm **Posts:** 82

Lukand wrote:

@TrekOSDeveloper how do you get that line? Check stack?

Right now I am just using the __LINE__ Macro to print the line, but the stack is my next thing to implement.

The __LINE__ only prints the line that called it, but I also pass an additional u32int with the panic call, allowing for additional error codes, Register State, or interrupt number.

crunch · **Posted:** Sat Sep 03, 2016 9:01 pm

octacone wrote:

Basic OS Update:
-Added fairly fast bitmap drawing function
-8 bit color support (for drawing wallpapers, no scaling support yet)
Graphics mode itself is 32 bit.
image

Update: also added 32 bit color support (for drawing wallpapers etc, no scaling support yet)
image in here

That looks really nice man. What font are you using? 8x8 VGA bitmap?

klange · **Joined:** Wed Mar 30, 2011 12:31 am **Posts:** 676

I now have working NIC drivers for the AMD PCNet series, which means working networking in VirtualBox. Not many improvements to the stack itself, though; I'm lucky that VirtualBox acts similarly to QEMU, as I do the absolute bare minimum to get QEMU to route packets. At this point, VirtualBox is now my best supported environment, especially with the Guest Additions support.

Octacone · **Joined:** Fri Aug 07, 2015 6:13 am **Posts:** 1134

crunch wrote:

octacone wrote:

Basic OS Update:
-Added fairly fast bitmap drawing function
-8 bit color support (for drawing wallpapers, no scaling support yet)
Graphics mode itself is 32 bit.
image

Update: also added 32 bit color support (for drawing wallpapers etc, no scaling support yet)
image in here

That looks really nice man. What font are you using? 8x8 VGA bitmap?

Thanks man! I am using a custom BIOS like font I made pixel by pixel (bitmaps), it took me a while to get it all working. It is not really like 8x8, there are ones that are as big as 10x14.
Also your project seems very interesting to me, I was already wondering what was that PowerShell for.

@klange
That feeling when you are struggling with the memory management and that buddy next to you says that he has a working network...
Great job. You are one of my ideals.

FusT · **Posted:** Tue Sep 06, 2016 11:16 am

Got tired of debugging memory errors with just prtinf() and bochs dumps so I implemented kernel tracing:

Attachment:

Screenshot_20160906_191255.png [ 18.09 KiB | Viewed 6228 times ]

Here it's calling a method to print out an immediate trace, in this case from the heap's init function.

Was a pain in the backside to get the actual symbol names to print out right until I found out I missed some parentheses.
Used to be something like this:

Code:

(uint32_t *)sym->st_value + sym->st_size

while it clearly should be:

Code:

(uint32_t *)(sym->st_value + sym->st_size)

Can't believe I overlooked that for about 8 hours #-o

crunch · **Posted:** Tue Sep 06, 2016 7:00 pm

FusT wrote:

Got tired of debugging memory errors with just prtinf() and bochs dumps so I implemented kernel tracing:

Attachment:

Screenshot_20160906_191255.png

Here it's calling a method to print out an immediate trace, in this case from the heap's init function.

Was a pain in the backside to get the actual symbol names to print out right until I found out I missed some parentheses.
Used to be something like this:

Code:

(uint32_t *)sym->st_value + sym->st_size

while it clearly should be:

Code:

(uint32_t *)(sym->st_value + sym->st_size)

Can't believe I overlooked that for about 8 hours #-o

That's sweet man. I think I'm gonna add that functionality. I haven't messed around with ELF symbol tables yet.

Octacone · **Joined:** Fri Aug 07, 2015 6:13 am **Posts:** 1134

Basic OS Update:
-Added PCI listing (oh god this took a while to implement, all those devices :roll:

)
-Added RTC support (time + date)
-Added CPU Identification
-Added Graphics Identification

brunexgeek · **Joined:** Wed Dec 25, 2013 11:51 am **Posts:** 45

Nothing much to see here. This is from a kernel I started a couple weeks to run on Raspberry Pi boards. This screenshot is from a physical memory allocation test using the new and delete C++ operators.

OSDev.org

What does your OS look like? (Screen Shots..)

Who is online