OSDev.org

Have you even tried?

Troy Martin wrote:Have you even tried?

oops!
Joke, I tryed.
I'm now trying to instal another version of it.

Rather then choosing different kinds of development tool chains, pick one (preferably one that you have the most experience with) and use that. GCC, DJGPP, Cygwin, MSVC, C::B, et al... there are alot of tutorials on setting up each of these.

It looks like you write code in C# and then it translates into assembly that is assembled by NASM and linked into flat binary.

neon wrote:Rather then choosing different kinds of development tool chains, pick one (preferably one that you have the most experience with) and use that. GCC, DJGPP, Cygwin, MSVC, C::B, et al... there are alot of tutorials on setting up each of these.

You're right. This whole topic isn't much of a good idea fountain.

Troy Martin wrote:It looks like you write code in C# and then it translates into assembly that is assembled by NASM and linked into flat binary.

...and autostart and configurate a emulator, makes an image to burn it to a CD or DVD or makes it ready to boot it from USB.

Axalto wrote: ...and autostart and configurate a emulator, makes an image to burn it to a CD or DVD or makes it ready to boot it from USB.

Nope. Do that and you will lose tons of CD/DVD. Only make an image.

I really wouldn't recommend getting started with an OS written in a managed language like C#. Don't think I'm bashing the OS, because I'm not - its a truly excellent idea.

However, I'm fairly certain that you won't know the half of what's going on with it - a lot of stuff gets done behind the scenes in one of these operating systems, and so I would recommend starting with something a little smaller, and written more close-to-the-bone (In a language like C, or even asm) to see exactly what is happening.

Once you understand that, then you can move on to understanding OSes like cosmos and singularity.

JamesM wrote:I really wouldn't recommend getting started with an OS written in a managed language like C#. Don't think I'm bashing the OS, because I'm not - its a truly excellent idea.

However, I'm fairly certain that you won't know the half of what's going on with it - a lot of stuff gets done behind the scenes in one of these operating systems, and so I would recommend starting with something a little smaller, and written more close-to-the-bone (In a language like C, or even asm) to see exactly what is happening.

Once you understand that, then you can move on to understanding OSes like cosmos and singularity.

I know, but this user-kit is the only working compiler/linker/emulator I've ever found. I hate this stupid linker!

Oh, and I already understand all the teoratical stuff.

NASM + GCC + LD works extremely well, you just need to know how to use it, and that's documented in our wiki. Search it and you will have yourself a booting OS you wrote in under twenty minutes, ten if you just use NASM.

I followed every step and it still didn't worked.

You followed every step of what? And what about it didn't work?

Every step of the Bare bones c tutorial.
The linker keeps saying:
"loader.o(.text+0x14): In function 'loader':
: undefined reference to `kmain'"
So, what have I done wrong?
[edit]YAY! I've found a solution!
I used a hex-editor to analize the kernel.o file and my compiler had put _kmain instead of kmain in the output file.
So I changed "global kmain" and "call kmain" to "global _kmain" and "call _kmain".
I only need to try it.[edit]

[edit2]AARCH! It dousn't work!
I finally get the good file (kernal.bin) but I can't get it on a floppy/cd/qemu/bochs.[edit2]

Axalto wrote:[edit2]AARCH! It dousn't work!
I finally get the good file (kernal.bin) but I can't get it on a floppy/cd/qemu/bochs.[edit2]

Once again, DO YOUR HOMEWORK BEFORE ASKING