OSDev.org

Of course it's good. I hope that you didn't abandoned PCI support

catnikita255 wrote:Of course it's good. I hope that you didn't abandoned PCI support

Even if he did, it's something that can be done in less than 1 KB source.
Really IMO, PCI support is just a read register and write register function.

I know. I have it too, but I didn't implemented any device drivers except of small RTL8139 driver that can't even receive packets.

Was bored, so I made a screen desaturation routine.

It may not seem impressive but there is some work behind this, it's an interpreter of colorForth language (which isn't very well documented in general), with all language constructs (it's not stable yet).
It runs on the bare metal, later other components will be coded in colorForth. I didn't pushed the corresponding commit because I haven't internet connection at home for the moment.
Here I run a loop which pushes number 3 on the stack 5 times.

That's good that people do such an amazing things.

Yes, I comment almost every post there.

narke wrote: It may not seem impressive but there is some work behind this, it's an interpreter of colorForth language (which isn't very well documented in general), with all language constructs (it's not stable yet).
It runs on the bare metal, later other components will be coded in colorForth. I didn't pushed the corresponding commit because I haven't internet connection at home for the moment.
Here I run a loop which pushes number 3 on the stack 5 times.

Definitely impressive, I can dig it.
Here's a quick screenshot of the barebones kernel I use for component testing running my scheme interpreter. I need to seriously improve the keyboard IO system though.

sad post...

octacone wrote:it is one big failure.

There's always a tomorrow

May I have a question, please?

How many times do you think that " the most engineer in the world " failure before the sucess?

do not give up!!!

keep calm...

try to code day by day... line by line... and ...

Lot of coffee...

Really lots of times. Even me (12-year old child with sh*t instead of lots of things in my OS) failured lots of times. What about the most experienced engineer in the world? Of course he failured more times.

octacone wrote:everything I need (double buffering, transparency, repainting areas) I can't code because I suck. Basic OS is pathetic. We should have a topic called "When your OS sucks". I guess I will have to stick around with my buddy terminal for a WHILE, yeah no multitasking. *cough *cough, no user mode *cough *cough, no system calls *cough *cough, it is one big failure.

Patience, you must have...

octacone, I understand the feeling. I really do, and I'm sorry you're there. But this is what we call learning -- you're not going to be great at everything instantly. And, unfortunately, you're still not going to be great at everything after a year of study. Mastery takes time. But it does happen, slowly but surely.

There's also the important question of what mastery actually is. If you define your goals too wide all at once, you're never going to meet them and you'll never feel like you accomplished anything, even if you've accomplished amazing subtasks that you're not giving yourself credit for. In particular, if you're trying to write an operating system, you're talking about trying to gain mastery in basically every single domain of computer engineering short of actually doing the electrical engineering. All at once. You've given yourself a task that is basically humanly impossible for a single person, given the number of disparate disciplines and man hours that go into even a relatively niche and unpolished group project like Haiku.

So, what I'm saying is that you have to realize the scope you've set yourself and give yourself credit in light of that. You will make progress. You will learn things. You will get better. I started playing around with this junk when I was fifteen, and now here I am, twelve years later, and I'm still even barely off the ground with my project still myself.

You rock. Just the fact that you've been willing to take on such a hardcore hobby -- and very seriously, I might add -- and gotten as far as you have to this point is incredible. I mean, do you have any idea how many people in the world can even just say they've booted custom code on the bare metal of their PC? Just by doing that, you've accomplished something that the vast majority of the public never will.

That's impressive.

octacone, we all as OSdevers have gone through the same feelings you are having. We all have our "aww yeah!" moments and our "I suck" moments. We've all once or twice (many times, really) tried to do something and failed. IMHO, taking up the hobby of OS development and not giving up after "Hello, world!" in itself is an achievement.
jojo beat me to this one; but this is called learning and it's how you teach yourself; by learning from your mistakes.
There are two things you need in this field, patience and persistence.

octacone wrote:Basic OS should be called Pathetic OS!
Basic OS sucks, it will never be good, it will always have broken graphics... I tried to implement double buffering (again) and failed, for the 5th time... I really don't have any hope, everything I need (double buffering, transparency, repainting areas) I can't code because I suck. Basic OS is pathetic. We should have a topic called "When your OS sucks". I guess I will have to stick around with my buddy terminal for a WHILE, yeah no multitasking. *cough *cough, no user mode *cough *cough, no system calls *cough *cough, it is one big failure.

If you want some graphical stuff, check out Surface. I developed it with my second developer for U365, there's drawing functions, transparency and it's just easy to code stuff with it, especially for me

Porting it isn't a problem, the only OS-specific stuff is initalization: you will need to get your framebuffer info and provide it in initialization. Then run init_surface_screen() in your OS initialization routine. After that you can fully use Surface. I attached the archive with the code.