Paul,
Before you start writing such inflammatory messages, remember that you don't
know all the facts! . . .. I don't. Probably no one person does!
To be honest, I am sick and tired of hearing the same people writing time
and again about their displeasure in the bugs found. I'm equally annoyed
for all sorts of reasons about this but, with the perplexity of reasons for
this bad and "buggy" release (which have to include the loss of Dean and
Jonathan), I'm not even going to comment on the rights and wrongs of the
situation on list.
I'm just asking that you, please, don't continue to thrash this one around.
It's certainly beginning to sound like a worn record now and I can't see
what you're achieving, even if you, like so many of us, are frustrated by
the situation in which we are placed.
If you want to do something positive:
1) take the time to make a whole list of those bugs you have found or
tested and those that others have found that you can verify and send the
list to Humanware.;
2) Try to give people positive feedback to problems they now encounter;
and
3) Go back to 7.0 and wait! Others appear to have gone back to 7.0 quite
happily so, if you don't like the first two options then I suggest you take
this one.
I don't usually write in this way but enough is enough, please!
--
Carol
[EMAIL PROTECTED]
----- Original Message -----
From: "Paul Henrichsen" <[EMAIL PROTECTED]>
To: "'Braillenote List'" <[email protected]>
Sent: Friday, September 15, 2006 6:42 AM
Subject: [Braillenote] adding my voice to 7.2 concerns
Hi, everyone. Although I have also seen problems with the daisy reader, a
reset usually fixed the problem. I had heard people's concerns with
getting
a low battery warning at a high percentage of battery life. I couldn't
speak
to this as my battery hadn't drained down since I had upgraded. However,
Now
I can.
I got my battery down to 30 percent and was told this with read escape. I
read a few chapters of a book then went to load another. Without any
warning
of battery low or critical, my braille note reset itself. I had to do a
service reset to get it started again. I had to reset the clock.
After coming up in the main menu, a read escape told me I was at one
percent.
How in the world could I have dropped from 30 percent to one percent in 15
minutes?
I have never had this problem until upgrading to 7.2.
It just amazes me how HW could put out an upgrade which is so blatantly
full
of bugs.
I am astounded that a product could be beta tested for over eight weeks
and
no one reported such obvious problems as the daisy book reader or
battery
issues, nor the various other problems we have found since the release of
this upgrade.
If I had been allowed to be on the beta team, this would not have happened
under my watch, I can assure you, not if I had any say in the matter. I
have
a masters degree in business with an emphasis in information systems and a
bachelor in computer applications and systems.
If I had handed in programs with major bugs in them like this, my
professors
would have given me an f.
I said this three years ago on this list to Larry Lewis when users were
finding numerous flaws in that version of keysoft.
I cannot imagine why HW would hand such flawed code to their users.
If these guys were in school and handing this stuff to their professors,
do
they think it would be tolerated? Don't they have any pride in their work?
I was really excited when this upgrade came out. Now, I wish I had stayed
at
7.01 and hadn't upgraded.
Paul Henrichsen
<[EMAIL PROTECTED]>
___
To leave the BrailleNote list, send a blank message to
[EMAIL PROTECTED]
To view the list archives or change your preferences, visit
http://list.humanware.com/mailman/listinfo/braillenote
___
To leave the BrailleNote list, send a blank message to
[EMAIL PROTECTED]
To view the list archives or change your preferences, visit
http://list.humanware.com/mailman/listinfo/braillenote
