[bookport] Re: Mean time between crashes -- is anyone else seeing this as often as I am?
- From: "Richard Ring" <ring.richard@xxxxxxxxxxxxxxxxx>
- To: <bookport@xxxxxxxxxxxxx>
- Date: Mon, 24 Jul 2006 14:12:12 -0500
Like you, Brian, I have experienced some crashes. However, I must say
they are relatively rare. Unfortunately, I don't often look at the
minutes spoken data, I tend to be more concerned with current battery
level information thus my own experiences are useless in terms of
discovering how many hours I am getting out of my Bookport before a
crash.
-----Original Message-----
From: bookport-bounce@xxxxxxxxxxxxx
[mailto:bookport-bounce@xxxxxxxxxxxxx] On Behalf Of Brian Buhrow
Sent: Monday, July 24, 2006 12:19 AM
To: bookport@xxxxxxxxxxxxx
Cc: buhrow@xxxxxxxxxxxxxxxxxxxxx
Subject: [bookport] Mean time between crashes -- is anyone else seeing
this as often as I am?
Hello. I'm really not trying to lodge a complaint against the
Bookport, but I am curious if my experience is atypical from the norm.
I use the spoken minutes meter as a way of measuring the
stability of
my Bookport. That is, I never reset it unless the bookport crashes or
otherwise needs to be reset to factory defaults. So, when I change
batteries, I use the DEF command to save my settings across battery
changes, including the spoken minutes timer.
Over the course of the past year, I've noticed that I have never
been
ab le to get my spoken minutes timer to run over 5,500 minutes or
so. Some
resets ove that time have been due to the need to upgrade the firmware
on
the unit, or because I inadvertently double-connected the batteries
during
a battery change, but more recently, I've been more careful about these
pilot errors, and, yet, I still, see crashes of one sort or another
about
every 100 hours of operation or so.
I'm still running 2.1.0.28(BETA), but I don't think that code is much
different from the 2.2.0 code.
To be sure, the 2.1.0.28 code is much more stable than the
2.1.0.0
code, and it really doesn't affect the usefullness of the device, but it
seems like the device ought to tick along without needing a reset for a
long time.
I'm not trying to perform a scientific study, but I am curious
if
others have gone more than 100 or hours or so between forced resets of
the
unit. Remember, a spoken minutes value of 6,000.00 means that the
device
has been operating for 100 hours. What I'd like to know, if people
con't
mind sharing, is:
1. How often do you have to reset you unit. We're talking in "spoken
minutes time" here, in case it wasn't obvious.
2. What's the longest, in spoken minutes time, you've been abble to kee
from having to reset your Bookports?
I'm not trying to be scientific, anecdodtal evidence will work,
-- I'd
just like to have a better understanding of my fellow Bookport users.
So, let us know what your experience is with the need to reset.
-thanks
-Brian
Other related posts:
