[smart_ritu]

want to know about stepwise description for
how to make my own opeating system in C++

[Louisda16th]

I don't know anything about making OSes but I believe that the description on doing so can go on for pages...
There is a thread that discusses OSes. Hope this helps:
http://www.dreaminco...wtopic20520.htm

[Elcric]

Hello,

This might give you some ideas.

http://www.planet-so...p...18&lngWId=3

Good luck and keep us posted on your progress.

[NickDMax]

You will ultimately need assembly as well as C/C++ (well if you are not starting form a pre-made kernel). Much to my chagrin I discovered that library functions like printf, malloc etc tend to use OS dependent mechanisms.

So step 1 for writing a OS in C++ is to get the C++ libraries ported over to your non-existent OS. But you can find the C libraries written in assembly out there and use them a jumping off point.

[RudiVisser]

When I wrote my kernel and std C/C++ library implementation I didn't use any straight ASM.

It was GCC configured not to link in *any* standard libraries, no headers is bliss. You just completely make your own stuff and it's absolutely brilliant, but no, you don't need assembly strictly.

EDIT: At least not a complete understanding of starting from scratch, inline assembly will have to be used (especially for interrupts etc) but the majority will be C/C++.

This post has been edited by MageUK: 06 August 2009 - 01:50 PM

[NickDMax]

I suppose that you are correct on a technical point... I find that many of the lowlevel operations are easier to do in assembly -- but I suppose that there is no reason why you can't use c++ as long you don't use any of the libraries.

[jeff666]

Simply posting this question shows that you should make pizzas instead.
(you don't know what is an Os, you don't know C++, you don't know Google...)

This post has been edited by jeff666: 08 August 2009 - 02:18 AM