Question about which tools to use, bugs, the best way to implement a function, etc should go here. Don't forget to see if your question is answered in the wiki first! When in doubt post here.
12 years after I created this post, i'm going to post a new screenshot of my new os going crazy!!
(i started recently a new kernel)
This is related to the issue i posted here: viewtopic.php?f=1&t=42446
But the result when not using the framebuffer is fascinating! And some how very tidy and clean...
This happens after adding a new print statement (after many of them already added above... and working, but for some reason whatever is the content is causing a that **** to happens...)
My original string implementation used a null terminated array of bytes, but now I have switched to using 16 bit characters as I add better support for real C# strings. I guess I didn't properly convert all my VGA text mode string functions properly...
I guess the bitmap font I generated was too big...
Hey! I'm developing two operating systems:
NanoShell --- A 32-bit operating system whose GUI takes inspiration from Windows 9x and early UNIX desktop managers. Boron --- A portable SMP operating system taking inspiration from the design of the Windows NT kernel.
This is an older build of my OS. I was trying to get command-line arguments from GRUB using Multiboot working. I was allocating an array of array of char in order to hold an array of argument strings. I went through the trouble to zero out the array, but I used the wrong number (by a lot) in the for loop, and it ended up running off the end of the stack and zeroing god knows what by like 64k, and it caused this. (EDIT: Oh, and after about 30 seconds it caused a triple fault)
When my monitor tried to help the BIOS copying fonts, but didn't take care of many of the subtleties surrounding REP MOVSB.
The result seems to belong to the nice collection of "broken but not totally random VGA patterns" here. You might even be able to spot the cursor, which was still blinking