I decided to get help from Verizon before trying to install the newer firmware (I guess that's what happens), and they sent me to Palm. After about 1.5 hours of work, discussion with two reps from Palm and waiting for the program to load, I successfully installed the updated 1.05a VZW for this Mac Book Pro. Hope it works; time will tell. It's been about an hour, and no errant resets.
I note that this is a far cry from the way this MacBookPRO Intel updates Apple software. It's entirely an automatic process for all the built in software. On the other hand, Windoze and MS never had such ease of restoring the OS. MS could learn a lot from Palm and Apple besides the look and feel of the desktop. Dave --- In [email protected], "Kevin Bachelder" <[EMAIL PROTECTED]> wrote: > > > I (and others here) have mentioned many times in the past that the #*377 > > (or whatever code you enter) is NOT a completely reliable way to determine > > the cause of a crash. > > My apologies if my earlier message inferred that using that code would > give you a simple answer as to what was causing the problem. > > My intent was to say that it might help give you an idea of where to > look or how to have more information that may be helpful in > troubleshooting the issue especially if you reset your unit back to > factory defaults. > > > Kevin > > -- > If you're a fan of Farscape or Firefly then you'll enjoy listening to > the award winning podcasts... > > The ScapeCast > http://www.scapecast.org > > The Signal > http://www.serenityfirefly.com > > Firefly Talk > http://www.fireflytalk.com > > On 2/7/07, Michael M. Rye <[EMAIL PROTECTED]> wrote: > > > > > > > > I (and others here) have mentioned many times in the past that the #*377 > > (or whatever code you enter) is NOT a completely reliable way to determine > > the cause of a crash. That method only reports the program which happened > > to be running in the foreground at the time of the crash/reset. If you > > have PalmOS enhancements or other programs installed that run in the > > background on the device, one of those background apps could have been the > > real cause of the crash/reset. The code dialing method below will not > > reveal that. > > > > --- > > Michael > > > > ..... Original Message ....... > > > > On Wed, 07 Feb 2007 12:31:00 -0500 Kevin Bachelder > > <[EMAIL PROTECTED]> wrote: > > >Hey Dave, > > > > > >I've had my Treo 650 for about eight months and I don't know how I > > >ever got along without it! > > > > > >However, just like you and many other people my unit will reset itself > > >periodically. There are many discussions on the web about the real > > >cause of the problem. > > > > > >It's my understanding that each carrier has their own code that you > > >can dial from the phone app after a reset to let you know the cause of > > >the most recent crash. On my Cingular device I dial... > > > > > ># * 377 > > > > > >and I get an error description for what caused the last reset. If you > > >are getting the same error each time your unit is resetting then you > > >might have something you can look into. I've been told that the > > >description that I always get is caused by a hardware problem and to > > >troubleshoot it I will need to wipe out my unit and reset to factory > > >defaults without any of my applications and then see if the problem > > >reoccurs. I've just decided to put up with the occasional reset > > >rather than deal with restoring backups or doing without all the cool > > >apps that I use. > > > > > > > > >Good luck, > > > > > >Kevin > > > > > >-- > > >If you're a fan of Farscape or Firefly then you'll enjoy listening to > > >the award winning podcasts... > > > > > >The ScapeCast > > >http://www.scapecast.org > > > > > >The Signal > > >http://www.serenityfirefly.com > > > > > >Firefly Talk > > >http://www.fireflytalk.com > > > > > >On 2/7/07, David Clark <[EMAIL PROTECTED]> wrote: > > > > > > >> I've looked at all the suggestions, and they're almost more trouble > > >> than the problem seems to warrant. I regularly back up the device to > > >> this MacBook Pro Intel, but I'm still concerned that going through the > > >> upgrades for a new OS patch will wipe out the Treo. > > >> > > >> Dave > > >> > > >> --- In [email protected], "Sandro Campos Mancini" <mancini@> > > wrote: > > >> > > > >> > Look for the freeware "MemInfo" to check on your NVFS status and > > >> give the > > >> > freeware "RescoLock" a try. Lock everything that shows with an > > >> exclamation > > >> > mark or with a P (protected) flag and has no L (locked) flag to the > > >> right. > > >> > > > >> > []s > > >> > Sandro Campos Mancini > > >> > > > >> > > > >> > ----- Original Message ----- > > >> > From: "Michael M. Rye" <mrye@> > > >> > To: <[email protected]> > > >> > Sent: Tuesday, February 06, 2007 4:40 PM > > >> > Subject: Re: [Treo] Verizon 650 Treo Resets > > >> > > > >> > > > >> > > The Treo 650 is an unpredictable device that can crash and reset > > >> even with > > >> > > only its own built-in software installed. Welcome to having a > > >> device with > > >> > > one of the first incarnations of NVFS storage. They have been > > >> improved in > > >> > > newer devices like the Treo 700p and the 680. Since you have a > > >> 650, you > > >> > > should read this - > > >> > > > > >> > > http://www.npug.org/forum/showthread.php?p=16535 > > >> > > > > >> > > (You may have to scroll up to get to the top of the article.) > > >> > > > > >> > > --- > > >> > > Mike > > >> > > > > >> > > > > >> > > ..... Original Message ....... > > >> > > On Tue, 06 Feb 2007 18:15:41 +0000 David Clark <dclark@> > > >> > > wrote: > > >> > >>My Verizon Treo 650 resets itself (soft re-boot, or whatever it's > > >> > >>called) without any outside impetus. It's just sitting there on the > > >> > >>desk, when it will reset. It just happened 2 minutes ago. Nothing > > >> > >>seems to be lost, but I'm not even sure of that. > > >> > >> > > >> > >>Outside signals might be coming from Verizon or via ChatterMail, > > which > > >> > >>is set for 10 minute check time. > > >> > >> > > >> > >>Appreciate any advice or help. > > >> > >> > > >> > >>Dave > > >> > > > > > > > >
