I'm running G-Palm on a Palm IIIe and I have no problems with it
calibrating. I have run into problems with it powering off while in
autostart, but I think I've traced that problem down. I'm using Hackmaster
to enhance the input (I highly recommend the middlecaps hack, and the menu
hack) among other things, and I think it interferes with G-Palm's override
of the auto-poweroff function. If I disable the hacks, it behaves like it
should.
You might ask your customer if they have any hacks running. I won't pretend
to know how the hacks work, but I'd bet they could cause a problem such as
this. The only other thing I could suggest is to check the power module for
defects, and the battery - but I'm sure that you've done that already.
-Brian Meyer
Byron Short wrote:
> Hey Guys,
>
> Is anyone out there using the G-Cube with a new Palm IIIe? I know
> there's not supposed to be any meaningful processor or language
> differences in the IIIe, but I have a user with problems we can't seem
> to resolve. I've already had him replace the IIIe, the HotSync cable,
> and I've replaced the Cube, power module, cables, etc...but we still
> have problems.
>
> When we try to calibrate we consistently get random 5 digit numbers in
> the calibration string. The same cube calibrates fine on my Palm III,
> and calibrates fine on the customer's PC. It also records fine on the
> customer's Palm; using testing tools we can even review the data at it's
> lowest level (before it gets turned into a GCD file) and see that it's
> all okay. It just refuses to calibrate. Anyone else seen this problem
> on any machine at all?
>
> Anyone have any ideas? This one has me stumped!
>
> THANKS for any help!
>
> --Byron
|