In article <457C868C.6027.71D173@twegner.swbell.net>, "Tim Wegner" <twegner@swbell.net> writes:

My joke at work is if it compiles you are done :-)

Heh heh, well with some of my changes that actually is true. However, I'm testing as I go with a half-implemented driver, so its no surprise that things are still a bit wonky. At my current employer I was introduced to two new phrases "PEBCAK" and "ID10T problem". The latter is pronounced "eye-dee-ten-tee problem" and the former is an acronym for "problem exists between chair and keyboard". :-) While I got things scrolling, the attributes were a bit wonky and I've fixed that and updated the screen shot on the blog. Just in case anyone was wondering why the colors were off :-). I'm stealing the WinText.c code from WinFract and reusing it as much as possible. I think it has some bugs in it though...more likely I'm just misunderstanding it and using it wrong. I'm starting to get more of a feel for which parts of the driver are "Win32" (timers, files, directories, sleep delays, message pumping, getting input) and which parts are "GDI" (drawing text, drawing pixels). Ultimately this will be factored out into a "platform" portion (stuff that is common between all Win32 drivers, for instance) and an "output" portion (just the graphics/text rendering). This will happen when I finish the Win32 disk driver and add the Win32 GDI driver. They'll share the common platform stuff. -- "The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download <http://www.xmission.com/~legalize/book/download/index.html> Legalize Adulthood! <http://blogs.xmission.com/legalize/>