NY Windows....heh
 

just when you think your computer is a piece of crap....someone reminds you just what company you are in:

http://www.networkworld.com/community/?q=node/4630/

Just goes to show, it's not the size that matters...it's how it's....uh, I got nothin :lol:

hehehe now this is what I call truth in advertising

Reminded me of when I was kid and turned on the TV to find the cable company had a 'guru meditation error'.

I know some of you will get it :)

Im seeing more and more of these larger than life error messages on billboards.... do you think its a form of advertising?

As soon as they pop up, people say "windows" its almost like they are branding their company through error messages.

Yay! Someone else who owned an Amiga!

Can't tell if you're joking or not......

No, it would be insane to use it as a form of advertising. I mean, the machine doesn't even 'know' that it is being used to power a billboard. And further-more, I don't think that this is the kind of 'publicity' that Microsoft value most. :hmm:

Also, it is not clear what application caused the crash. Something called "Video And Text Output" which appears to be using the DirectX icon. Not necessarily anything to do with Microsoft. Anyone know what this program is? (Google for "Video And Text Output" gives nada)

Teh Evl Windoes Strykes Agen!!!11111!!!!111!1

That's not even a Windows problem. Some other application caused an error. Still funny though.

Those have also become common on elevator advertising/weather screens.

What surprises me is how developers of these unattended systems haven't learned to make use of watchdog tasks. Things happen, whatever the operating system. For Windows it's just part of defensive programming.

Red, the source of an error cannot be known by the error message.

That's an oversimplification surely. I've written apps that give descriptive errors - for example, that value X is not set in the database, and this is required for calculation Y.

So - I think that the source, if not perhaps the ultimate source, is potentially visible in an error message. Whether the error message caters for that level of detail is another matter.

True, I was flying. An program's own error message may be incredibly detailed, and if the problem is self-contained (not dependent on outside code or services) the message may be spot-on. I should have said something like...

The source of a program error cannot be known from a host OS' error message.