OSDev.org

Even after fixing it, I'm still not quite sure why it said "I don't trust it." I think my code has trust issues.

My custom syscall entered in recursion, or something like that.

This is what happens when you incorrectly copy some data.

crosssans wrote:
This is what happens when you incorrectly copy some data.

The classical error

https://imgur.com/a/tI6spO6

My first visual error + cannot figure out how to print he keyboard keys thing

xSlendiX wrote:https://imgur.com/a/tI6spO6

Interesting.

xSlendiX wrote:https://imgur.com/a/tI6spO6

My first visual error + cannot figure out how to print he keyboard keys thing

You forgetted the return carriage escape sequence! ('\r')

hextakatt wrote:

xSlendiX wrote:https://imgur.com/a/tI6spO6

My first visual error + cannot figure out how to print he keyboard keys thing

You forgetted the return carriage escape sequence! ('\r')

I got the keyboard working properly and the print was a bug, made a terminal_scroll function and implemented it wrong. idk how to do it but ok

Keyboard: https://imgur.com/a/MwQU8TQ
It works well, the only problem it the blinking cursor ill fix it later and somehow i creatted this c o o l effect

I posted the full screenshot in the other thread, but it's only upon examination that I spotted this bug:



The screenshot was actually taken on February 28th (so should display "2019-02-28")... I suppose the 0th day of March is kinda the same day as the last day of February, but obviously something isn't working right. The odd thing is that the date values are read directly from the RTC at boot time; maybe QEMU has a bug?

EDIT: Seems to be a bug in my epoch time <-> time and date conversion functions.

xSlendiX wrote:https://imgur.com/a/tI6spO6

My first visual error + cannot figure out how to print he keyboard keys thing

I know that screen well. That's what happens when you dump your 16-bit IVT table at memory location 0x00 to the screen. When you see the 3 horizontal lines and a bunch of 'S' characters, that's a good sign that you've tried printing a NULL pointer to the screen.

It's actually been a while since I've seen that screen, but it does take me back to my earlier OSDev days

Like an old song you haven't heard in a while...

When trying a simple print statement, I managed to get to this screen. How did such a small change fail so horribly.

K3achas: Wild jump which happened to land in BIOS code?

SpyderTL wrote:I know that screen well. That's what happens when you dump your 16-bit IVT table at memory location 0x00 to the screen. When you see the 3 horizontal lines and a bunch of 'S' characters, that's a good sign that you've tried printing a NULL pointer to the screen.

Good to know.

SpyderTL wrote:It's actually been a while since I've seen that screen, but it does take me back to my earlier OSDev days

Like an old song you haven't heard in a while...

Lots of these remind me of my Atari and MS-DOS days.

I was working on my compositor and I got this

Monax wrote:I was working on my compositor and I got this

Keep the code for a screensaver -- xscreensaver did! It looks a lot like like xscreensaver's "decay", but "slip" (slipped blits) is similar too.

Sadly this only a appeared when I moved the mouse, so this would be a quite pointless screensaver