OSDev.org

Right now i only wrote a kind of splash screen. Pretty pointless, but at least the i/o and timers work


As for todays work: setting graphics modes without v8086


[edit]I cleaned up my own screenshots page and broke some links doing that - now fixed[/edit]

PortixOS ...a unfinished OS (in CLI); almost all fns are in develing (for example, time is totally wrong, it should be 16:27 (4:27 PM :D )
OS is in Slovak Language; my English suxx

dev'ed in Borland pascal

Here is a bit of an old one

Here is one of smiddyOS:

Enjoy!

Here is one of BlueIllusionOS - window composer working solala.



Have fun.

distant voices: Thats a really cool OS, you have.

x86, 16-bit, coded in assembler. Some very basic DOS compatibility too

Mike

heres JouleOS with consoles and stuff... don't have multitasking implemented yet(it works but isnt in the consoles yet)
also a bit of colors..(pretty huh?) lol yea pretty cheap but anyway..

SolarOS

http://www.oby.ro/os/index.html

looks like this

what does "optimize on/off" do and what does "cool down" do?... it makes me curious

It's probably a CPU specifc feature or puts the OS in an idle state or w/e

The optimize thing could have something to do with memory usage?

The Optimize On/Off checkbox is about "dirty lines optimization". The screen redraw will target ALL lines without it and only "dirty" lines when it is active. It is an early/naive atempt to reduce the CPU utilization if the screen is static. real dirty rectangles should be used ... but that will complicate the code too much (for now).

The TK2 and CoolDown are somehow releated to puting the CPU into idle for a while after each OS loop. Solar is a realtime OS so it has a loop and a frames per seccond.

This way unless a new IRQ or Event arrives the CPU gets cooler. This is somehow needed for laptops or overclocked CPU's. Activate it and you will hear the CPU fans slow down after a while. Sometimes it works in Virtual PC also.

It is named the "same" as TM2 (Thermal Monitoring 2) that is available in some CPU hardware ... however TK2 is an purely software solution.

"Cool down" is adaptative in a sense that it will keep the CPU at high usage for a while after some actions have been done (expecting more user or applications activity) and adds iddle only ofter a certain time of non-activity has passed.

TK2 will add iddle each time but it will exit immediately if an IRQ or Event occurs allowing fast response. Activated together they do "cool" the CPU more...

how would you make it cool down though... like does hlt not use any cpu because I know that a for(;;){} loop does so how would you make it cool down with irqs and everything also?

Yes, HLT Opcode does tell the CPU that it can "take a break" and unless an IRQ does come (for a task switch or for an hardware device ISR) --> then the CPU will cool down ...
Besides modern CPU's do have "speed steep" and other thermal monitoring and power management commands that can be used to cool down the CPU while in idle state...

But I guess this thread is for screenshots ...

Here's a bootup shot of an early version of ndk. It's got an ascii art plasma animation running in a separate thread while the bootup process continues in the main thread.



I think it looks cool, at least

--Jeff