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

[Karlosoft]

I never used an English keyboard thank you for the info

[bzau]

[Combuster wrote:
Quote:
EDIT: Is there a way to make my pictures smaller?
How about not enlarging them in the first place? They should be 720x480 in 90x60 text...

That and I can't imagine that you don't know how mspaint or gimp works

Heh I'm on a mac, so no paint software. Will get gimp, though. My screen is 1024x1024 and my vmachine is full screen. But yeah shoulda thought about gimp]

many free toos mentioned here : http://www.squidoo.com/Shrink_A_Picture

[mariuszp]

Recently I've added a feature to my OS called BootLock, which allows you to program a compile-time password (and hash it!), and you can use this password during startup, reboot and shutdown. This is useful when you are trying to stop unauthorized users from messing with your system I've got a mgets() function which is like gets(), except masked

The password in the screenshot says "greetings to osdev!"

[bluemoon]

Bluemoon is an 32-bit hobby OS project started on dec 2010.

Implemented features:
- Higher-half kernel
- On-demand paging, kmalloc, kfree, mmap stuff
- process scheduler
- driver interfaces, implemented ramdisk, tbfs(my own simple fs), pci bus, and bochs video card
- some INT80 syscall
- basic newlib functions
- VFS layer
- automatic load all drivers from initrd (plan to load on demand later)
- ring0 kernel threads
- execute ring3 application (dummy shell)

@7 Mar 2012:
Added latest screenshot after rewritten almost all code...


@1 May 2012:
rewrite bluemoon as 64-bit OS.

kernel @ -2GB space (-mcmodel=kernel)
- load built-in drivers (ramdisk and tablefs/my own fs with just table of content and file payload)
- load more drivers from initrd (pci, bga, rtl8139), they are compiled as ELF64 with -fPIC
- detect hardware on pci bus
- found bga
- open a file using VFS layer
- memcpy a bmp to bga's frame buffer

@6 May 2012:
Support userland application, basic newlib functionalities.

[DavidCooper]

Hex mode added and it seems to work properly.

[Neolander]

What does this stuff all mean ?

[Neolander]

Should I assume from what I have read that this is a sort of hexadecimal editor working directly on top of the RAM, designed for direct machine language programming, and that the lines with text inside are all comments ? But then where are those comments stored ? Does the OS have some sort of private storage region that cannot be accessed via the editor ?

[DavidCooper]

Should I assume from what I have read that this is a sort of hexadecimal editor working directly on top of the RAM, designed for direct machine language programming, and that the lines with text inside are all comments?

It's simply a machine code editor: it lets you write program code directly into memory as machine code instructions, and then it lets you edit your code without having to worry about it instantly breaking in thousands of places whenever you shift parts of it about. I've never used a hex editor so I can't usefully compare the two things. Maybe in time it will acquire the full capability of a hex editor, but that is not its purpose - it is designed to be able to build and maintain itself, to build an operating system on top of itself, and to build applications to run on top of the operating system.

But then where are those comments stored ? Does the OS have some sort of private storage region that cannot be accessed via the editor ?

Each code cell (often a 64K chunk of memory) has its code growing upwards from the base while the indexes grow downwards from the top - once the two things meet in the middle, the cell is full and no more can be written in it. You can see the index data just by looking in the right places in memory and you can edit the content if you need to (e.g. to repair minor errors). The indexes are typically a half to two thirds as big as the code in their cell, but that space could be reclaimed once paging is added to the OS - the indexes are only needed for linking code cells together (e.g. when loading applications) and for modifying code (when writing or editing programs).

This thread is intended for snapshots (discussions tend to get moved out of it), so if anyone needs to ask further questions, the best place to do so is probably the MSB-OS thread in the announcements forum.

[rand]

Since I'm not a full time low level developer, I feel like big efforts for little results are worth a screenshot, so here is my kernel splash, launched from self made bootloader:

[Nessphoro]

Hmm, here is mine OS - not much, but I really like it

[fzajac]

Hi guys, my name is Filip Zając and i'm new here but instead of introducing myself i thought that i will show you my OS.
I see some of you are doing really great stuff, i'm nowhere near what most of you have done. I'm using real mode with some BIOS interrupts so call me a n00b or whatever xD
Anyway i just thought i will share a screenshot as yesterday my OS started to look cool (don't want to sound narcissistic or anything but i really like the fact that i'm able to do all that colorful sh*t in text mode since i'm no longer using 10h 13h )!

[piranha]

Hi guys. I just solved a string of several major bugs in my OS (for example, processes literally disappearing, and other things). Anyway, I now have e2fsck running on my OS (actually have had it ported for some time, but just now got it stable). Plus, as far as I can see, there aren't any errors from my ext2 driver (which must be compliant enough for e2fsck to not complain [except that the "directories aren't optimized" and the superblock write time, but thats an easy fix], woo!). Heres a screenshot.



Yeah! I'm approaching a release soon, and I'll post it under announcements probably within a couple months.

-JL

[Neolander]

@fzajac : Cool screenshots ! If I can criticize a little bit, though, you should add more spacing between lines in the text rendering code that produced the second screenshot. Text that's so tightly packed is quite hard to read.

[zhongyijun]

Lets dig up this thread again! I haven't posted any screenshots for a while so I thought I'd put in a few more.

Exclaim compiling itself:
http://alex-smith.me.uk/files/exclaim/image1.png
http://alex-smith.me.uk/files/exclaim/image2.png

Installing the compiled kernel/drivers:
http://alex-smith.me.uk/files/exclaim/image3.png
http://alex-smith.me.uk/files/exclaim/image4.png

Running the new kernel/drivers:
http://alex-smith.me.uk/files/exclaim/image5.png

Exploring the new kernel's symbol table with Nano:
http://alex-smith.me.uk/files/exclaim/image6.png

Test application using the Cairo graphics library:
http://alex-smith.me.uk/files/exclaim/image7.png

If you look at some of the dates on those shots you'll notice things are a bit slow - I still need to work on that... the ATA driver doesn't use DMA and the Ext2 driver is fairly inefficient... I added a block cache a few weeks ago so things aren't as slow as they used to be, but it still takes quite a while . In the next week or so I'd like to put out a new release of Exclaim (finally!), almost exactly a year after the last.

Well Done.A extraordinary GUI

[zhongyijun]

Milestone! Bash running on my os.

Good job.I want to port bash to my os too!