Hello
Unfortunately, today there is no point in writing OS,
despite all the efforts, you always find in front of the same problem suffered by all Hobby OS, the driver.
Everyday I try a different hobby OS, but nobody supports driver for my Hardware,
will have more meaning to write an OS when there will be universal drivers interface ,not only for Win / Linux,
or when all manufacturers release hardware documentation

driver is not a problem, the main problem is to have a good os. tht can work as easy as win, lin or macos.

there is the problem, code an OS that permit to launch applications, have the total control of all processes, and then, have drivers for all hardware.

what is your configuration dj?

Do you have solve the problem?
Good ,please let me known,so I'll start to write a OS

USB Wireless Network,
VIA Chipset,
Creative 10k1 processor Audio chipset,
nVidia graphic Card,
Note that also if you solve my configuration,you must solve other 100 more
configuration.
You can thing to use Vesa for graphic card,but the people that buy 200 euro graphic card want 2d 3d accelleration .not simply set vesa mode and go....

yep, but about 2D and 3D acceleration, it is specific, for this, we need first an OS that works, and then, build a sort of openGL for that os.
it's not impossible, but need so many work, that it will be made only if constructors share their documents.

first, builmd a good os.
second, public is falling in love for this, and then, constructor will write drivers.

I think this may change, as more and more Co are releasing there full spec.
Eg: http://www.phoronix.com/scan.php?page=article&item=amd_tcore_release&num=1
and here's the doc's
http://ati.amd.com/developer/open_gpu_documentation.html

The problem with most hobby OS, is a good driver interface, where you can load and unload driver's on the fly, most do not have any interface, but need a re-compile etc.

Also too many coder's think in terms of a desktop OS, this is a multi purpose OS, more coder's need to think of a single purpose OS.
Eg: I am using my OS, to run a CNC mill, reading G-code.

You may said, but these are not for my spec, that's right, but maybe you should only buy from Co that release there spec .

A Os is not good without drivers since drivers is what makes it to be a OS.
Public will not falling in love for a OS without drivers and constructors will not write drivers for it.
Also having documents for the hardware is not enought ,because one programmer is unable to write all the required drivers.
The hardware must be documented and standard ,like cpu,vesa graphics,hardisk... and some manufacturers now start to understand this
is also better for them.

the time is changing, it's true, constructors give they spec now.

and as stated dex, the drivers are not problem, but the driver interface, it is.
it is very important to be able to load and unload drivers on the fly, and the more important, is to save the stability, and avoid the restart reflex of re-window$.

drivers need 2 layers:
the direct hard ware.
the lib connection.

and then, a lib need, to be evolutive, with possibility of connect, deconnect, a function index list instead of direct function access.

then, to call a function



or something like this.

Hi
I guess the tendency of Intel and AMD for the future,
and will be having pc Intel / AMD compatible, where everything will be labelled Intel or AMD / ATI.
So the most logical solution seems to me to write an OS Intel / AMD compatible, as was IBM compatible PC in '80

There's no point in making an OS unless it's some how better than all the other OSes...so what are we aiming for speed? security?

What if we converted Windows or Linux drivers into the OSes's file format or what if the OS supported drivers written for other OSes

i have a little idea, we can define not an OS spec, but a driver spec, that is OS independant.
like a video card driver that will only provide a set of pointers and structures, relativelly easy to use, to control the screen as a simple array, a linear memory place, including hardware acceleration, th esame for 3D, something that can understand any 3D file structure, and then, execute the driver routine...
it shall be at least a pseudo BIOS sheme, like aeBIOS.

We aim for suitability. Not every system requirement will fall neatly into the existing OS parameters, we have to make trade-offs to make things work. So if your system has a particular requirement, it can in many cases make sense to have a customised OS. I deal with systems where a general OS like Windows or LINUX would not make any sense to use. I write custom OSes specifically designed to meet particular requirements.