- I want a OS source code, easy to understand (C is not easy), maybe develop in Pascal, or other easy language.
- Or a good beginner tutorial.
- I programing in DOS, but I see souce code of Pmode OS and I dont see instruccion like SETINTVEC or GETINTVEC. How is the form to the kernel comunicate to device drivers.
Thanks
OS beginner
RE:OS beginner
Uhm... there aren't many OSs designed today that aren't written in C, and even few that are written in pascal. I know of _one_, which you might be interested in:
http://www.thegaineys.fsnet.co.uk/
There are many tutorial links on this page (check the "links" and "osDev ring" links up above).
And, lastly, setintvec and getintvec are functions provided by the compiler and rely on the operating system in use under the compiler. In your case, for instance, both functions are designed to run under DOS... so how do you plan on using these functions in your own "non-DOS" operating system? The short answer is, you can't... not unless you're writting a real mode operating system with a static IDT located at 0x0.
In other words, you'd have to write those functions yourself. Most functions provided by your compiler and standard run-time libraries cannot be used when developing a new OS.
Jeff
http://www.thegaineys.fsnet.co.uk/
There are many tutorial links on this page (check the "links" and "osDev ring" links up above).
And, lastly, setintvec and getintvec are functions provided by the compiler and rely on the operating system in use under the compiler. In your case, for instance, both functions are designed to run under DOS... so how do you plan on using these functions in your own "non-DOS" operating system? The short answer is, you can't... not unless you're writting a real mode operating system with a static IDT located at 0x0.
In other words, you'd have to write those functions yourself. Most functions provided by your compiler and standard run-time libraries cannot be used when developing a new OS.
Jeff
RE:OS beginner
I suggest looking at the linux 0.01 source code. This is before the bloat - he nLinux maintained the code - and it was ppossible for 1 person to read the ****.