OSDev.org

Nice one, Kevin Lange!
It seems pretty nice that your OS is advancing.

lust

I'm not sure that you understand what this word means.

Roman wrote:

lust

I'm not sure that you understand what this word means.

What's wrong with that? He's got his thing for toaruos, but I'm more of a Sortix guy.

Roman wrote:

lust

I'm not sure that you understand what this word means.

lol

Code: Print a red z on 0xB800.
Hardware: mkay here's the final result of that




I know why it happened, some apparently intelligent person thought B800 was correct and i thought it didn't matter since i tho-

oh, i dumped stuff into ROM

NunoLava1998 wrote:Code: Print a red z on 0xB800.
Hardware: mkay here's the final result of that

When I open the overclock settings in my BIOS this happens to my desktop.

zenzizenzicube wrote:

NunoLava1998 wrote:Code: Print a red z on 0xB800.
Hardware: mkay here's the final result of that

When I open the overclock settings in my BIOS this happens to my desktop.

When i opened the overclock settings in my (OLDER) BIOS after overclocking, well, after a few megahertz, you had to:
turn off, turn on, turn off, turn on, turn off, turn on, turn off, turn on, set your normal BIOS settings and then you can continue

NunoLava1998 wrote:Code: Print a red z on 0xB800.
Hardware: mkay here's the final result of that




I know why it happened, some apparently intelligent person thought B800 was correct and i thought it didn't matter since i tho-

oh, i dumped stuff into ROM

When I started linking my real mode code with watcom, Instead of incrementing the pointer in the print method, I was incrementing the the character in the first character of the string. My computer learned the ASCIIbc's and beeped along to it endlessly.

Working my way through bare bones, trying to get terminal scrolling working. Almost there.

Did i put too many newlines?

Trying to implement scrolling and failing kind of (it works until you scroll more than 2 lines)
My code is completely written in x86 real mode but i'm compiling gcc atm so i can move on to proper real mode coding.
@NunoLava
i've run across that issue too:
1. the o with white background is printed when you try to print 0x0a (newline)
2. the cursor needs to be moved separately and it is at that very position because it is left there after the bios message

My OS decided that it wanted to create abstract art.

Twinkle twinkle little stars, I can't get scrolling to work.
Up above the screen so high, why the hell am I doing this?
Twinkle twinkle little stars, how you litter all over my screen.

TheCool1Kevin wrote:Twinkle twinkle little stars, I can't get scrolling to work.
Up above the screen so high, why the hell am I doing this?
Twinkle twinkle little stars, how you litter all over my screen.

Your width and height changed places or something?

Judging by the flipping, I think the X and Y axes got swapped in the calculation.