Genuine Shop Manuals Standard Equipment on All Cars

On Fri, 10 Dec 2004, mike gray wrote:

> > So when you said "faulty computer systems" you meant "a fault
> > somewhere in some system either feeding or fed by the computer, but
> > quite possibly not directly related to the computer itself in any way
> > shape or form?" And later when you said "Fortunately for most folks,
> > the ECU can deliver all sorts of bogus data with impunity" you didn't
> > actually mean the ECU?

> I try to be a little more trenchant than that.
^^^^^^^^^

You've misspelt "incoherent".

hmmmm he did a fine job
One entry found for trenchant.


Main Entry: tren·chant
Pronunciation: -ch&nt
Function: adjective
Etymology: Middle English, from Middle French, present participle of
trenchier
1 : KEEN, SHARP
2 : vigorously effective and articulate <a trenchant analysis>; also :
CAUSTIC <trenchant remarks>
3 a : sharply perceptive : PENETRATING b : CLEAR-CUT, DISTINCT <the
trenchant divisions between right and wrong -- Edith Wharton>
- tren·chant·ly adverb

"Daniel J. Stern" > wrote in message
n.umich.edu...
> On Fri, 10 Dec 2004, mike gray wrote:
>
> > > So when you said "faulty computer systems" you meant "a fault
> > > somewhere in some system either feeding or fed by the computer, but
> > > quite possibly not directly related to the computer itself in any way
> > > shape or form?" And later when you said "Fortunately for most folks,
> > > the ECU can deliver all sorts of bogus data with impunity" you didn't
> > > actually mean the ECU?
>
> > I try to be a little more trenchant than that.
> ^^^^^^^^^
>
> You've misspelt "incoherent".

hmmmm he did a fine job
One entry found for trenchant.


Main Entry: tren·chant
Pronunciation: -ch&nt
Function: adjective
Etymology: Middle English, from Middle French, present participle of
trenchier
1 : KEEN, SHARP
2 : vigorously effective and articulate <a trenchant analysis>; also :
CAUSTIC <trenchant remarks>
3 a : sharply perceptive : PENETRATING b : CLEAR-CUT, DISTINCT <the
trenchant divisions between right and wrong -- Edith Wharton>
- tren·chant·ly adverb

"Daniel J. Stern" > wrote in message
n.umich.edu...
> On Fri, 10 Dec 2004, mike gray wrote:
>
> > > So when you said "faulty computer systems" you meant "a fault
> > > somewhere in some system either feeding or fed by the computer, but
> > > quite possibly not directly related to the computer itself in any way
> > > shape or form?" And later when you said "Fortunately for most folks,
> > > the ECU can deliver all sorts of bogus data with impunity" you didn't
> > > actually mean the ECU?
>
> > I try to be a little more trenchant than that.
> ^^^^^^^^^
>
> You've misspelt "incoherent".

On Wed, 08 Dec 2004 17:53:39 -0500, Matt Whiting
> wrote:

>mike gray wrote:
>
>> Joe Pfeiffer wrote:
>>
>>> mike gray > writes:
>>>
>>>> Joe Pfeiffer wrote:
>>>> >> mike gray wrote:
>>>> >> >
>>>> >> > Show me a car over four years old without faulty computer
>>>> systems....
>>>> > It's funny how this myth lingers on.
>>>>
>>>> Just like the myth that the earth is a globe.
>>>
>>>
>>> If I were in a pedantic mood, I'd point out it's not. Very close,
>>> though.
>>>
>>>> Just like the myth that operating systems can crash.
>>>
>>>
>>>> What percentage of recalls are for computer problems?
>>>
>>>
>>> Dunno -- but I sure hear of a lot more for mechanical problems.
>>>
>>>> And how old is the computer on which you wrote yer reply?
>>>
>>>
>>> I'd have to check -- but it's a 700 MHz Athlon, and the chip had just
>>> come out when I bought it. Though this is about as relevant as
>>> everything else you wrote except the question about percentage of
>>> recalls.
>>
>>
>> And as relevant as the myth of computer infallibility.
>
>Nobody said computers were infallible, just not prone to a high rate of
>failure as you assert.
>
>
>> If I were in a pedantic mood, I'd point out that it is not -34 degrees
>> here in SoFla, though my vehicle's computer sets the fuel mix there, nor
>> is the proper voltage 22, though that's what the ECU insists on
>> delivering to the battery.
>
>One computer failure does not a trend establish.

Now you sound like Yoda.

On Wed, 08 Dec 2004 17:53:39 -0500, Matt Whiting
> wrote:

>mike gray wrote:
>
>> Joe Pfeiffer wrote:
>>
>>> mike gray > writes:
>>>
>>>> Joe Pfeiffer wrote:
>>>> >> mike gray wrote:
>>>> >> >
>>>> >> > Show me a car over four years old without faulty computer
>>>> systems....
>>>> > It's funny how this myth lingers on.
>>>>
>>>> Just like the myth that the earth is a globe.
>>>
>>>
>>> If I were in a pedantic mood, I'd point out it's not. Very close,
>>> though.
>>>
>>>> Just like the myth that operating systems can crash.
>>>
>>>
>>>> What percentage of recalls are for computer problems?
>>>
>>>
>>> Dunno -- but I sure hear of a lot more for mechanical problems.
>>>
>>>> And how old is the computer on which you wrote yer reply?
>>>
>>>
>>> I'd have to check -- but it's a 700 MHz Athlon, and the chip had just
>>> come out when I bought it. Though this is about as relevant as
>>> everything else you wrote except the question about percentage of
>>> recalls.
>>
>>
>> And as relevant as the myth of computer infallibility.
>
>Nobody said computers were infallible, just not prone to a high rate of
>failure as you assert.
>
>
>> If I were in a pedantic mood, I'd point out that it is not -34 degrees
>> here in SoFla, though my vehicle's computer sets the fuel mix there, nor
>> is the proper voltage 22, though that's what the ECU insists on
>> delivering to the battery.
>
>One computer failure does not a trend establish.

Now you sound like Yoda.

mike gray wrote:
> Ol' Duffer wrote:
>
>> Here's my idea: Since most vehicles seem to be going toward
>> onboard computers anyway, why not install a LAN port in the
>> dashboard with a web server applet and burn the manual files
>> into flash memory? Each vehicle would be furnished with the
>> latest information as it comes down the assembly line, and
>> you could even do automatic updates via XM radio satellite
>> feed. Anyone with a network enabled computer could view the
>> files, print out pages if needed, maintain service logs, etc.
>
>
> But how would you figure out how to repair the defective flash memory?
>
> Show me a car over four years old without faulty computer systems....
i would sure hate to be you your life sucks

mike gray wrote:
> Ol' Duffer wrote:
>
>> Here's my idea: Since most vehicles seem to be going toward
>> onboard computers anyway, why not install a LAN port in the
>> dashboard with a web server applet and burn the manual files
>> into flash memory? Each vehicle would be furnished with the
>> latest information as it comes down the assembly line, and
>> you could even do automatic updates via XM radio satellite
>> feed. Anyone with a network enabled computer could view the
>> files, print out pages if needed, maintain service logs, etc.
>
>
> But how would you figure out how to repair the defective flash memory?
>
> Show me a car over four years old without faulty computer systems....
i would sure hate to be you your life sucks