StarDestroyer.Net BBS

Try figuring out what went wrong here

http://img86.exs.cx/my.php?loc=img86&im ... god7ln.jpg

He changed color settings while playing GTA?

That's up there with that other old favourite; "an error has ocurred".

I work in electrical retail, and our computer system has a section for recording details of returned faulty items. One of the fault description categories is "unexpected fault". As opposed to those faults you fully expect to occur when you buy the thing, I suppose.

He's running a trainer.

Anyway, I love the error. It's almost as amusing as the errors from the early days of the Steam v2 beta, such as NotEnoughChildren and the one about blobs.

EDIT: Clarification about Steam.. that program, with the Valve, and the Half-Life, and such.

I prefer "flagrant system error."

Mitth`raw`nuruodo wrote:He's running a trainer.

A GTA3 trainer? Never heard of it.

I work in electrical retail, and our computer system has a section for recording details of returned faulty items. One of the fault description categories is "unexpected fault". As opposed to those faults you fully expect to occur when you buy the thing, I suppose.

Here's one I got: http://yt300000.250free.com/hahas.jpg

Yeah, that's me on the desktop.

Not as bad as a kernel panic *shudder*.

darthdavid wrote:Not as bad as a kernel panic *shudder*.

A what?!

Ace Pace wrote:

darthdavid wrote:Not as bad as a kernel panic *shudder*.

A what?!

You've never used a UNIX based OS, have you...

You shoulda seen what happened when I dropped my PowerBook and knocked the wireless card out of its socket...

Praxis wrote:

Ace Pace wrote:

darthdavid wrote:Not as bad as a kernel panic *shudder*.

A what?!

You've never used a UNIX based OS, have you...


You shoulda seen what happened when I dropped my PowerBook and knocked the wireless card out of its socket...

I installed NVidia's drivers of YOU into Suse back when I was running that and a Gforce 4 in this box. Somehow it borked up and caused a kernel panic...

The scariest error meassage I ever got was "Not enough"
I clsoed a few programs and eventually got the updated error message "not enough mem"
I believe the computer was trying to say "not enough memory", but was unable to get it all out.

"No Keyboard found.
Press F1 to continue."

"Error- there is no error message for this error." Spontaneous crash gave me that helpful hint on what went wrong.

Praxis wrote:
You've never used a UNIX based OS, have you...

You shoulda seen what happened when I dropped my PowerBook and knocked the wireless card out of its socket...

Nope, so can you explain?

A kenel panic is what happen when Unix completely tosses it's cookies, it usually happens because the protected memory area for the kernel gets fucked with (windows will produce a similar error with depressing frequency)

It's actually quite hard to make it happen, but you can get if from things like badly written device drivers (or deleting your system folder, that's a good way to make it happen).

Dahak wrote:"No Keyboard found.
Press F1 to continue."

I've gotten that, but I thought it was F8

Vendetta wrote:A kenel panic is what happen when Unix completely tosses it's cookies, it usually happens because the protected memory area for the kernel gets fucked with (windows will produce a similar error with depressing frequency)

It's actually quite hard to make it happen, but you can get if from things like badly written device drivers (or deleting your system folder, that's a good way to make it happen).

Actually, there is an easy way to make it happen.

Open the computer case and yank something out while it's running. Voila. Done.

A unix Kernel Panic is practically identical to a Windows BSoD.

In both cases something has fucked up beyond belief (Normally bad kernel level drivers or some bad hardware)

Praxis wrote:

Dahak wrote:"No Keyboard found.
Press F1 to continue."

I've gotten that, but I thought it was F8

In a way, that error message makes perfect sense. To correct the error, plug in a keyboard. then press F1 (or F8).

ggs wrote:A unix Kernel Panic is practically identical to a Windows BSoD.

In both cases something has fucked up beyond belief (Normally bad kernel level drivers or some bad hardware)

Only in Windows XP, 2000, and NT. In Windows 98 and 95 you could get a BSOD from doing something as simple as yanking out a floppy after double clicking on a file.

andrewgpaul wrote:

Praxis wrote:

Dahak wrote:"No Keyboard found.
Press F1 to continue."

I've gotten that, but I thought it was F8

In a way, that error message makes perfect sense. To correct the error, plug in a keyboard. then press F1 (or F8).

Nope, because you have to restart to get it to recognize the keyboard

Yeah, but with Win9x, BSODs aren't as critical; in the case of your example with the floppy, you can just hit Escape or put the floppy back in and hit Enter and everything's all right once more. With NT, a BSOD halts the system.

I remember an old error message in the old Half-Life, it went something like ERROR:NoError and then it just shut down HL.

Usually happened when something happened with our network when we had LANs.

Uraniun235 wrote:Yeah, but with Win9x, BSODs aren't as critical; in the case of your example with the floppy, you can just hit Escape or put the floppy back in and hit Enter and everything's all right once more. With NT, a BSOD halts the system.

It takes more to get a bluescreen out of NT though. It will only throw one up when the whole system is irrevocably fucked, whereas 9x will give you bluescreens if it just feels bored.

This one hosted on my friend's blog

http://kzoskronos.home.comcast.net/shafted.JPG

We were trying to install it at skool but thats the only screen we could get. it was so wierd. it worked on other pcs though.