Has anyone actually been able to reproduce this problem on a "stock"
Palm V (that is, one WITHOUT Clock III installed)? Furthermore, has
anyone seen this problem (with or without Clock III) on a Palm IIIx?
The Palm IIIx runs the same OS build and is based on a very similar
hardware design as the Palm V.
Without a reproducible case, it's really hard to identify the source
of the problem.
It's interesting that users are cautioned to NOT mention this
additional software when calling 3Com, because MY first response
would be "What third party software is installed?" It's entirely
possible that Clock III's use of the AlarmMgr may be causing the
problem (especially if it won't happen without Clock III installed,
even if it does also occur in the Datebook app). To be fair, it
could also be an issue in Palm OS, whether or not Clock III is
involved.
If anyone has any additional information on this, I'd love to hear it
-- especially before people start claiming that this is a "serious
defect" or "manufacturing glitch" in the Palm V.
--Steve
At 6:40 PM -0500 4/27/99, James wrote:
>We continue to receive reports from customers whose Palm V units do not
>wake up when a Datebook alarm comes due. We have sent numerous email
>messages about the problem to David Fedor and Gabriel Acosta at 3Com, and
>they simply do not acknowledge receiving them. Does anyone else have any
>further information on this serious defect in the Palm V?
>
>FYI, what follows this message is the standard response that we now send to
>all of our customers who encounter this fault.
>
>- James Einolf
>Little Wing Software Development
