I was thinking about the concept of creating an operating system the other day. Just for fun. I mean, don't get me wrong, I'd love to actually create one (not general-purpose, not for the public, just for me, just a simple, bare-bones, only-needs-to-run-the-programs-I-use OS), but I know damn well I don't have the tenacity and patience. Doesn't mean I can't ponder how I'd go about making one, though.
Anyway, rather than read some sort of "how to make an OS" thing, which I wouldn't understand and which I probably wouldn't like even if I would, I decided to just dream up how I might make an OS from scratch, using nothing but my human-level capacity for rational thought, extrapolation and critical thinking.
One thing I was thinking was, "how does an OS even send data to a monitor so it can display stuff in the first place?"
I came up with a way I'd do it (which, since I'm going off nothing, might be total hogwash, but that's not what this topic is about so I'll keep my dumb ideas to myself) but then I thought, "wait...I really, really
have no idea how OSes actually send image data to monitors."
So I googled, but all I can come up with is stupid general-public crap like this HSW article
and this eHow thing
. I know what an arfing "resolution" is, I know the difference between LCD and CRT, that's not the info I'm looking for. I'm talking about, when those articles mention "the monitor interprets signals from the computer," what are those signals? What is it that the OS is actually doing? Sending RGB values to each pixel?
I have signitures disabled. If you do, too...you can't read this, so nevermind >_>