A firmware bug in the Treo-500v causes all applications to receive a
spurious private message 0x00008017 after a phone call is performed from the
device.

This message is normally in a range reserved for private communication
between the threads of an application and should never be sent to an
application by the system, the shell, or any other software on the device.
This firmware bug can cause random application crashes and other issues.

This issue exists in various other windows mobile devices and was reported
to microsoft two years ago (first spotted on the Motorola Q), but apparently
microsoft still does not include testing for this firmware bug in their
platform validation tests, and we see it popping regularly on new devices.

More information can be found here:
http://www.modaco.com/content/Window...-firmware-bug/

any comment on that from MSFT or a MVP?

this is a serious firmware bug, and it's surprising to still find it in new
devices... platform tests certainely don't catch it.

"The PocketTV Team" <support@pockettv.com> wrote in message
news:O2UdwVImIHA.1680@TK2MSFTNGP06.phx.gbl...
>A firmware bug in the Treo-500v causes all applications to receive a
>spurious private message 0x00008017 after a phone call is performed from
>the device.
>
> This message is normally in a range reserved for private communication
> between the threads of an application and should never be sent to an
> application by the system, the shell, or any other software on the device.
> This firmware bug can cause random application crashes and other issues.
>
> This issue exists in various other windows mobile devices and was reported
> to microsoft two years ago (first spotted on the Motorola Q), but
> apparently microsoft still does not include testing for this firmware bug
> in their platform validation tests, and we see it popping regularly on new
> devices.
>
> More information can be found here:
> http://www.modaco.com/content/Window...-firmware-bug/
>