Caution on Universal Wireless Keyboard driver

Archived from groups: comp.sys.palmtops.pilot (More info?)

Just a note in case my suspicions are correct, so nobody else runs into
the same thing:

I downloaded and installed the new (10/8/04) Universal Wireless Keyboard
driver the other day without realizing that it was the driver for a new
product and *NOT* an updated driver for the IR Wireless keyboard, and
when I ran it managed to lock the system so hard that even a reset was
being ignored.

Since it's a character input app and Palm says that it's for the T3, T5
and other similarly new devices only, I suspect that it ties into the
Grafitti2 libraries in some way. That means that IF I'm right, anyone
who's reverted to the older Grafitti with T|T PRCs may have the same
problem I did - my Palm locked up so hard that I had to wait for the
battery to completely die and wipe the memory before I could do anything
with it.

If this happens to you, it only takes a day or two because the T3 locks
with the screen on. Eventually voltage drops too low to power the
screen, but it'll keep powering the LED for longer. After that goes out
you'll probably have to wait another 24 hours or so for the battery to
get far enough down that the memory clears. Following that you should
be able to re-hotsync as if you'd done a hard reset (since you have -
you've done the "dead battery reset" ). If you still have that keyboard
driver on, when you run it the same thing will happen again, so I'd
advise either deleting it or just removing keyboard.prc from your Backup
directory.

Hope this is useful for someone,
ajm

Archived from groups: comp.sys.palmtops.pilot (More info?)

On Mon, 01 Nov 2004 21:49:09 GMT, Alan Miller wrote:

>>2. How long did you wait after the 'dead battery reset' was
>>performed (counting from power off of the screen)? Is 24 hours
>>enough?
>
> I don't recall precisely, but it was between 1-2 days (it was over the
> weekend). I didn't have it with me for 2-3 business days, but I don't
> recall which. After that I put it back on the cradle and let it charge
> for a while; when turning it on then it was like it was coming back from
> a hard reset. It didn't come back to life immediately after I put it on
> the cradle.

Out of curiosity, isn't the T3 screwed together rather than glued like
the Vx? In that case, wouldn't it be more expedient to open the case
and disconnect the battery?

On the other hand, if it's a relatively new unit, opening the case
would void the warranty, I guess.
--
Derek

If you can't learn to do something well, learn to enjoy doing it
poorly.

Archived from groups: comp.sys.palmtops.pilot (More info?)

I just had the same problem. But the caution about not using the new
driver is not helpful since I actually have the new keyboard that uses
the new driver. And I want to use it!

C

Alan Miller <fpnews@fencepost.net> wrote in message news:<MPG.1bd9f9a55227f354989b65@localhost>...
> Just a note in case my suspicions are correct, so nobody else runs into
> the same thing:
>
> I downloaded and installed the new (10/8/04) Universal Wireless Keyboard
> driver the other day without realizing that it was the driver for a new
> product and *NOT* an updated driver for the IR Wireless keyboard, and
> when I ran it managed to lock the system so hard that even a reset was
> being ignored.
>
> Since it's a character input app and Palm says that it's for the T3, T5
> and other similarly new devices only, I suspect that it ties into the
> Grafitti2 libraries in some way. That means that IF I'm right, anyone
> who's reverted to the older Grafitti with T|T PRCs may have the same
> problem I did - my Palm locked up so hard that I had to wait for the
> battery to completely die and wipe the memory before I could do anything
> with it.
>
> If this happens to you, it only takes a day or two because the T3 locks
> with the screen on. Eventually voltage drops too low to power the
> screen, but it'll keep powering the LED for longer. After that goes out
> you'll probably have to wait another 24 hours or so for the battery to
> get far enough down that the memory clears. Following that you should
> be able to re-hotsync as if you'd done a hard reset (since you have -
> you've done the "dead battery reset" ). If you still have that keyboard
> driver on, when you run it the same thing will happen again, so I'd
> advise either deleting it or just removing keyboard.prc from your Backup
> directory.
>
> Hope this is useful for someone,
> ajm