|
KB2VXA > TREK 25.02.04 17:38l 45 Lines 1795 Bytes #999 (0) @ WW
BID : 20730_WT3V
Read: DB0FHN GUEST
Subj: Re: G0TEZ's abrasive hull plating
Path: DB0FHN<DB0FOR<DB0SIF<DB0FSG<HB9EAS<HB9AK<K1UOL<K1UOL<WA2PNU<KC2COJ<
WT3V
Sent: 040225/0805Z @:WT3V.#CNJ.NJ.USA.NOAM #:20730 [Lakehurst] $:20730_WT3V
From: KB2VXA@WT3V.#CNJ.NJ.USA.NOAM
To : TREK@WW
Hi Ian (the British one),
Why are you getting all snotty?
"Warren seems to engine (?) a bit of a fight in public. ... I don't think
he'll stop 'til he's prooved (proved) his superiority."
Just because I have given the proper definition of "plasma" and a full
explanation of how ST star ships use it as a power transfer medium you
don't have to get all huffed up and ask the same question again. Can't
you simply accept the dictionary definition and a common sense
explanation (backed up by plenty of series tech notes) or are you bent on
starting another squabble in order to once again kill TREK?
We don't need this sort of nonsense, especially since it has happened
repeatedly and each time it's a long time before anyone dare post
anything for fear of getting into it again.
BTW, the news reports on the space shuttle burnup on reentry continually
referred to the cause as "engress of plasma" which caused the heat alarms
in the wheel well to go off. Your partial quote (clip) of that
explanation containing a partial reference to the Challenger explosion is
misleading. That may be expected with clipped quotes such as this, it was
a leaking O ring in one of the solid fuel boosters that caused the
Challenger explosion, but hopefully everybody by now has both stories
straight simply by watching the news and the video clips of each of those
shuttles on takeoff.
C'mon Ian, you can do better than all that, really.
73 de Warren, KB2VXA@WT3V.#CNJ.NJ.USA.NOAM
Powered by JCP&L atomic energy.
E-MAIL: kb2vxa@juno.com
**************************************
Preserve the integrity of our network,
stop Internet forwarding!
**************************************
Message timed by cesium laser: 08:13 on 2004-Feb-25 GMT
Read previous mail | Read next mail
| |