bl00dninja

jumping into programming wanting to make an OS is like trying to rebuild your car's engine only knowing how to put gas into it. try learning how to change the oil first, and we'll go from there.

__________________
i put on my robe and wizard hat...

Have you ever heard of Plato, Aristotle, Socrates?...Morons.

frankish

Well, it's just like Windows 95 or Windows 3.1. DOS would boot those systems.

DaWei

DOS is not MS-DOS. Your terminology sucks rocks. MS-DOS was an OS (albeit a poor one, not reentrant). An OS has, among other things, an executive and a user interface. The core of the executive was command.com. It had a number of internal commands. If a command did not match an internal command, it had the ability to search the path for an executable file with a name matching that of the command. Executable files were .com, .bat (shell, but poor), and later, .exe. The user interface was text-based (what you would now call "console").

When Windows was introduced it was just a graphical user interface running under MS-DOS; again, it was a poor one. With the introduction of Windows 95 the first step was made to divorce the executive from MS-DOS. With Windows 98 the divorce was essentially final. MS-DOS, more specifically, command.com and cmd.exe, became tools of the executive, and not the core of the executive. The majority of the booting of the system involves the loading of drivers, the configuration, and other necessary features. This process is NOT conducted by MS-DOS. The user-interface is intended to be primarily GUI. The "console" interface became just a text window running as part of the GUI. "Booting into DOS" with a working Windows installation is essentially booting into a single text window with no additional windows, and without the desktop, which is really just a separate full-screen window. True booting into what you call "DOS" actually happens if one boots into the Recovery Console. It just isn't MS-DOS.

__________________
Abstraction doesn't make it impossible to write bad code; it makes it possible to write superior code.
Contributor's Corner: Grumpy on C++ Exceptions DaWei on Pointers

zorin

Why does everyone want to code an OS, and whose going to use it (apart from themselvs) there are so many good ones out there already. Theres been loads of posts about coding an OS and half of them dont have a clue about where to start

mikaoj

I'm going to write an OS, not to use it, but to learn more programming, and get more understanding of it.

__________________
Heh.

Mjordan2nd

I would say for the purpose of learning, and entertainment. I actually want to write an OS also, for myself, and anyone who wants it. I don't expect it to be used, I just want to write it to learn. I know that I'm eons away from being able to write an actual OS, though, so while I'll keep studying, I doubt I'll do anything about that ambition for a while.

__________________
"Every gun that is made, every warship launched, every rocket signifies, in the final sense, a theft from those who hunger and are not fed, from those who are cold and are not clothed. The world in arms is not spending money alone. It is spending the sweat of its laborers, the genius of its scientists, the hopes of its children." - Dwight D. Eisenhower

big_k105

I'm Guessing that people want to code an OS to learn like Mjordan2nd stated. I mean why else do colleges (atleast around here) make the CS Students take an Operating Systems Class where they actually work on writing a basic OS. Alot of the reason I wanted to was to learn more about how an OS actually works. I still have alot of studing to do before I would ever attempt it. And then some people think they can jump into the OS wars and create a great OS that will be the future. Someday the main OS everyone is using will probably have been created in some kids basement.

__________________
BIG K aka Kyle
Programming Forums
Kyle K Online

Please do not PM or email me programming questions. Post them in the forums instead.

D-Ferg27

kid = (me + 10 years)

bigguy

Yes, Datalisk a OS would take a long time. DirectX is for windows, just like VB is for windows. If im not mistaken you would have to have some ok the windows kernel, to work with the DirectX, so this is a bad idea. I would suggest just messing around with some Linux source code, and leanr there, and than take on building a small Os, not one that supports games, and is portable.

__________________
Forgiveness is the fragrance that the violet sheds on the heal that has crushed it. - Mark Twain

We all make mistakes. If it doesn't kill us, it will make us stronger. If it does kill us, then it's to late, but it was a great ride while it lasted. - Seth Hall