When your OS goes crazy - Screenshots

[finarfin]

We have a post called "What does your OS look like? (Screen Shots..)"

and i thought: "Why don't do a post with screenshots of our OS when it goes crazy?"

When we are coding, and our new pieces of code make our OS to strange things, print unprintable and etc.

I begin with my screenshot (i collect them ):

That happens when i was trying in old version of my OS the task switching (I had the feeling that the OS was laughing at me?, wath do you think? )


That happens when i insert a very very long command (over 260 characters).

If you have screenshot of your Os when it goes crazy i think it would be nice to post them here.

bye ^_^

[LordMage]

Wish I had know this was going to be posted, I had mine spew a few hours ago, I fixed the problem though and didn't think to get a screenie.

[Troy Martin]

This happened when I tried to do 8x8 font in 640x480 VGA mode

[Love4Boobies]

Gee, Troy... I remember getting similar results back in the days of Borland Pascal's graphics unit. Borland compilers came with video drivers for a few popular video cards (except generic ones like VGA). I never knew what the hell caused those red pixels to appear. I thought it had something to do with their implementation; WHY RED? What exactly did you do?

[neon]

I forget what I was doing but I remember one time when I was clearing a region of memory. I watched the system (It was printing some info out). Nothing much new. Then out of nowhere a few seconds later the entire display turned black.

Turns out I was overwriting a buffer somewhere infinitely with the value 0...That could have turned nasty when it reached the end of memory...or even before reaching the end of memory...

[Troy Martin]

What exactly did you do?

Code: Select all

mov ax,0012h    ; Set up 640x480 graphics mode
xor bx,bx
int 10h

mov ax,1112h    ; Use 8x8 font
xor bx,bx
int 10h

[froggey]

This happened after I messed up a memcpy and dumped my kernel's debug info to VGA memory.

[01000101]

ooo pretty. =)

I don't have any shots yet, when I do I'll post.

[xyzzy]

I just went through my screenshots directory and picked up all the screw-ups I could find:


Really old version of my kernel - don't quite remember what happened but it looks like the panic function is causing an exception, causing a recursive panic. Fun!


Quite recently when I was writing my terminal driver - bad memcpy in the scrolling code! I think it had ended up copying part of the kernel onto the VGA memory


When my PNG display application went wrong =)


Font setting fail!

[Combuster]

Font setting fail!

Consider it a novel method of setting leetspeak font

[Firestryke31]

Heh, if you still have the code that did that, you could just for laughs implement some sort of 'mirrored mode.' Plus, if you did that, you'd have most of the code for a RTL language!

[jal]

WHY RED?

The character font resides at plane 2 (EGA, VGA) and 3 (VGA) in text mode (plane 0 = character, plane 1 = attribute). When setting the (text mode) font, the BIOS writes to plane 2. It just so happens that writing to plane 2 encodes for attribute 0100b, which is dark red. I doubt it having anything to do with your BGI problems of yore :).


JAL

[Craze Frog]

When I tried to resume Windows:
The smilies were blinking on and off.

[DeletedAccount]

Thats possibly a hardware issue . Most the time windows crashes due to poorly written third party drivers , Microsoft cannot take the blame for that .

Regards
Shrek

[Craze Frog]

Most the time windows crashes due to poorly written third party drivers , Microsoft cannot take the blame for that.

As if they didn't chose to let the drivers run with maximum privileges...

I've already had three Microsoft HQL certified drivers (one written by Microsoft) on this computer which shouldn't have passed the certification because they blatantly violates the specifications by huge amounts (up to 130 times as long block as maximium allowed). If MS can't take the blame for certifying drivers that don't comply with their own specifications, who can?