Replies

Glad you are adding your "expertise" but are you a software engineer? You would do the Government more good if you kept out of these threads because you lead people to believe there is a cover-up. I have been around the Air Force for 25+ years and know accident investigations look at every possible scenario and take time. You never, repeat never, discount something like software, structural fatigue, hairline cracks undetected (except this shuttle just went through overhaul and their wings should have been ex-rayed looking for fatigue), or any number of potential problems. Tiles have fallen off before.

Don't tell us software cannot be a problem -- my brother is a software engineer! Nothing is 100% full proof! Ask the automatic test community in DoD! Other family members/friends are Government aerospace/electronic engineers so don't go around treating people like idiots when they ask questions or give their theory.

No one knows for sure what happened and that is what the Accident Board will determine!

Glad you are adding your "expertise" but are you a software engineer?

I am a man of many, many talents and in a wide, but associated, variety of fields ...

Don't tell us software cannot be a problem -- my brother is a software engineer!

I don't think you have any idea of the practices and special hardware that can be used in hi-rel apps, techniques such as watchdog timers, timed execution of check-sum routines that examine/tally program memory to verigy it's integrity ...

Most programmers have *little* on-the-hardware experience or understanding thereof - they are far better off using the stndard 'libraries' and leaving the hardware I/F and real-time programming to the EE's ...