Slashdot Mirror


SpaceX Launch To International Space Station Delayed For Code Tweaks

RogerRoast writes "The first private spaceship launch to the International Space Station has been delayed, possibly by at least a week, the vehicle's makers announced Monday. The commercial spaceflight company SpaceX was set to launch its Dragon capsule atop a Falcon 9 rocket April 30 from Cape Canaveral Air Force Station in Florida." The article quotes SpaceX lead Elon Musk's twittered explanation: "Am pushing launch back approx a week to do more testing on Dragon docking code. New date pending coordination with @NASA."

72 of 97 comments (clear)

  1. Re:Sure... by azalin · · Score: 4, Funny

    Maybe the just noted half the libraries were in metric

  2. Patches by Chillas · · Score: 1

    I have waiting for patches to install. They always seem to take forever.

    --
    --- Math illiteracy affects 8 out of every 5 people.
  3. Release schedules by azalin · · Score: 3, Insightful

    When is any project ever on time? It's not like they can release beta grade software and release an automatic update to fix it later. If they mess this up, it's going to cost them and maybe, just maybe the engineers plea for proper testing has been answered (a little late though)

    1. Re:Release schedules by Infiniti2000 · · Score: 2

      ...and maybe, just maybe the engineers plea for proper testing has been answered (a little late though)

      Not late. Hopefully, just in time. Late would be after launch and, then uh oh...

  4. Yikes! by sycodon · · Score: 4, Insightful

    "Last minute code tweaks" never go well.

    --
    When Fascism comes to America, it will call itself Anti-Fascism, and tell you to give up your guns.
    1. Re:Yikes! by Like2Byte · · Score: 5, Funny

      heh.

      Reminds me of that song, "99 instances of bugs in the code..."

      99 instances of bugs in the code...
      99 instances of bugs, ....
      code one out, mark it out,
      106 instances of bugs in the code...
      106 instances of bugs in the code...
      106 instances of bugs, ....

    2. Re:Yikes! by Megane · · Score: 1

      But they're a lot worse when you have to send updates to an already deployed system. LEO is one of the remotest of remote sites. It's kind of hard to get the janitor to walk up and to push the reset button for you. I think a week delay to get it right is a lot better than "ship it and we'll push an update later".

      --
      #naabhaprzrag, #sverubfr-000, #agi-fcbafberq, negvpyr[pynff*=' negvpyr-ary-'] { qvfcynl: abar !vzcbegnag; }
    3. Re:Yikes! by jaymemaurice · · Score: 1

      Thats why all LEO devices need advanced ILO or DRAC licenses. Can I be CTO now?

      --
      120 characters ought to be enough for anyone
    4. Re:Yikes! by gstrickler · · Score: 1

      What about last minute code tweaks that save a ~$1M account, and work so well that within 3mos are rolled out to 90% of customers?

      I agree with you, but never is a strong word.

      --
      make imaginary.friends COUNT=100 VISIBLE=false
    5. Re:Yikes! by Megane · · Score: 1

      Only if you can RFP more TLAs ASAP!

      --
      #naabhaprzrag, #sverubfr-000, #agi-fcbafberq, negvpyr[pynff*=' negvpyr-ary-'] { qvfcynl: abar !vzcbegnag; }
    6. Re:Yikes! by sycodon · · Score: 1

      I'd call that pulling your ass out of the fire at the very last minute.

      --
      When Fascism comes to America, it will call itself Anti-Fascism, and tell you to give up your guns.
    7. Re:Yikes! by gstrickler · · Score: 1

      Not exactly. The bug was on their end, I just added a feature that avoided their bug, and it was a feature that lots of others found reduced confusion so everyone wanted it.

      --
      make imaginary.friends COUNT=100 VISIBLE=false
    8. Re:Yikes! by sycodon · · Score: 1

      "Last minute code tweak" to me, means changing the code at the very last minute.

      They say a week, but it seems that with something so complex any change in code would require a complete rerunning of all of the regression tests, a complete detailed examination of the results plus a review by whatever group provides oversight.

      Try to get that all done in one week under a drop dead deadline...recipe for disaster.

      --
      When Fascism comes to America, it will call itself Anti-Fascism, and tell you to give up your guns.
    9. Re:Yikes! by sycodon · · Score: 1

      Well, You Da Man in that case.

      Strictly speaking though, your tweak should have under gone the full test and review process. But then, while we read about those things, very few companies actually have them.

      --
      When Fascism comes to America, it will call itself Anti-Fascism, and tell you to give up your guns.
    10. Re:Yikes! by blueturffan · · Score: 2

      Sorry, ASAP is an FLA, but FLA is a TLA.

    11. Re:Yikes! by gstrickler · · Score: 2

      In theory, yes, it should have gone through more extensive testing. But business timelines don't always allow that.

      I cultivated a great relationship with our QA dept. While I had the ability and authority to bypass QA and put something in production, I only did that in one or two emergencies over 16 years. The rest of the time, I made sure my code went through QA, even if it was an abbreviated test, and I (almost) always gave them a list of things I thought they should test, to which they would add their own tests. And I never gave them a hard time or had a bad attitude about them finding bugs or suggesting improvements to the work flow, UI, wording, etc. I gave them code with few bugs, they gave me valuable feedback and kept most of my bugs from reaching production.

      JMHO, but that's how development & QA should work.

      --
      make imaginary.friends COUNT=100 VISIBLE=false
    12. Re:Yikes! by FullBandwidth · · Score: 1

      True - but where in the article does it say anything about making any code tweaks? All I saw was they want to do more hardware-in-the-loop testing and review the data. If all that passes muster, no code will change and presumably they will be go for launch. If it doesn't pass, THEN they may consider standing down to make code changes. Or, change operational procedures or ground software or ask for a waiver or any of a number of corrective actions. Maybe MSNBC updated the article after you read it ... or maybe my browser hid page 2 or something? The only mention of "code tweaks" is in the incorrect /. headline. Cheers

      --
      My friend Debbie Ann is so promiscuous, instead of an appointment book she needs a package manager
    13. Re:Yikes! by monoqlith · · Score: 1

      Last minute bug fixes are one thing. Last minute features are another.

      Last week I made a last-minute feature add that not only saved my job(the VP changed his mind about me), but got me promoted.

      I don't mind saying: It was legendary.

  5. Better to fix it first by pablo_max · · Score: 5, Insightful

    Better they found it now and missed the deadline than went anyhow and exploded. You do not get too many second chances in space.

    1. Re:Better to fix it first by Theophany · · Score: 3, Insightful

      My thoughts exactly. If only the same had happened with Challenger.

    2. Re:Better to fix it first by joh · · Score: 4, Informative

      Has nothing to do with "exploding". The problem is the automatic docking (actually berthing) and I've read they still have too many false emergency aborts in testing. They don't want to go all the way to the ISS just to have it pull back for no good reason automatically.

      Anyway, if they have their software and their testing not ready one week before launch, this isn't good at all. They should better put if off for a month or so.

    3. Re:Better to fix it first by jamesbulman · · Score: 4, Funny

      I've checked in the fix...

      //bugfix: Stop abort code messing up docking
      //if(doAbort)
      //{
      // DoAbort();
      //}

    4. Re:Better to fix it first by luis_a_espinal · · Score: 1

      Better they found it now and missed the deadline than went anyhow and exploded. You do not get too many second chances in space.

      In Space No One Can Hear You Scream.

    5. Re:Better to fix it first by gstrickler · · Score: 1

      Dave? Is that you?

      --
      make imaginary.friends COUNT=100 VISIBLE=false
    6. Re:Better to fix it first by Darinbob · · Score: 1
    7. Re:Better to fix it first by X0563511 · · Score: 1

      Not so much exploding, but aborting for no real reason and wasting lots of time and funds. (or taken the other way, not aborting and damaging the ISS)

      --
      For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
    8. Re:Better to fix it first by lenorin · · Score: 1

      Just wanted you guys to know, the SpaceX flight software group are laughing our asses off right now. Thanks.

  6. Re:Elon Musk by Anonymous Coward · · Score: 2

    He's doing an absolutely fantastic job with his two post-paypal start-ups. I already have quite a few shares of Tesla, and when SpaceX goes public I'll pick up as well.

    not sure telsa is a wise investment choice, always seem to be on the brink of going broke

  7. Where is their spirit of adventure? by fuzzyfuzzyfungus · · Score: 5, Funny

    Cowards!!! Launch early, launch often. (Or just give the coders the honor of being test pilots. That will make those code monkeys program it real good the first time...)

    1. Re:Where is their spirit of adventure? by HangingChad · · Score: 1

      Cowards!!! Launch early, launch often.

      Seriously, if the rocket went wonky the most likely place for it to land would be on Titusville. Whatever it hit there would make an instant improvement.

      --
      That's our life, the big wheel of shit. - The Fat Man, Blue Tango Salvage
    2. Re:Where is their spirit of adventure? by t4ng* · · Score: 1

      Exactly this. It will be interesting to see how the "ship the beta, we'll fix it later with patches" style of development holds up in any renewed interest in space travel. So far it's not looking good.

    3. Re:Where is their spirit of adventure? by fuzzyfuzzyfungus · · Score: 1

      You wouldn't want to take it to the extremes commonly practiced by the software industry; but it wouldn't entirely surprise me if the 'ship now, fix later' model, within limits, actually holds up pretty well as long as only robots and expendable people(and no radioisotopic generators) are involved...

      If space travel is going to be anything but a toy(outside of a few commercially viable niches for small satellites doing very valuable things in earth orbit), launch costs need to fall. If launch costs fall, the economics of being a raging perfectionist about every bit of gear you send up start looking less sensible compared to taking the risk of possibly having to send up a second one.

      Concerns about space junk ruining valuable orbital slots will place a lower bound on how careless the world's nation states will let you be, and public opinion will be touchy about any accidents involving radioactive sources or high-profile humans burning up in the atmosphere; but nobody cares about the occasional satellite dropping dead or unmanned satellite launch blowing up...

    4. Re:Where is their spirit of adventure? by Darinbob · · Score: 1

      Well there's a wall full of post-it notes that will get them halfway there. Next week the scrum starts to get them the other half of the way.

  8. Re:Elon Musk by XPeter · · Score: 1, Interesting

    They already have thousands of pre-orders for the Model S, and I'm betting they'll get even more for the Model X

    --
    "The difference between genius and stupidity is that genius has it's limits" - Albert Einstein
  9. Did they try... by Troyusrex · · Score: 1, Funny

    updating to the latest version and rebooting? That's what vendors always tell us to do the second anything doesn't work perfectly.

    1. Re:Did they try... by fuzzyfuzzyfungus · · Score: 1

      I would suggest adding a watchdog to the system to handle that, but just ask Laika how well that works...

    2. Re:Did they try... by tompaulco · · Score: 1

      In the case of SpaceX, the problem probably is that they have too many windows open.

      --
      If you are not allowed to question your government then the government has answered your question.
    3. Re:Did they try... by Loadmaster · · Score: 1

      Here's the transcript from the launchpad.

      Robot #2: "Uh oh, he froze up again."
      Robot #3: "Try control, alt, delete!"
      Robot #4: "Jiggle the cord!"
      Robot #5: "Turn him off and on!"
      Robot #6: "Clean the gunk out of the mouse!"
      Fry: "Call technical support!"
      Robot #2: "Ok, ok, he's back online."

  10. NASA behind this by Anonymous Coward · · Score: 2, Interesting

    Not that SpaceX is infallible - but I think it's NASA behind this requiring an insane amount of testing. They employ the Monte Carlo method of testing which basically tests every (or at least a random sample) value of each input variable and the combinations there of. I don't care who you are, but that method of testing is going to result in "issues" coming to the surface. The problem is that the issues will be extremely rare if not practically impossible. And Musk is not in a position to criticize them, since he wants their business for cargo and crew services.

    Not saying this kind of testing isn't valuable, but it doesn't lend itself well to schedules.

    1. Re:NASA behind this by mbone · · Score: 4, Insightful

      Space travel has a long history of "extremely rare if not practically impossible" issues coming up to bite you. Missions have been lost because of a single missing comma in the code. So, there is reason for this caution, and neither you nor Elon Musk is going to be able to change it.

    2. Re:NASA behind this by taiwanjohn · · Score: 2

      Can't say I blame them for all the testing, given the potential risks involved. It's frustrating as hell to put up with the delays, but we space geeks ought to be used to that by now.

      One thing I'm curious about is whether or not they're going to try recovering the booster stages on this launch. Musk has said in the past that they're going to "keep trying until we get it right," but with all they've got riding on this mission already, I wouldn't be surprised if they skip that in order to concentrate everything on rendezvous and berthing. Still, it would be quite a feat if they could pull off that stunt as well on this launch.

      --
      XML is like violence. If it doesn't solve your problem, you're not using enough of it. --AC
    3. Re:NASA behind this by luis_a_espinal · · Score: 3, Insightful

      Not that SpaceX is infallible - but I think it's NASA behind this requiring an insane amount of testing. They employ the Monte Carlo method of testing which basically tests every (or at least a random sample) value of each input variable and the combinations there of. I don't care who you are, but that method of testing is going to result in "issues" coming to the surface. The problem is that the issues will be extremely rare if not practically impossible. And Musk is not in a position to criticize them, since he wants their business for cargo and crew services.

      Not saying this kind of testing isn't valuable, but it doesn't lend itself well to schedules.

      This is how you test mission critical systems. No, this is how you must test mission critical systems, regardless of schedules. The key adjective here is "mission critical". This ain't a Heroku web deployment just so you know.

    4. Re:NASA behind this by crazyjj · · Score: 4, Insightful

      NASA and Russia are extremely cautious when it comes to anything ISS-related for very good reason. If this thing really screwed up and seriously damaged ISS to the point where they had to abandon it, it would probably end the era of human spaceflight and lead to big budget cuts for both agencies.

      --
      What political party do you join when you don't like Bible-thumpers *or* hippies?
  11. I can see the headlines now by crazyjj · · Score: 2

    "ISS Seriously Damaged Because That Fucking Moron Peter Forgot To Do Garbage Collection."

    --
    What political party do you join when you don't like Bible-thumpers *or* hippies?
    1. Re:I can see the headlines now by Megane · · Score: 1

      Next week on Family Guy: Peter gets a job writing spacecraft docking software!

      --
      #naabhaprzrag, #sverubfr-000, #agi-fcbafberq, negvpyr[pynff*=' negvpyr-ary-'] { qvfcynl: abar !vzcbegnag; }
    2. Re:I can see the headlines now by Darinbob · · Score: 1

      This isn't garbage collection. All I see is reference counting!

  12. Wait, what? by tgd · · Score: 1

    How does a statement that they're doing "more testing" turn into "fixing bugs"?

    All the posts on here are all ZOMG, buuuug fixes!

    The tweet and article say no such thing. And if you haven't finished your test cycle, best to delay and finish it. That's not rocket science.... or is it?

    1. Re:Wait, what? by FatLittleMonkey · · Score: 1

      Rumours are that they've been getting too many erroneous abort codes during testing. It may not be true, but it seems a reasonable inference that solving such a problem would have required changes to the code, changes that themselves required testing. Hence the delay.

      --
      Science is all about firing a drunk pig out of a cannon just to see what happens.
  13. Re:Sure... by K.+S.+Kyosuke · · Score: 3, Funny

    Yes, but which half?

    An imperial half.

    --
    Ezekiel 23:20
  14. One week? by hey_popey · · Score: 1

    I am surprised. I don't remember very well what were the launch windows for LEO orbits, so this might not be applicable... But for GTO orbits, it was either one or two days of delay if there was a minor preparation glitch on the launcher, or something like one month if a new flight software had to be generated and qualified... Anyone knows more about this?

    1. Re:One week? by BZWingZero · · Score: 1

      For the ISS, launch windows are less than 10 minutes with about one window every day. This lasts a few weeks then there's a couple week period without a window.

  15. if it were open source by nimbius · · Score: 4, Funny

    im sure you'd see git comments like
    --removed sound-activated LED code
    restored sound activation code. needed for espresso.py

    --removed callbacks, class for rancilio espresso maker. please stop this.
    --added pizza ordering support for dominos, stub for pizza hut

    --removed food related code for pizza, chinese food, references to 'the luther'.
    -- removed orbital re-entry positioning code. two can play this game
    -- re-added orbital code. this is not funny. please stop.
    -- added DMX512 dance-floor lighting control module, arduino support for twitter potted plant control

    --
    Good people go to bed earlier.
  16. hmm by strack · · Score: 1

    guess it really will be a diablo 3 launch.

    1. Re:hmm by DigiShaman · · Score: 1

      Let's hope it won't turn into a "falling star" as in Diablo 3 there after.

      --
      Life is not for the lazy.
  17. Re:Sure... by jellomizer · · Score: 1

    Having worked for commercial industry, this is code words for, we are not done coding it yet.
     

    --
    If something is so important that you feel the need to post it on the internet... It probably isn't that important.
  18. Launch window by Skylax · · Score: 1

    Can he just delay by one week? There are only small launch windows for Cape Canaveral launches to ISS. Does somebody know the approximate window size for a Falcon 9+Dragon launch to ISS? Also from this ISS launch schedule, there is a launch of a soyuz at may 15th so if he delays too much, he will probably have to move the launch date back by at least a month.

    I wonder what the requirements are at NASA versus SpaceX concerning mission failure probabilities? Reaching a 90% chance of success is probably easy but 99.99% chance of success is much harder.
    And then you could ask if NASA or SpaceX has such high requirements why didn't SpaceX plan accordingly? Are they forced to promise early launch dates to keep investors?

    1. Re:Launch window by Anonymous Coward · · Score: 1

      A launch window happens approximately once per day, give or take a few minutes.

      The ISS has a fairly static orbit as far as it matters for this purpose, so you only have to wait for the earth to rotate to the right angle under it. It reliably does that with every rotation.

      However, it is important to note that you can't just casually put off a launch for anther day, because for every delay you have, you're going to need to calculate a new course for the rocket's guidance system and make sure you haven't fucked that job up. For a machine costing a decent fraction of a billion, you don't just slap in whatever numbers seem right and hope for the best.

    2. Re:Launch window by Mercano · · Score: 1

      There was a Atlas V scheduled to go up on the 5th, but that's now bumped up to the 3rd. I read over at NASASpaceFlight that Falcon 9 has a launch window approximately every three days from the Cape to ISS. Spaceflightnow.com has a worldwide launch calender; you can see how many times this flight has been delayed. It was originally scheduled for June 6th of last year, so it'll be just a day shy of 11 months behind schedule, if there aren't any further reschedules.

      --
      #include <signature.h>
    3. Re:Launch window by ClayJar · · Score: 1

      The Space Shuttle had a launch window of approximately plus or minus five minutes from in-plane, but for the Falcon 9/Dragon COTS-2/3 launch to ISS, they have an instantaneous launch window. From the comments on the COTS-1 webcast, it sounded as if Dragon flights to ISS would have instantaneous launch windows, but I have no data to know whether this is merely a constraint for the initial flights or a constraint for all future COTS/CRS launches.

      For the April 30th window (which will not be used), there was also an instantaneous launch window on May 3rd (with the days between those two blocked by ISS orbital constraints, I believe -- SpaceX has additional requirements for the test launch and recovery than for an operational launch). The next set of instantaneous launch windows would be May 7th and May 10th (with the days between blocked), but the May 10th window would mean that in the event of an aborted docking, there would be only time for one additional attempt before Soyuz conflicts (which would push the Dragon docking beyond May 17th, which may or may not be possible depending on fuel constraints, which I am not privy to).

      Regarding the failure probabilities, from last week's press conference, it sounded as if SpaceX is the primary driver of mission assurance for this flight, i.e. they want to be sure they have as many of their waterfowl properly queued as possible. A cynic might note that if they don't get it right this time, it costs NASA nothing and SpaceX the full cost of another attempt. Someone with a brighter outlook would likely just say that if *everyone* on earth were watching you (most hoping you'd succeed, some hoping you'd fail), you'd *really* want to double-check everything one last time.

  19. Re:Sure... by craigminah · · Score: 2

    I too worked in the space launch business and delays always are lastg minute because they cost so much and everyone is waiting for someone else to be the reason for the delay. If there was a delay due to cryo problems the coding issue would never come to light as they'd feverishly work to get it done while launch is delayed due to "cryo issues."

  20. Life support systems require more rigorous testing by tlambert · · Score: 5, Insightful

    Life support systems require more rigorous testing than simple Monte Carlo. They generally require component testing, bounds case testing, and branch path analysis of the code so that every line of code gets hit during testing.

    I've worked on two projects that qualified as life support systems; one was an MRI console for a GE Medical Systems MRI machine (back when it was still being called NMR before it was politically corrected to remove the word "Nuclear"), and the second was a blood gas analyzer. Incorrect operation of the code in either of those cases could have resulted in someone dying as a result of a doctor getting misinformation.

    The amount of testing and the rigor of the testing involved in both of those projects was unbelievable. Even then, we were required to carry liability insurance out the wazoo on both projects in case we screwed up the code. There's a reason medical equipment is so expensive.

    Space systems that can ram into an occupied space station, and which are intended to some day carry humans to orbit qualify as life support, even if they are being sent up with a load of supplies instead of a human crew. Monte Carlo won't cut it any more than it will for a system call fuzzer trying to find a sequence of three system calls in a row that , if they are called with precisely the right parameters, will trigger a kernel panic.

    -- Terry

  21. Title is wrong, /. SOP by paramour · · Score: 2

    TFA says the delay is for hardware in the loop testing, not code tweaking.

    One hopes normal end-to-end testing was done long before this, but given the costs and logistics of assembling the actual hardware this final phase of testing pretty much has to wait until shortly before launch.

    I'm a developer and am pretty much in the camp of "if it complies and boots, ship it", but I appreciate the need for QA. When you're shooting a missile at a fragile target keeping a crew alive 200 miles above earth just maybe before you sign off on the launch you want to finish testing. It's the low delta-v docking code they're testing apparently, but docking coupling damage has happened in the past, and that or just a failure to dock would be kind of a big deal.

  22. Tests, not tweaks! by wjsteele · · Score: 4, Informative

    No where in Elon's Tweet or in the referenced article does it say they need to tweak the code... it says they need more time to "test" it.

    Bill

    --
    It's my Sig and you can't have it. Mine! All Mine!
    1. Re:Tests, not tweaks! by joh · · Score: 1

      If the testing wouldn't carry the risk of having to change some code (or tweak some parameters) they could just stop testing and launch already.

  23. On a rocket? by garyoa1 · · Score: 1

    What am I missing? I thot the commercial companies were all building a "kind of" plane or space ship since they'd be re-useable. Why/when did they fall back to rockets?

    --
    Wuddooeyeno? IITYWYBMAD? Like nuts? eclecticallyincorrect.com
    1. Re:On a rocket? by wjsteele · · Score: 1

      Actually, only a few companies working on non-orbital vehicles are designing aircraft with wings... since they spend a lot of their time in the air... in space, you don't need wings. It's much more efficient to design a vehicle without them if all you're doing is shooting it up on a rocket and landing it under a parachute (after reentry, which also causes problems for wings.)

      Bill

      --
      It's my Sig and you can't have it. Mine! All Mine!
  24. Re:Sure... by Tmann72 · · Score: 1

    I'm pretty sure they want to make absolutely sure it doesn't fail. Considering the fact the capsule costs a ton of money to make, and the historic factor here. If they fail now it could potentially destroy the companies finances and reputation. I highly doubt this is so simple as being 'not done coding yet.' Its more likely they decided to do another round of unit tests to make absolutely sure everything is going to work.

  25. Re:Falcon-Dragon by WindBourne · · Score: 1

    Ah, You must be working on the SLS?

    --
    I prefer the "u" in honour as it seems to be missing these days.
  26. The Last Bug Guy worked for NASA by RobertLTux · · Score: 1

    but hey at least they had a body to bury "face down 9 edge first" since a number of times in NASAs case they didn't.

    --
    Any person using FTFY or editing my postings agrees to a US$50.00 charge
  27. Much better article by joh · · Score: 2

    NASAspaceflight has a much better article than TFA. Go read it, if you're interested in details and facts.

  28. Re:Elon Musk by X0563511 · · Score: 1

    That's the perfect time, if you think the risk is acceptable. Things don't get much more rock bottom than rock bottom.

    The trick is to be patient and not pull out, consider the money you invested lost already, and put it out of your mind. This way, the worst that will happen is nothing.

    --
    For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
  29. Re:Delayed because of code change or because .... by wjsteele · · Score: 1

    Really? I'm pretty sure Falcon 1 has successfully launced several payloads to orbit... which pretty much blows your assertations out of orbit. Also, the Falcon 9 has had launched twice, both successfully orbiting the Dragon capsule (though the first was just a shell with no avionics) it still was a successful mission. They did have failures (first 3 F1s for example) but that's not a 90% failure rate by any stretch.

    Bill

    --
    It's my Sig and you can't have it. Mine! All Mine!