[bookport] Re: braille input for search string?
- From: "ROB MEREDITH" <rmeredith@xxxxxxx>
- To: <bookport@xxxxxxxxxxxxx>
- Date: Fri, 01 Apr 2005 16:29:32 -0500
Kaari:
If all of your keys work, and you have firmware 1.2.0, it should (must)
work. Try locking the unit and pressing all keys to be sure you get a
beep for all 18 keys. If all keys work, and they perform their normal
functions when unlocked, I can't imagine why the command to enter a
Braille find string wouldn't work.
Rob Meredith
>>> kparrish@xxxxxxxxxxxxxxx 04/01/05 01:56PM >>>
Nice to hear someone else has trouble with this. Mine won't go into
braille
mode at all. I'm not running any beta software, either, but I do have
the
latest regular firmware. I've tried rotating the BP both directions,
pressing keys all together, one at a time, anything, but it stays
silent and
refuses to even enter braille mode.
Can anything fix this? Will the next firmware upgrade take care of
it?
Or do I need to have this working before I go to the next update?
Would
adding some of the betas take care of it?
Thanks lots
Kaari
----- Original Message -----
From: "Steve" <srobertson4@xxxxxxxxx>
To: <bookport@xxxxxxxxxxxxx>
Sent: Wednesday, March 30, 2005 2:07 PM
Subject: [bookport] braille input for search string?
> HI listers.
>
> I'll try to make this as clear as I can. It seems my Bookport isn't
> working with the find text feature. Please note, am not running the
> beta verssions. I went to the book port manual, pressed and held key
1
> to go to the top of the file. Rotated the book port 90 degrees with
> the flash card facing toward me. I pressed left spacebar and dots 1
2
> 4 or the leter "f" and wrote the search term "braille" without the
> quotes and hit the enter key which I understood to be the far right
key
> in the middle row. Book Port said "exiting braille mode" and I
> expected to be moved to the first instance of the word "braille" in
the
> manual. Instead I remained at the top or beginning of the file.
> Again, I tried the same steps using the word "agree" as my search
> string and still nothing happened. I'm sure I'm either not
> understanding this feature well or am missing something that is
> glaringly obvious, stupid though it may be, <grin>, can someone tell
me
> what I'm doing wrong?
>
> Thanks!
>
> Steve
>
> srobertson4@xxxxxxxxx
>
>
>
>
Other related posts:
