Troy Martin wrote:You can also get 80x30 in real mode fairly easy by activating 640x480 graphics mode and adding a "mov bl,07h" statement before every usage of int 10h ah=0Eh. Haven't tried activating 8x8 in graphics mode though!
Using graphics mode for text would kinda defeat the purpose. Terribly slow.
The text mode cursor gets disabled as well so you'd need to use an underscore or some other character to show the cursor.
Oh, and don't try doing 80x60, it does weird things with the graphics in Virtual PC and Bochs, so I'm guessing it's possible it could damage a CRT monitor.
Solar wrote:It keeps stunning me how friendly we - as a community - are towards people who start programming "their first OS" who don't even have a solid understanding of pointers, their compiler, or how a OS is structured.
That's not what I meant. Besides, QEMU can cause no harm; it uses the OS host OS' services to draw to the screen, it doesn't have access to I/O ports, etc. What I meant was that the screen doesn't get updated properly and it looks funny.
"Computers in the future may weigh no more than 1.5 tons.", Popular Mechanics (1949)
[ Project UDI ]
When I said "damage a CRT monitor" I meant on RHW only, not virtualized, just RHW. And probably on an older monitor too.
Solar wrote:It keeps stunning me how friendly we - as a community - are towards people who start programming "their first OS" who don't even have a solid understanding of pointers, their compiler, or how a OS is structured.
