MobileRead Forums - View Single Post

Alan · 07-13-2008, 09:49 AM

Hi,

I want to add my ¢2, too:

I experienced the same problem. After reading a lot of threads about this problem, I believe the file system in my Cybook was corrupt. So far I tried everything, including a firmware flash with version 538. Finally I succeeded.

But after all this also shows me, where the real problems are: If simple reading with the device can destroy the file system (at least this is what I think was causing the problems) rendering the device useless, than something is really, really wrong. Sure, hardware can become defective. This is true for your dishwasher as well as for the Cybook. It's not nice, but it happens.

But software (the supposed cause of these problems) cannot become defective, it can only be defective from the beginning. I am a professional Windows and backup software administrator and have also some basic Linux skills. I know how operating and file systems work. I have seen corrupt NTFS partitions as well as pink screens on Linux machines. File system corruption can occur. But, and this is a big BUT, the Cybook is, compared to the servers I administer, not more than a pocket calculator when it comes to complexity and power. It has only to do some very limited routines. Frankly, using a Linux kernel for a book reader is quite an overkill. But anyway, a device that is out for the mass market as a book reader simply must not have this kind of problem.

I consider myself quite resourceful and I am able to at least try to solve many problems before giving up. But think about the average user. He won't be able to flash firmware nor will he be able to rebuild a file system on his reading device. He will either throw away the device or will go to the painstakingly slow process of contacting Bookeen, requesting an RMA number and sending it to Bookeen.

So I urge Bookeen to look into this kind of problem - the most serious one - in order to prevent future problems of this nature.

Alan

07-13-2008, 09:49 AM	#58
Alan Connoisseur Posts: 55 Karma: 10 Join Date: Dec 2007 Location: Germany Device: Bookeen Cybook Gen3	Hi, I want to add my ¢2, too: I experienced the same problem. After reading a lot of threads about this problem, I believe the file system in my Cybook was corrupt. So far I tried everything, including a firmware flash with version 538. Finally I succeeded. But after all this also shows me, where the real problems are: If simple reading with the device can destroy the file system (at least this is what I think was causing the problems) rendering the device useless, than something is really, really wrong. Sure, hardware can become defective. This is true for your dishwasher as well as for the Cybook. It's not nice, but it happens. But software (the supposed cause of these problems) cannot become defective, it can only be defective from the beginning. I am a professional Windows and backup software administrator and have also some basic Linux skills. I know how operating and file systems work. I have seen corrupt NTFS partitions as well as pink screens on Linux machines. File system corruption can occur. But, and this is a big BUT, the Cybook is, compared to the servers I administer, not more than a pocket calculator when it comes to complexity and power. It has only to do some very limited routines. Frankly, using a Linux kernel for a book reader is quite an overkill. But anyway, a device that is out for the mass market as a book reader simply must not have this kind of problem. I consider myself quite resourceful and I am able to at least try to solve many problems before giving up. But think about the average user. He won't be able to flash firmware nor will he be able to rebuild a file system on his reading device. He will either throw away the device or will go to the painstakingly slow process of contacting Bookeen, requesting an RMA number and sending it to Bookeen. So I urge Bookeen to look into this kind of problem - the most serious one - in order to prevent future problems of this nature. Alan