[bookport] Re: A dead bookport

  • From: "Scott Learned" <learnedtechnology@xxxxxxx>
  • To: <bookport@xxxxxxxxxxxxx>
  • Date: Sun, 12 Feb 2006 11:29:33 -0700

Hi Scott,
before sending  your BP back, remove the CF card and batteries. Let it sit 
for at least 24 hours before reinstalling the batteries  again.

This procedure has helped a number of people in the past.


Scott
----- Original Message ----- 
From: "Scott Rutkowski" <scott@xxxxxxxxxxxx>
To: <bookport@xxxxxxxxxxxxx>
Sent: Sunday, February 12, 2006 9:46 AM
Subject: [bookport] A dead bookport


HI all.

This to me sounds like a dead bookport thought i'd run this by you all
first.

This morning my bookport batteries needed to be replaced.
I removed the batteries carefuly as I have twice before and when I inserted
the new batteries the correct way, I heard the usual sound as if the unit
was gaining power and no speech.

I did however use the d e and f commands before hand and this has worked
fine on 2 previous ocasions.
I tried brand new alcaline batteries from there packaging and unfortunately
no speech after waiting for 2 minutes and putting the batteries back in.

The battery terminals don't feel bent and i've had no trouble in the past.

when I connected the usb cable to the unit to see if it could be recognized,
I recieved the error from windows saying the device is not functioning
correctly or has malfunctioned.

I'm wondering why do these units have problems like this just changing a
couple of batteries only having the unit for less then 3 months and this
happens.

I think the unit definently has a fault and I know others have experienced
similar issues.

I hope the next generation of bookport actually uses springs in the battery
compartment and not those flaky metal connectors that bend so easily
according to others.

I'll await further info from the list but i'll ship my unit back today to
the library who is lending it to me and they can ship me a replacement unit.




__________ NOD32 1.1404 (20060211) Information __________

This message was checked by NOD32 antivirus system.
http://www.eset.com



Other related posts: