Hi, when i turn on the device, in the middle of the screen appears a black cross, and the ebookwise remains blocked in this way.
Please, someone help me!
Mauperio from Italy
Hi Mauperio,
Can you give us a little more context? Did you just buy an EB1150, and if so, did it display the cross right out of the box? Is it a new unit or a used unit? Have you tried the manual reset button?
The only place I've ever heard about a cross appearing on the screen is on the comments section of an EB1150 review from 2005, when a user accidentally removed a Smartmedia card from the reader while it was turned on. Check out: <
http://www.bradenslen.com/uncategorized/another-review-of-the-ebookwise-eb-1150/>.
It sounds like his solution involved a firmware update, but I don't know anything about how that worked. Your best bet might be to contact ETI directly, as they have excellent customer service (in my experience). Their email address is <support@ebookwise.com>. Hope this hopes, and good luck on this strange problem.
In effect the problem was about firmware, i have charged it again and the device is working.
Thank you for your advice!
Ah, I was wondering if it was in "calibration" mode! Glad you got it working.
That's great news, mauperio, you're welcome. So did you have to contact ETI to get the firmware?
I'm now getting that on 2 of my devices. I've tried the reset, removed the battery - still same results when powering on.
I tried the 4.2f17 version of the files used for migrating GEB1150 to EB1150 hoping that the device would flash to an older version of the firmware. No success.
Anyone know where I can find the 4.2f25 version of the files or of another method to recover from this error?
I only just noticed that version was on mine. I never had to download it. I thought it downloaded on its own when connected to the computer.
Have you tried reinstalling from
http://www.ebooksystem.net/support_usbdriver_download.htm?
I strongly suggest you contact their support:
support@wildethechnologies.netThey are great!
Your link is for the USB drivers.
I did get my hands on 4.2f25 binary files that I then put on a SM card and flashed the device. It did solve the issue.
