Hard Light Productions Forums
Off-Topic Discussion => General Discussion => Topic started by: ShivanSpS on May 08, 2007, 05:27:25 pm
-
(http://i18.tinypic.com/63lrre9.jpg)
-
Heh, I saw this on YTMND the other day.
-
It's so nice to know M$ is still up to usual form... :rolleyes:
-
Thats a 3D accelerated blue screen you know! :D
-
I was once on an Airbus flying from the US to Italy and got a BSOD on the video screen in the seatback in front of me.
-
:p
-
Now I really want Vista!
:pimp:
-
How is it that I can't get a BSOD?
I've crashed - frozen - had my HDD die, but not the BSOD.
-
I don't think I've ever gotten a BSOD.
-
The last time I got a BSOD was when I royally ****ed up some driver installation or something.
-
How is it that I can't get a BSOD?
I've crashed - frozen - had my HDD die, but not the BSOD.
Back in the Win95 and Win98 days both of those OS's would BSOD for all sorts of reasons. At one point there was a nifty little trick with some versions of mIRC and some utilities that you could basically just cause a BSOD in Win95 on someone elses computer. Early days of the various internet vulnerabilities. Now it takes a whole lot to get to that point where the OS just shuts off completely and blue screens. Usually its really bad drivers having a field day that causes it...people used to be seeing BSOD's all the time...but now they are quite rare. Which is nice.
-
I was once on an Airbus flying from the US to Italy and got a BSOD on the video screen in the seatback in front of me.
"There has been a critical error, please reset the airplane" :lol: :lol:
-
Actually, there is a way to simulate a BSOD in Windows, IIRC. I forget how it worked...
-
Yeah, I read about that.
Here's how to create a BSOD:
1. Launch the Registry Editor (Regedit.exe).
2. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\i8042prt\Parameters.
3. Go to Edit, select New | DWORD Value and name the new value CrashOnCtrlScroll.
4. Double-click the CrashOnCtrlScroll DWORD Value, type 1 in the Value Data textbox, and click OK.
5. Now if you want a BSOD just press [Ctrl]+[ScrollLock]
But I don't need that. I get BSOds now and then. The fun is that it's unpredictable. I'm surfing the internet and then suddenly BSOD.
-
#756448 +(344)- [X]
<@Longcat> Could a blue screen of death constitute being defenestrated?
<Edible> Thrown out of Windo-
<Edible> ...
* Edible goes to cry.
-
^^ epic.
-
#756448 +(344)- [X]
<@Longcat> Could a blue screen of death constitute being defenestrated?
<Edible> Thrown out of Windo-
<Edible> ...
* Edible goes to cry.
:lol: Truly awesome.
-
I was once on an Airbus flying from the US to Italy and got a BSOD on the video screen in the seatback in front of me.
"There has been a critical error, please reset the airplane" :lol: :lol:
im pretty sure the avionics run linux :D
-
No, I'm pretty sure they don't run any commercial OS. The software is probably tied into the hardware close enough that an OS would be redundant.
Avionics software must be extremely robust and provable. No commercial OS, not even BSD, is either of those.
-
No, I'm pretty sure they don't run any commercial OS. The software is probably tied into the hardware close enough that an OS would be redundant.
Avionics software must be extremely robust and provable. No commercial OS, not even BSD, is either of those.
perhaps. i just figure they used quadruple redundant servers. you can loose 3 before you loose any control, and if you loose 4 it probibly reverts to a hard tie in with the hydraulics. where it handles like a stick and rudder aircraft, rather than a super computerized system that you cant crash if you tried and it pretty muchf flies itself. yea when you consider how much the airframe costs spare no expence on cpu power.
-
Eh, UNIX?
-
Nuke: It's 5 independent systems on smaller commercial aircraft, and 7 or 9 on larger ones.
On the A320 it is actually 5 different computers, with 3 architectures.
as for In-flight entertainment systems. The 777 was delayed by 6 months just to deal with bugs in the entertainment system, and it is rumoured that this is the same problem with the A380
-
I have got Vista, :hopping:, i have seen that screen on many occasion
-
Yup, aircraft need a lot of redundancy, and they use multiple software systems too. No point having five copies of the same software, because they'll all have the same bugs.
-
Generally speaking, mission-critical/safety-critical software for devices like aircraft electronics, lift controls, medical equipment, et al do not have "bugs" as we know them. You don't get away with putting "this can sometimes crash" in the comments section of an app that runs the flow control on a life support machine; Nor in cockpit control software.
-
damn, i would hate to think what would happen to many f1 cars that will run microsoft's ECU, which itself will be standard soon.
-
My friend works for Goodrich aerospace and works on code that's millions of times less complex than that of a modern operating system, is completely tied to the hardware, and yet thousands of man hours go into it to make sure it's rock solid. If the same principles were applied to operating systems, we might get a solid version of Windows or Linux every two centuries or so. :p
-
O_O
Microsoft is supplying what?!
I can't bear the thought of an expensive 800bhp++ engine blowing up thanks to a simple crash... :(
-
My friend works for Goodrich aerospace and works on code that's millions of times less complex than that of a modern operating system, is completely tied to the hardware, and yet thousands of man hours go into it to make sure it's rock solid. If the same principles were applied to operating systems, we might get a solid version of Windows or Linux every two centuries or so. :p
Except that software is, like you said, less complex, and bound to the hardware that it supports :) OSs need to be much larger, and support many different hardware configs.
-
Generally speaking, mission-critical/safety-critical software for devices like aircraft electronics, lift controls, medical equipment, et al do not have "bugs" as we know them. You don't get away with putting "this can sometimes crash" in the comments section of an app that runs the flow control on a life support machine; Nor in cockpit control software.
'There's always one more bug.'
In other words, there's still a tiny probability that a piece of software, no matter how well tested, will fail under a certain unknown set of conditions. Two or three different programs tested to the same standard are a lot less likely to all fail under the same conditions. Which is why they use multiple software architectures for the same task as well as varying types of redundant hardware.