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

[Peterbjornx]

Working on a userland debugger interface based around procfs

[bloodline]

In December I set about trying to get my filesystem interface working properly... But I was finding it rather tedious, and I found myself losing motivation... Fortunately @spotracite gave me some very positive feedback regarding my GUI, and encouraged me to put some time into developing that.

The result is that I’ve fixed a bunch of GUI bugs (including a very serious composition bug which allowed covered/invisible rects to be marked as visible under certain conditions), have properly implemented gadgets and events... and as bonus I was able to easily add theming (as spotracite like the look of the classic Mac, so I wanted to make it more usable for him).

So I thought I would show the current three GUI themes available:

Normal:


Classic Mac:


AmigaOS3:


-edit- This was a suitable distraction from working on boring filesystem code... and has kept me motivated! I’ll try and push on with my filesystem code in the new year.

The themes currently need to be selected at compile time, though there is absolutely no reason why it can’t be runtime switchable... watch this space

[CorruptedByCPU]

Some changes

Next will be:
- calculator,
- graphics editor,
- tetris like game.



Previous post: viewtopic.php?f=1&t=12087&start=3510#p308511

[PeterX]

At @bloodline and @akasei: Both very impressive: The GUI is looking good and the OS seems quite far (from my point of view).

@bloodline: I like the Amiga and Mac style. It reminds me of the 80s.

@akasei: Is it all in Assembler?

Greetings
Peter

[CorruptedByCPU]

@akasei: Is it all in Assembler?

101% x86-64

[bloodline]

At @bloodline and @akasei: Both very impressive: The GUI is looking good and the OS seems quite far (from my point of view).

@bloodline: I like the Amiga and Mac style. It reminds me of the 80s.

My OS is a fairly pure ‘80s micro kernel, it has few redeeming features... So hopefully it can at least offer people a little dose of nostalgia if they try it out

[SanderR]

I wrote a small 32bit singletasking monolytic kernel in C. It has FASM ported and the main goal is to be able to read from a USBstick (where it has boot from) . Currently EHCI and XHCI are working fine on the emulators but on hardware it is not 100% OK. I want to create a mixture between MikeOS and PuppyLinux with the easyness of MikeOS and the protability of PuppyLinux

[eekee]

@bloodline: I think theming is easy if you've structured your GUI code well. I know it's a nightmare if you haven't. Almost every GUI I've wanted to modify to suit my eyesight has had some or other foible making it difficult, so I think you've done well there.

@akasei: It's looking as cool as ever! How long has it taken you to reach this point?

@SanderR: That's my kind of retro.

[CorruptedByCPU]

@akasei: It's looking as cool as ever! How long has it taken you to reach this point?

I don't even remember how many times I've rewritten the entire source code The project started on 1st 2013, so ... it's going to be 8 years of slow development. The most time I spent on optimizing and rewriting to the code "perfectly simplified and commented". Now that I have the whole system stable and well laid out (including GUI) ... I can start writing more useful stuff.

[eekee]

@akasei: It's looking as cool as ever! How long has it taken you to reach this point?

I don't even remember how many times I've rewritten the entire source code The project started on 1st 2013, so ... it's going to be 8 years of slow development. The most time I spent on optimizing and rewriting to the code "perfectly simplified and commented". Now that I have the whole system stable and well laid out (including GUI) ... I can start writing more useful stuff.

Ah! Well, a good foundation will no doubt help a lot. I'm not at that stage yet.

[bloodline]

@bloodline: I think theming is easy if you've structured your GUI code well. I know it's a nightmare if you haven't. Almost every GUI I've wanted to modify to suit my eyesight has had some or other foible making it difficult, so I think you've done well there.

Adding theming at this early stage certainly is much easier than if I had tried to add it later

I’m really pleased with the GUI as making a general purpose desktop GUI is one part of the project I have almost no experience with! It’s been a steep learning curve, but also far more intuitive and satisfying than I expected.

[klange]

Happy New Year from Tokyo.

[Korona]

Happy New Year from Tokyo.

In Europe, we still have to nyan a bit longer

[bloodline]

Happy New Year from Tokyo.

In Europe, we still have to nyan a bit longer
[/img]

For the lucky ones who are still in Europe

[BenLunt]

Hi everyone,

It has been a little while since I have been this way. Sometimes my real job gets in the way.

Anyway, after a few posts recently about emulating an x86 instead of using virtual real-mode, I made a few notes and thought that it would be an interesting idea.

After doing a few other things, I took it a bit further and emulated a whole 32-bit (un)real mode machine. (16-bit real mode 80x386 machine. No protection.)



It is 100% emulated. All emulation is written from scratch using C/C++ and compiles and runs at 64-bit or 32-bit.

It still needs a lot of work, but the current emulation is enough to execute the BIOS from Bochs, both the Legacy BIOS and the VGA ROM BIOS, as shown in the screen shot above.

It should be pretty close to turning control over to the first sector of the emulated disk. However, I haven't written the emulated FDC yet, so the interrupt service routine will fail.

Also, looking at the displayed text in the screen shot, since the VGA BIOS is licensed for Bochs, I guess I get to find a different VGA BIOS to use. Either that, or find an older machine and read 32k from 0xC0000.

Anyway, it wasn't as difficult as one might think. My OS already had a disassembler that put the instructions into tokens. All I had to do was call this disassembler to disassemble a line at a time. Then take the tokens and manipulate the emulated system.

It has a somewhat working VGA adapter--obviously, due to the screen's display.

It has a mock-up minimalist DMA controller, keyboard controller, two parallel ports, four serial ports, a non-working PIC (currently mocked-up to use), a non-working PIT (again, simply mocked-up so stuff works), and misc other items.

It needs the PIC emulation written so that I can send keys to the system, the DMA so the floppy will work, and a few other things. The interesting thing is that the system would fail and I didn't know why. After looking over the code, it came down to a simple error in the eflags register emulation. Not setting the Carry flag correctly after a SUB instruction. It happened more than once. :-)

It has been an interesting project though. Also, another interesting thing is that I am using an emulator (QEMU) to emulate my OS which in turn is emulating another x86 machine. :-)

One last thing is that I spotted a bug in my task scheduler that I haven't been able to pin-point where it is yet. The scheduler is modifying the stack approximately 32-bytes above the current stack location. This in-turn modifies a parameter used by the task that got interrupted by the scheduler, so when this task regains control, it sometimes crashing the whole (emulated) system due to a parameter now being destroyed. Something I need to further investigate.

Update: My emulator now runs DOS 5.0a: http://www.fysnet.net/blog/2021/01/

Anyway, Happy New Year to you all,
Ben
- http://www.fysnet.net/fysos.htm