The Cybook Frame made me wonder if you can now read while using external power?

[HarryT]

Originally Posted by adelheid

I beg your pardon? You are not serious, are you?

Er, yes, I am.

[DDHarriman]

Thank you very much HarryT, those are really great news!

And thank you for the outstanding contributions you have been putting all over this forum - your posts where mandatory in my decision to buy the Cybook.

Best reagrds,

[HarryT]

My celebrations are "on hold" until I actually SEE the update and find out what's in it . But yes, having a date for it is good news.

[tompe]

Originally Posted by HarryT

I'd forgotten about that bug, Tommy - yes, that one IS major, I agree with you. Can it happen, though, on books which meet the Mobi spec of images <64k in size

Yes, it seems more related to the actual image size than the file size.

BTW, After the messages on this thread I wrote to "support@bookeen.com" yesterday afternoon and asked when the next firmware release was due. I got an answer within the hour to say that it would be released in March.

I think they might have created a "support department" now since my response was signed with something like that. That might mean that things have become better now.

[ProfJulie]

Originally Posted by HarryT

My celebrations are "on hold" until I actually SEE the update and find out what's in it . But yes, having a date for it is good news.

Having a date is only good news if it is real.....I was encouraged when I received an email from Bookeen around the 1st of January that gave a "few weeks" timeframe.....So now I reset my expectations to the end of March. we'll see what happens.

[HarryT]

Originally Posted by ProfJulie

Having a date is only good news if it is real.....I was encouraged when I received an email from Bookeen around the 1st of January that gave a "few weeks" timeframe.....So now I reset my expectations to the end of March. we'll see what happens.

I agree with you completely - let's hope that the March release date is an accurate one.

[JSWolf]

I thought that it was image size and not file size that was the issue. Because there can be large images less then 64k in filesize.

[HarryT]

Originally Posted by JSWolf

I thought that it was image size and not file size that was the issue. Because there can be large images less then 64k in filesize.

I think there are two separate issues, Jon. Some MobiPocket platforms (eg Palm machines) won't handle images >64k (although the Gen3 appears to handle them without difficulty). There seems to be an entirely separate issue specific to the Gen3 concerning image dimensions, rather than file size.

[JSWolf]

What I could do is the next PRC I make make it with different size cover images and then let the gen3 owners soo when it locks up to know what size is too big.

[tompe]

Originally Posted by JSWolf

What I could do is the next PRC I make make it with different size cover images and then let the gen3 owners soo when it locks up to know what size is too big.

It is probably not so simple. I did try to test a lot of sizes to find if there was a limit but the result was not consistent. Sometime a large image works and sometimes i does not work. And even for problematic images the maximum size varied. For MobiPerl I took a size that never caused problem for me and used that as a maximum.

This is something that is very time consuming to test as a user but probably very easy for Bookeen to debug since it is totally reproducable and they have been sent test cases.

[JSWolf]

What is the largest size image you've constantly had work in a Mobipocket format eBook?

[tompe]

Originally Posted by JSWolf

What is the largest size image you've constantly had work in a Mobipocket format eBook?

480x640 and number of bytes less than 61000.

[DDHarriman]

800x600 grey jpeg and 91 kbytes.

Have just created a new eBook with this front page today and zero problems.

[tompe]

Originally Posted by DDHarriman

800x600 grey jpeg and 91 kbytes.

Have just created a new eBook with this front page today and zero problems.

As I said. There is cases were this work or even larger images. The limit was the limit that always work according to empirical observations.

[HarryT]

Originally Posted by ProfJulie

I agree with you in principle. But I have an email from Bookeen, dated January 3, 2008, which states:

"We will release in the next few weeks a software upgrade which fixes at least the first issue. We have no final release date yet, but we work to find a definitive solution to the bookmark issue and integrate it at the same time."

In accordance with their email message to me, I start expecting to see a firmware update around mid to late January.

As we are discussing in another thread, it seems that they did exactly what they said they would - released a firmware upgrade (build 538) around mid January which does indeed appear to have fixed at least the majority of the reported bugs. If you write to "support@bookeen.com" and request it, they'll send you reflash instructions.

The reason it's not been publicized is that this is just an "intermediate" release which fixes bugs rather than add any new features, and all new Gen3's are being shipped with the new firmware. Anyone who reports "old" bugs now (as I did) appears to be being sent the reflash instructions.