On 12/6/06, Dave Jones <[EMAIL PROTECTED]> wrote:
I don't know what the computer problem was (other than it was serious enough to prevent us from taking off had the pilot not been able to rectify it), nor what hardware processor or what software was involved. The plane itself was fairly new, being less than 5 years old.
Was it the second Tuesday of the month maybe? ;-) But seriously, it should worry us. Don't think this has anything to do with industry standard procedure, except that people have gotten used to "when in doubt, try again" procedure in all kind of computerized situations. If you don't have access to the material to sort out the cause, then your only concern is to get it back up. We have not seen nothing yet. There's a market of alternative microcode for cars (though I am not sure it already goes beyond enabling options that were legally disabled in your country). I tried to talk Sir Santa into getting one of these extra battery packs and new firmware for his Prius, but he wants to postpone till after warranty coverage period... Rob
