fullymatted.
Back to search
986Forum

Message for JT! - 986 Forum - The Community for Porsche Boxster & Cayman Owners

Add to repair workspace
Open repair workspace
Original source
3 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW

Discussion summary

YOUR RESEARCHMessage for JT! - 986 Forum - The Community for Porsche Boxster & Cayman Owners

Leading reported evidence

Replace text in the body of the message

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

I changed the text in the body of the message, but was unable to edit the title itself.

Original post Read captured discussion
Message for JT! - 986 Forum - The Community for Porsche Boxster & Cayman Owners
Read full discussion summary

Leading evidence: 'Replace text in the body of the message' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Replace text in the body of the message' (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.

Read captured replies

1 matching discussions · 3 captured posts examined · 0 partial discussions

Frequently discussed actions (1)

These are separate views of the same evidence. Frequency alone does not establish a fix, and these counts must not be added together.

Replace text in the body of the message

No successful repair reported for this finding.

0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
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

I changed the text in the body of the message, but was unable to edit the title itself.

Original post Read captured discussion
Message for JT! - 986 Forum - The Community for Porsche Boxster & Cayman Owners
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.

3 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.

  • 986Forum: 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: 20261026T052503Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources

POST 1 / ORIGINAL POSTEROriginal post

JT, Can you please change the title of the first message in the KC Box message area to read October 19th instead of 12th? I changed the text in the body of the message, but was unable to edit the title itself. PLEASE HELP! Also, are you the same JT that works for Intel and posted a message about the Xscale processor yesterday on the Clie site? If so, I'd like to chat with you about Xscale. Thanks, Ken

POST 2Original post

I will change the title for you. Yes that was me on the Clie site JT

POST 3 / ORIGINAL POSTEROriginal post

Yes I meant the 12th instead of the 19th, brain fart! Do you want the PDF file for the new CLIE? Ok, question on the Xscale, Intel promised us all this extra performance when we made the jump to 400mhz Xscales vs. 206mhz Strong ARMs, but so far in Pocket PC devices there is little difference. As I understand it, it is because PocketPC is based on Win CE 3.0 and it isn't optimized for Xscale, but that Intel and Microsoft put some patches into PocketPC 2002 to tide users over and give them "some" performance increase, although there have been a lot of complaints about chopping media playback on some forums, something that PocketPC 2002 was supposed to be "patced" for XScale to improve performance. What's the hold up on performance and when will it get better? I also saw where XScale can scale down battery usage to extend battery life, but if you look at that new Clie, 5 hours of NON-Backlight usage is HORRIBLE battery life for a PDA, and it runs on Xscale. My own experience with XSCale PocketPC's is that battery life is about the same as on StrongARM, so again, where's the improvement? Thanks! Ken Yes the 12th, change everything to 12!

This is a source reference. Confirm exact model applicability in the original material.