The latest BeBook firmware has dropped DRM-ed (encrypted) MOBI support in favour of DRM-ed Adobe ePub/PDF support. The DRM-free MOBI reader in the new firmware acts like the old one, and you still have the option of using the old MOBI firmware anyway. With the new firmware, converting to ePub is also a possibility. This also should have no problems with large files, providing you convert them to ePub using Calibre, because Adobe's reader only processes one "chapter" at a time (and Calibre adds in fake chapters if needed to keep the processed file sizes withing Adobe's limits).

The latest BeBook firmware has dropped DRM-ed (encrypted) MOBI support in favour of DRM-ed Adobe ePub/PDF support. The DRM-free MOBI reader in the new firmware acts like the old one, and you still have the option of using the old MOBI firmware anyway. With the new firmware, converting to ePub is also a possibility. This also should have no problems with large files, providing you convert them to ePub using Calibre, because Adobe's reader only processes one "chapter" at a time (and Calibre adds in fake chapters if needed to keep the processed file sizes withing Adobe's limits).

The ADE viewer that's now being released on all the current devices (BeBook, Opus, etc) appears no longer to have the 260k "flow limit" that the old viewer on the Sony had.

It's the MobiPocket Java-based one if I remember correctly. Havent read all that many mobi books on my bebook due to the fact that it tends to crash more frequently than for instance RTF does. Even though there are some crashes with RTF as well.

It's the MobiPocket Java-based one if I remember correctly. Havent read all that many mobi books on my bebook due to the fact that it tends to crash more frequently than for instance RTF does. Even though there are some crashes with RTF as well.

So this would imply that it is possible to use MobiPocket code without DRM support. Then you can wonder why Bookeen does not do that?