13 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHRecommendation for Milwaukee area Repair Shop
Leading reported evidence
Recommend (only out of sheer curiosity
Suggestion or failed attempt
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 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
is there someone you would recommend (only out of sheer curiosity to see what the response would be)?" His response, "no there isn't."
Leading evidence: 'Recommend (only out of sheer curiosity' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Recommend (only out of sheer curiosity' (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 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.
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.
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.
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.
13 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: 20261026T130754Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
The title says it all. I live in the Milwaukee area (Pewaukee) and recently purchased a 2001 Midnight Blue Cabriolet. It has low miles (26K) and seems to run perfect. It's got the original IMS bearing, so I am thinking about replacing it. I do lots of work on cars myself, but the IMS is above my pay grade.
If you are in the Milwaukee area who would you recommend for this type work?
Thanks
Myron
I would go with Chris. Have had lots of work done on my SC there and likely will take my C4S there too. I've also had work done ay Fabson in Cedarburg abd was happy with their work as well.
Hi myronf,
I recommend European Auto House in Mequon. Nathaniel is the owner/mechanic and was factory trained on 996s...
He is very thorough and honest... went through my entire car when I first bought it!
My car already had the IMS done but I remember being quoted a fair price when looking at other cars!
The funnier part of it was after he said they didn't do IMS bearings there, I asked, "okaaay... is there someone you would recommend (only out of sheer curiosity to see what the response would be)?" His response, "no there isn't."
Unfortunately a couple of guys are like that around here and I will now no longer take my SC over to them. Chris too has made similar comments in the past, but Austin at CS works on them quite frequently.
Talked with Nathaniel today at EAH and he is the only LN certified shop in our area and the cost was ~2500 to do the bearing.
