1 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHPath to Palooza, Fri, 11/9 - please read if you are going...
Leading reported evidence
Run 's (mtfr)([email removed]
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 · Original poster
Monthly Mid TN Fun Run's (MTFR)([email removed] for details)
Path to Palooza, Fri, 11/9 - please read if you are going...
Read full discussion summary
Leading evidence: 'Run 's (mtfr)([email removed]' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Run 's (mtfr)([email removed]' (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.
Suggestion · Original poster
Our MTFR (Mid TN Fun Run) #8 is a run to the Palooza.
Path to Palooza, Fri, 11/9 - please read if you are going...
Run route and make a guide, and meet yo all
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 · Original poster
I'll run the route and make a guide, and meet yo all before cut-off
Path to Palooza, Fri, 11/9 - please read if you are going...
Coverage and how to read this overview
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.
1 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: 20261026T222516Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
OK, Porsche Palooza is coming up next weekend, 11/9-11/2007. Here is the link for Palooza (
www.pca-palooza.com
). They already have 132 cars registered so far.
Our MTFR (Mid TN Fun Run) #8 is a run to the Palooza. We are driving out Friday the 9th and will be hitting Little Rock about 12:30pm and stopping for lunch. Dick Price (dickepoohp) has been kind enough organize a nice barbque joint for us to stop at for lunch (joint is relative, this place is set up for large crowds). I know several are comign from different directions, so I wanted to invite anyone who would like to meet up with us for lunch to join us. If you are interested, please email me at
[email removed]
, so I can get a rough headcount. I am posting details about getting to the restaurant at the end of this post. After lunch, Dick says there are about 4 ways to get to Eureka Springs and Palooza. Each is different and may suit various individuals depending on how your lunch sits with you! Dick has been nice enough to try to put together some maps to hand out to those joining us for lunch, adn then everyone can make their way to Palooza on the route that suits them. Again, a rough head count would be nice for this part of it as well, so please email me.
One other thought: it would be kind of nice to know a Porsche you see on the road was heading to Palooza or not... maybe a ribbon of a certain color teid to your antenna... any ideas?
Here is the info from Dick about lunch. If you need to, you can call myslef at [phone removed], or Dick Price at [phone removed].
Any ideas on telling who is who at the event... screen names on a window or something?
Take care and here is lunch info:
Here is the tinyurl for the Mapquest for 2516 Cantrell Road, Little Rock, Ar. 72202.
The "real" url was over 1,400 characters!)
http://tinyurl.com/2apboy
Whole Hog is on Hiway 10 (which is Cantrell Road...2615 is addy) just out west from downtown LRock. Coming from Memphis on I-40, you would turn South onto I-30 toward LittleRock, cross the Arkansas River and immediately follow signs to Ar 10 west, which quickly puts you onto a four lane..Whole Hog is in a shopping center on the right just after the traffic light/Exxon station, approx 2 miles from downtown.
Departing, just continue out 10 to I-430, turn north over the river, and bear left to ward Fort Smith on I-40 again.
I'll run the route and make a guide, and meet yo all before cut-off
To clarify.
http://tinyurl.com/2apboy
clik on "aerial image" and zoom in to third bar or so..make much more clear.
Mapquest insists on putting the red star just before the intersection..shopping center is just a block PAST the light..look at this map, restaurant is just above the "10" a few hundred yards to left of star..
__________________
1983 Ruby Red Cabriolet
SCWDP member #0002
http://www.scwdp.com(insert
evil laugh here)
Monthly Mid TN Fun Run's (MTFR)([email removed] for details)
This is a source reference. Confirm exact model applicability in the original material.
