At 12:59 PM -0700 2001/06/28, Scott Johnson (Bellevue) wrote:
> > From: Jim Schram [mailto:[EMAIL PROTECTED]]
>> You beam the Installer application, not the System Update.
>
>Right, but I was pointing out that an end user could helpfully try to beam
>the final update itself to someone else because it appears in the beam list
>and is not beam-protected.
Hmmm... good point. Historically, System Updates have never been beam protected (to my
knowledge anyway).
> > (Curious why would you expect a serial driver prc to be beamed
>> along with an update prc?)
>
>You misunderstood -- realizing exactly what does and doesn't get beamed, I
>was asking if it's a bad thing that the end user could end up with the new
>update but not the new driver. Is there any critical dependency between
>them?
Doh! Brain... needs... more... caffeine... :oS
I believe the only side effect is that the hardware flow control bug will not be
fixed. This particular fix has two components. One part of it lives in the System
Update prc and involves patches to the Serial Manager and Modem Manager, and the other
part lives in a device-specific serial driver and involves changes to the way it
enables and disables the hardware flow control lines. Without both of these
components, serial flow control remains problematic.
The user should be able to run the Installer application again to correct this problem
and install the necessary serial driver.
Regards,
Jim Schram
Palm Incorporated
Partner Engineering
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
