16 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHI love the new Jake!
Leading reported evidence
Replace posting account and new jake is awesome
Performed · outcome unconfirmed
No successful repair reported for this finding.
0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that performed work without a confirmed outcome
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Performed · outcome unconfirmed · Original poster
Then he changed his posting account and new Jake is awesome!
Leading evidence: 'Replace posting account and new jake is awesome' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, the most frequently mentioned possible cause is 'none of you guys knew the really old jake' (1 discussions; 0 report identifying it and 1 suggest it). The most frequently discussed action is 'Replace posting account and new jake is awesome' (1 discussions). For that action, 0 discussions report a resolution and 0 report an unsuccessful attempt. No action has an explicit, attributable resolution report under the current rules. These are forum reports and suggestions, not a confirmed diagnosis.
Source reports, not a diagnosis or a success probability. Counts refer to discussions and can overlap.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that suspect a cause
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suspected cause
I suspect none of you guys knew the really OLD Jake, from the era of "If it's not air cooled don't drive it in my yard"
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
Agreed, makes me want to use him should the need ever arise.
Counts describe captured discussions, not unique people or a diagnosis. Author identities are not reliably stored. Exact duplicate evidence is counted once across matching discussions; one discussion counts at most once per action/state. Multiple repairs reported together remain a combination. Suggestions and failed attempts do not establish a fix. Matches cover whole discussions and can include related faults, model variants and incomplete threads.
16 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
Rennlist: 1 discussions
0 evidence records excluded for query context · 0 excluded by outcome qualification · 0 adjusted by outcome qualification.
0 acknowledgements have no verified action link; they do not establish a repair result.
Generation: 20261026T163944Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
I haven't been on this forum for long....but when I did start, there was another Jake, can't really remember the guy.
Then he changed his posting account and new Jake is awesome! So much to share!
I have to say it's great being in a forum with somebody like him and the 5 or so others that have so much knowledge and share it.
[Image-only post; no author-written text. Original image references:]
https://cimg8.ibsrv.net/gimg/rennlist.com-vbulletin/1200x954/two_faced_2bed232b337f892a811a3d347238945d66aadafa.gif
That's funny, I noticed it too in Sneaky Pete's thread. I love knowledge and the breadth of knowledge about these engines you share Jake is fantastic! Thanks!
I suspect none of you guys knew the really OLD Jake, from the era of "If it's not air cooled don't drive it in my yard"
When I went to interview with him for a job I drove up in a new Mini . DAMN it.........
Although he was a heck of a nice guy in person.
