JPEG is less complicated than PNG, I think, just requires a bit of math. I have a little JPEG decoder in ToaruOS.BenLunt wrote:I guess .jpeg would be next, but this image format is a bit more complicated.
- http://www.fysnet.net/osdesign_book_series.htm
What does your OS look like? (Screen Shots..)
Re: What does your OS look like? (Screen Shots..)
Re: What does your OS look like? (Screen Shots..)
I thought PNG was fairly easy once I got the documentation figured out. I will have another look at JPEG and visit your decoder to see how you do it.klange wrote:JPEG is less complicated than PNG, I think, just requires a bit of math. I have a little JPEG decoder in ToaruOS.BenLunt wrote:I guess .jpeg would be next, but this image format is a bit more complicated.
- http://www.fysnet.net/osdesign_book_series.htm
Thanks,
Ben
Re: What does your OS look like? (Screen Shots..)
As a side note, I did not want to use ZLIB in my project so I decided to write my own tools that use Deflate. I don't have the decoder at this point but I have a tool that can produce ZIP files. The encoder is embarrassingly naive but I was very surprised that the compression ratio is not that bad. For example, I packed all the source code files that I have in the project and compared it to a Linux "zip" (with -9 option):BenLunt wrote:so I decided to implement .PNG images, which now must include a ZLIB decoder
Code: Select all
My zip: 176 KiB (roughly)
Linux zip: 146 KiB (roughly)
Re: What does your OS look like? (Screen Shots..)
Just-about...! I thought you'd ported Armagetron for a moment. Good game! As for me,BenLunt wrote:Can you tell I am a TRON fan...
I'd say there's at least an 80% chance my OS GUIs will end up with a lot of black surfaces and glowing neon lines.
Kaph — a modular OS intended to be easy and fun to administer and code for.
"May wisdom, fun, and the greater good shine forth in all your work." — Leo Brodie
"May wisdom, fun, and the greater good shine forth in all your work." — Leo Brodie
Re: What does your OS look like? (Screen Shots..)
It has console. It has calculator and clock. But what's most important…
It runs DOOM!
It runs DOOM!
Re: What does your OS look like? (Screen Shots..)
Another windowing system implemented in-kernel... tsk tsk!pvc wrote:It has console. It has calculator and clock. But what's most important…
It runs DOOM!
But seriously, congrats on the Doom port!
This video is a year old, got anything new?mariuszp wrote:https://www.youtube.com/watch?v=bOKfypG7MRQ
Re: What does your OS look like? (Screen Shots..)
My suggestion is to use OBS to screen-cap VirtualBox or QEMU - that's how I do all my videos these days. I found VirtualBox's integrated video recording to have weird stutter issues.mariuszp wrote:Yes, I tried recording something knew but VirtualBox refused to let me. I'll try again later.
Re: What does your OS look like? (Screen Shots..)
- Attachments
-
- label-centralized.png (7.7 KiB) Viewed 6307 times
Re: What does your OS look like? (Screen Shots..)
"I ain't afraid of no quake".
Re: What does your OS look like? (Screen Shots..)
Wait, you got Quake to run?! If the Github page is accurate, you started in September last year. I'd say that this is really impressive, if that's the case.pvc wrote:"I ain't afraid of no quake".
Re: What does your OS look like? (Screen Shots..)
I've ported SDL 1.2 (video, events, threads and partially timers and audio). Since quite a lot of games use SDL, porting them requires just some minor tweaks.
Re: What does your OS look like? (Screen Shots..)
Your next step should be to port Bochs, so you can run your OS in your OS.pvc wrote: I've ported SDL 1.2 (video, events, threads and partially timers and audio). Since quite a lot of games use SDL, porting them requires just some minor tweaks.
Re: What does your OS look like? (Screen Shots..)
Haha… What have you done?! OSception? Good job!
That would be funny if I could do that as well. But not happening right now. I still have some issues with writing on ext2 (which is the only writeable filesystem on my OS for now).
And I thought about actually trying DOSBox. But first BusyBox, YASM and GCC (binutils are already done).
That would be funny if I could do that as well. But not happening right now. I still have some issues with writing on ext2 (which is the only writeable filesystem on my OS for now).
And I thought about actually trying DOSBox. But first BusyBox, YASM and GCC (binutils are already done).
Re: What does your OS look like? (Screen Shots..)
Yes. It’s typically just OBS in conversation, there’s nothing really special about Studio over the previous version. It’s the gold standard in desktop recording and streaming these days.mariuszp wrote:What is OBS? Are you referring to "OBS studio"? Trying to find it, but can't.
Re: What does your OS look like? (Screen Shots..)
After taking a 5 month break I decided to pick quack back up. I have started moving it to a microkernel architecture, and so far I've got:
In this picture the "hello world, this is quack" text was typed in via the PS/2 keyboard, and the one lone character at the bottom is the least significant byte of the global system tick counter, which processes can nicely ask the kernel to map into their address space as read-only. All I really need to do now is to actually focus on the userspace side of the OS, since the kernel has almost everything I need(apart from waiting for multiple kinds of events, like waiting for either an IPC message or an IRQ).
- New and improved scheduling and task management code
- A simple exec server that can start new programs from ELF files passed to it via an IPC message
- A way for processes to handle device interrupts(process sleeps until the interrupt arrives, kernel wakes the process up)
- A test program that handles PS/2 keyboard interrupts and simply prints characters to the screen
- Other stuff too small to mention individually
In this picture the "hello world, this is quack" text was typed in via the PS/2 keyboard, and the one lone character at the bottom is the least significant byte of the global system tick counter, which processes can nicely ask the kernel to map into their address space as read-only. All I really need to do now is to actually focus on the userspace side of the OS, since the kernel has almost everything I need(apart from waiting for multiple kinds of events, like waiting for either an IPC message or an IRQ).
Working on managarm.