[bookport] Re: More transfer errors
- From: "Cheryl and Dash Lenartiene" <Dashman@xxxxxxxxxxxx>
- To: <bookport@xxxxxxxxxxxxx>
- Date: Mon, 18 Apr 2005 11:29:31 -0400
Hi Rob,
Thanks for the advice (and Larry, too). If it's a bad card, that is
easily remedied. As I had said before, if I had made some fatal mistake, or
if there was some strange bug in the firmware, I didn't want to purchase
another big card and have the same thing happen. While I realize there are
no guarantees in life, the fact that you are relatively confident that it's
not the firmware, or anything I might have done, is a big confidence
booster. I will contact the manufacturer about getting a replacement.
Cheryl
----- Original Message -----
From: "ROB MEREDITH" <rmeredith@xxxxxxx>
To: <bookport@xxxxxxxxxxxxx>
Sent: Monday, April 18, 2005 11:15 AM
Subject: [bookport] Re: More transfer errors
> Cheryl:
>
> That number of bytes written was for the current block, not the entire
> transfer. So, 0 is an OK number here. I think I would pursue getting a
> replacement for the card.
>
> Rob Meredith
>
>>>> Dashman@xxxxxxxxxxxx 04/18/05 10:54AM >>>
> I'm sorry. I got a card full condition, and hit to hit OK in BP
> transfer. I went ahead and checked the properties of the card through
>
> Windows Explorer, and it said bytes used: 0; bytes free: 0. I
> unplugged the
> BP. It said OK GGGGGGB. I could not press any keys; they were
> unresponsive. I pulled the batteries, and reset the BP. It then
> became
> fully functional.
> Now, an interesting note. BP Transfer had reported that it had
> written
> 0 bytes to the card when I got the card full error at 47% of the
> transfer
> process. It gave a requested byte count but said it was unable to
> write
> that count to the card. However, part of that file is actually on my
> card,
> about 4MB worth. Let me know if I can answer any more questions.
> Cheryl
> ----- Original Message -----
> From: "ROB MEREDITH" <rmeredith@xxxxxxx>
> To: <bookport@xxxxxxxxxxxxx>
> Sent: Monday, April 18, 2005 10:31 AM
> Subject: [bookport] Re: More transfer errors
>
>
>> When you say it locked up at 47%, what do you mean? Can you cancel
> at
>> this point? Does disconnecting allow you to regain control of Book
> Port
>> Transfer?
>>
>> It sounds like a bad card.
>>
>>>>> Dashman@xxxxxxxxxxxx 04/18/05 10:21AM >>>
>> Rob,
>> Sorry for the delay in responding, but I have some very strange
>> results. The root directory of my card had the BP manual, and the
>> notes
>> folder. I had also created two folders: audio and bible. The Bible
>> folder
>> has no subfolders and consists of 66 text files. The Audio folder
> has
>> a
>> Bible folder and a books folder. The books folder has Audible files
>> and no
>> subfolders. The Bible folder consists of 4 subfolders, each
> containing
>> an
>> average of 20 audio files (MP3s).
>> Okay, so I had 372 MB free. I was able to send one 9.54MB MP3
>> file to
>> the root of the Audio folder. I tried to send the second one (10MB)
>> and it
>> locked up at 47%. I unplugged the BP, and it said OK GGGGGGB. I
> had
>> to
>> pull the batteries to reset.
>> Next, I plugged it back in, created a temp folder in the root
>> directory, and sent about 140 small text and Braille files to it.
> They
>> all
>> sent fine. I sent a couple of folders containing .BRF files, and
> they
>> sent
>> fine. I then sent a bunch of MP3s to this folder, and they all sent
>> fine.
>> I'm now down to 267 MB free.
>> When we tested with the reader yesterday, and not the BP, we
>> formatted
>> the card and just sent a bunch of MP3s to the root directory. It
> would
>> lock
>> up around 363-358 MB free. I also tried recording a memo with 367
> MB
>> free
>> on the BP, and it locked up after about 10 minutes, and I got a file
>> recording error.
>> So, any thoughts. Very, very strange.
>> Cheryl
>> ----- Original Message -----
>> From: "ROB MEREDITH" <rmeredith@xxxxxxx>
>> To: <bookport@xxxxxxxxxxxxx>
>> Sent: Monday, April 18, 2005 8:21 AM
>> Subject: [bookport] Re: More transfer errors
>>
>>
>>> Try disconnecting all other USB devices from your computer, and see
>> if
>>> you can copy enough to the card that you get less than 363MB free.
>> You
>>> can use the card reader or the BP to test this.
>>>
>>> Rob Meredith
>>>
>>>>>> Dashman@xxxxxxxxxxxx 04/18/05 04:32AM >>>
>>> Hello everyone,
>>> This is primarily addressed to the folks at APH. I started
>>> drafting this message Friday night. Note: I am using a Lexar 1 GB
>>> card.
>>> OK, since my last message, the unit has been locking up on the
>>> same file each time. I tried sending the files one at a time, and
>> got
>>> the same results. This time, I was able to write down the
> following
>>> additional BP errors:
>>> Card insertion error; ......; saving voice recording
>>> Firmware Error Conditioning Y#N RZV at line number 29698. Press the
>> 0
>>> key to reset BookPort.
>>>
>>> Preceding this, the transfer software forze in the middle of
>>> sending this one specific file, and when I hit Cancel, reported
> that
>> the
>>> flash card was full; it is not. I never removed or reinserted the
>> card.
>>> Also, the 0 key would not reset the BP. I had to remove the
>> batteries
>>> to force a reset. The firmware conditioning error occurred more
>> than
>>> once, but has not occurred since Friday, though much additional
>> testing
>>> was done.
>>> What I have found, with extensive testing over the weekend, is
>>> that the card seems to have become partially corrupt. I can fit
>> over
>>> 600 MB on the card, but wants I get down to about 363 MB free,
>> nothing
>>> else will go on the card. BP Transfer reports a card full
>> condition,
>>> and CF readers report that the device is not ready. I have tried
>> using
>>> the BP and the PC to reformat the card. Once, I even tried
>> reformatting
>>> it as a FAT32 (then sent files to it from the PC's card reader),
> and
>> got
>>> the same results. I've tried running ScanDisk and the BP
> Transfer's
>> Fix
>>> Errors utility on the card, but to no avail.
>>> This card is just a couple of weeks old, so I can't imagine it
>>> would have gone bad. Can anyone at APH provide insight into the
>> error
>>> message above, and what may have possibly happened? I don't want
> to
>> put
>>> money into another 1 GB card until I at least have an idea if I did
>>> something wrong, or what might have happened. I am happy to answer
>> any
>>> questions to help clarify the situation.
>>>
>>> Thanks,
>>> Cheryl
>>>
>>>
>>>
>>
>>
>>
>>
>>
>
>
>
>
>
Other related posts:
