Re: [NTLK] MP2100 Offset of Recognition

From: Stefan Thorsteinson <>
Date: Mon Aug 24 2009 - 19:01:54 EDT

Mr. Brown,

Thank you. A recent holiday to the wilds of Manitoba may be a contributing
factor. (Amazing what you can find once you have the correct term:
"JAGGIES") The archives is a wonderful source as is Eckhart's PDA soft site.
The link to the PDF file on the WWNC2007 site appears broken. If anyone has
a copy they can share that would be great.

The way I see it my issue is likely dirt under the case to screen. I'm
usually diligent about that but obviously dropped the ball while on
holidays. "Apart she comes" for a good cleaning. Thanks all. I think I'm on
the right trail.

Now, where's my poutine and sledgehammer? :)

Thank you,
Stefan Thorsteinson

-----Original Message-----
[] On Behalf Of L.W. Brown
Sent: Monday, August 24, 2009 3:45 PM
Subject: Re: [NTLK] MP2100 Offset of Recognition

to reiterate - it's almost certainly a case of "the jaggies": dust or
a crumb caught between the screen and the screen bezel, or something
about the case itself, putting pressure on the pressure sensitive
screen layer.
if cleaning under the bezel does not work, then a more serious
adjustment to the geometry of the inside of the case may be required -
in either situation, plenty of detailed instructions are in the list

On 24. Aug., 2009, at 16:23 PM, Stefan Thorsteinson wrote:

> Ed, Thanks for the direction - will do.
> Abraham, Should have mentioned that recalibrating screen does nothing.
> -----Original Message-----
>> From:
>> [] On Behalf Of Ed Kummel
>> Search the archives (see the bottom of this message for the link)
>> and do a
>> search for the word jaggies
>> --- On Mon, 8/24/09, Stefan Thorsteinson <>
>> wrote:
>>> I'm noticing that my 2100, for no apparent reason that I can
>>> trace, will
>>> start offsetting the point of recognition of a tap on the screen.
>>> If I tap
>>> on an X to close an app., it thinks I tapped a spot to left. Just
>>> enough to
>>> make typing frustrating. For example: If using the onscreen
>>> keyboard a "t"
>>> becomes and "r", a "j" an "h" etc.
>>> Has anyone else experienced this? I've had to do a hard reset in
>>> order to
>>> rectify in the past. Is there a better way?

The NewtonTalk Mailing List -
The Official Newton FAQ -
The Newton Glossary -
WikiWikiNewt -

The NewtonTalk Mailing List -
The Official Newton FAQ -
The Newton Glossary -
WikiWikiNewt -
Received on Mon Aug 24 19:02:34 2009

This archive was generated by hypermail 2.1.8 : Tue Aug 25 2009 - 03:30:00 EDT