Page 53 of 55
Re: When your OS goes crazy - Screenshots
Posted: Sun Apr 04, 2021 6:01 am
by finarfin
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...)
Re: When your OS goes crazy - Screenshots
Posted: Sat May 08, 2021 9:09 pm
by JohnpaulTH
Something went wrong implementing Carriage return.
Code: Select all
push rax
push rcx
push rdx
mov rax, rdi
sub rax, TEXTBUF_BASE
mov rcx, 80
div rcx
sub rdi, rdx
pop rdx
pop rcx
pop rax
adding 'xor rdx,rdx' after the pushes solved the problem.
I will have to look at my previous implementation
Re: When your OS goes crazy - Screenshots
Posted: Mon Jul 12, 2021 2:22 am
by valdect
Nice, patterns...
Re: When your OS goes crazy - Screenshots
Posted: Thu Jul 22, 2021 10:48 pm
by leap123
Re: When your OS goes crazy - Screenshots
Posted: Sat Jul 31, 2021 5:20 am
by trashoperatingsys
I forgot to increment the offset register twice in the video memory and ended setting the color attribute to a character.
Re: When your OS goes crazy - Screenshots
Posted: Wed Oct 27, 2021 3:03 am
by 0Nera
Try create kheap...
Re: When your OS goes crazy - Screenshots
Posted: Sat Jan 08, 2022 11:36 pm
by giawa
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...
Re: When your OS goes crazy - Screenshots
Posted: Tue Feb 08, 2022 2:39 pm
by iProgramInCpp
I guess the bitmap font I generated was too big...
Re: When your OS goes crazy - Screenshots
Posted: Tue Mar 29, 2022 7:32 pm
by pvc
Adding memory regions to perfectly working physical memory manager. I wonder where such uniformly random data even came from.
Re: When your OS goes crazy - Screenshots
Posted: Tue May 24, 2022 2:58 am
by davmac314
I forgot to intiialise the attribute buffer apparently
Edit: problem was actually a wrong calculation for character (and attribute) position in the scroll routine.
Re: When your OS goes crazy - Screenshots
Posted: Fri Jun 10, 2022 12:32 am
by Techflash
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)
Re: When your OS goes crazy - Screenshots
Posted: Tue Jul 05, 2022 1:28 pm
by RayanMargham
Divide Error!
Re: When your OS goes crazy - Screenshots
Posted: Fri Jul 22, 2022 11:55 pm
by one737
This is a screenshot from my ancient project.
Re: When your OS goes crazy - Screenshots
Posted: Sat Jul 30, 2022 6:39 am
by oli2
When you mess up your multiboot header
Re: When your OS goes crazy - Screenshots
Posted: Mon Aug 01, 2022 8:42 pm
by xeyes
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
