OSDev.org

Although I don't think the answers you got were particularly reasonable (WHY ALL THE SHOUTING?), you'd get a lot more respect if you actually followed the advice people are giving you about the learning process. They're not just empty words, you know. You're not the first one to think he's clever, ignore them, and think the easy way out will work just fine if you just figure out a few more technical details---it's actually not right around the corner at all. And you won't be the last to think it either. So far, you're setting yourself up for failure in a big way but don't know enough to see it and the rest of the forum is watching it happen. It's up to you to change that.

Yes. You need to do a bit of research yourself though.
I don't think people mind helping you, but sometimes you need to help yourself.

It's a two-way street; to be treated as a normal user first you have to act like a normal user. A normal user does not post over and over about every line of code they are trying to write. A normal user does not expect others to do all the work for them and to baby-sit them through the basics of processor operation. A normal user does a bit of research first. A normal user pays some heed to the advice they are given.

No-one can give you a nice answer to your question because no-one, you least of all, know what you are really asking. You have such a lack of understanding - and an inability, it seems, to learn - of what is involved that you really don't know what you are asking for.

Example - you are testing your IDT by doing an interrupt 0. And it fails; of course it does. You haven't defined an interrupt routine to handle this interrupt and you haven't made an entry in the IDT for it. So a triple fault is the only possible result (as you don't have handlers for GPF and PF exceptions either).

You are not ready for OS development yet; you need to understand better what it is that you are trying to do.

Okay, first of all: Forget about the IDT for now, get a working GDT first. Once that works, the IDT shouldn't be too hard because its structure is similar. The way to check whether your GDT is valid is to reload the segment registers.

The other thing is: How did you implement a "big part of my IDT/GDT" without knowing what GDT entries are? The GDT is literally just an array of GDT entries, so without entries you shouldn't have anything. Each GDT entry is a 64 bit integer, whose meaning is described in the wiki article.

Next step: Now you try and figure out how many entries you need in your GDT and which numbers to put there. Then tell us those numbers and we'll check them. Don't come back before you haven't made at least an attempt at them. The wiki describes everything you need, and checking the Intel manual can't hurt either.

I'm not so sure about that. I don't think that the OP realizes that he has to write interrupt routines for the interrupt descriptors to point to. In reality it seems pretty clear that he only understands interrupts as software interrupts (and even then doesn't seem to know that he needs a handler for the descriptor to point to). Exceptions and hardware interrupts are still unknowns; unfortunately they are not "things that we know that we don't know".

Well, possibly. Anyway, one problem at a time. And without a GDT, you can't get a working IDT, so GDT is first.

Yeah, i really had no idea what i was doing.
I'm now loading the GDT/IDT properly.

I just look at this thread and say "was I really that stupid so little ago?".

And you still are! Imagine that.