noob project

[mmx486]

I'm starting on a new project with no decided name (targeted as a desktop OS) and would like to know what i need to know before i get started. any input on features, concepts, design, architecture, names, etc. would be appreciated.

thanks!

[pjt]

I'm starting on a new project with no decided name (targeted as a desktop OS)

O.K., but please take notice, that some OS names are alrady taken, as my OS is called OS, I'm developing a GUI called GUI, and a very good FS called OSFS. You've been warned.

[pcmattman]

I'm starting on a new project with no decided name (targeted as a desktop OS) and would like to know what i need to know before i get started. any input on features, concepts, design, architecture, names, etc. would be appreciated.

thanks!

You could start by reading (and understanding) the Intel manuals. They're really useful and I deeply regret the fact that I didn't read them first.

Also, read the articles in the Wiki. They're really quite helpful, even if they don't give free code.

There are some great tutorials at osdever.net.

And when you write drivers the hardware datasheets and documentation are the best place to look.

Good luck!

[~]

The code I'm developing right now is calles TestOS/DebugOS, TestFS/DebugFS, because I find that I work better when I forget about the presentation of the code and leave it as it gets to be completed, no matter if it ends up messy but works, or I seem to lose too much time and energy.

I'm looking into new ways of advancing because it looks like far too much effort for twice far too few actual useable/enjoyable/practical results.

[mystran]

And when you write drivers the hardware datasheets and documentation are the best place to look.

Actually I wanna emphasize this: use datasheets if you have one. Try to find one if you don't. Always check everything from the datasheets. Never trust tutorials or other people code without confirming from the datasheets. If you need to trust other people's code (either because datasheet is missing, incomplete, or you think it's not clear enough or even incorrect) only trust well-known code like the drivers from Linux, which actually attempts to deal with all the real-world special cases. You can look at other peoples examples and simple drivers, ofcourse, but confirm their correctness elsewhere if you can, and you can save a lot of time.

edit: Oh and consider the Intel manuals to be the datasheets for the first device you are going to deal with: the processor.