New Jinke firmware V2.01EN

[javimm]

Just released today. From the Jinke's page:

Cheers,

V3update hanlin V2.01EN 2008-11-21
Description:

1. Add pdb parser
2. Update chm parser
3. Update pdf parser
4. Update epub parser and epub parser support catalog operation.
5.Support pdb files which use "REAd" as create id
6.Update makeup effection of mobi files.
7.Support readable pdb files recognize automatically.

[mvoosten]

nice, thx

[delphidb96]

Thnx. But I keep getting *NOTHING* when I click to download the file. I mean, eventually the web page appears and nothing further. No prompt for accepting a file, no progress dialog showing the (non or otherwise)completion of the download process and no file.

Derek

[torbich]

delphidb96 Works for me (under Firefox browser).

[javimm]

I downloaded it with no problems, apart from the slow speed of the chinese server. Haven't tried it yet. I'm going to flash it now.

[delphidb96]

So could someone email me a copy or post a copy to RapidShare for me to download?

Derek

[Trono]

Does anybody know what the status are on the Hanlin firmware regarding support of fb2-files drm'd mobipocket..? I've been using the Bebook firmware for a while now because of these features

[Moe The Cat]

Originally Posted by delphidb96

... post a copy to RapidShare ...

Derek, it is posted on Rapidshare here.

[DaleDe]

Originally Posted by Trono

Does anybody know what the status are on the Hanlin firmware regarding support of fb2-files drm'd mobipocket..? I've been using the Bebook firmware for a while now because of these features

Both have been supported for several months now.

Dale

[delphidb96]

Originally Posted by Moe The Cat

Derek, it is posted on Rapidshare here.

Thank you! Thank you! Thank you!

Derek

[Trono]

Originally Posted by DaleDe

Both have been supported for several months now.

Dale

Thanks Dale. I made the jump, and you are correct - mobi and fb2 is still readable

I was, however, rooting for something else as well, regarding pdb-files. Seeing it mentioned several places in the list got my hopes up.

Question - again - is due to my long list of books bought at eReader.com. My understanding so far is that it is unlikely that the "secure files" will be readable (ever?) on the e-ink devices. I was, however, hoping that 1, 5 and/or 7 in the list would mean I could read the none-drm'ed ones on my V3. This, I find, is not the case, and I'd like to learn what these improvements in the Hanlin firmware list actually does:

1. Add pdb parser
....
5.Support pdb files which use "REAd" as create id
..
7.Support readable pdb files recognize automatically

Can anyone explain?

[wallcraft]

Originally Posted by Trono

Question - again - is due to my long list of books bought at eReader.com. My understanding so far is that it is unlikely that the "secure files" will be readable (ever?) on the e-ink devices. I was, however, hoping that 1, 5 and/or 7 in the list would mean I could read the none-drm'ed ones on my V3. This, I find, is not the case, and I'd like to learn what these improvements in the Hanlin firmware list actually does:

1. Add pdb parser
....
5.Support pdb files which use "REAd" as create id
..
7.Support readable pdb files recognize automatically

Can anyone explain?

The PDB format is used by many applications on Palm devices, including several ebook formats. These are not the same internally, and they are initially distinguishable using an internal file code, see Wiki: PDB. The TEXtREAd code identifies PalmDOC ebooks, which is one of the commonest formats.

MobiPocket requires DRM exclusivity on dedicated reading devices that support its DRM. So you won't see eReader DRM capability on the V3. Your best option is to use ereader2html to convert your DRMed ebooks to HTML and then format shift the HTML to whatever is best on the V3.

[pilotbob]

Originally Posted by Trono

Question - again - is due to my long list of books bought at eReader.com. My understanding so far is that it is unlikely that the "secure files" will be readable (ever?) on the e-ink devices.

Maybe, maybe not. It is possible that OpenInk Pot will support it. It is also still "possible" that Astak will come through with a version that has eInk on it.

What is most likley is that in the future as small CPUs get more powerful that some device will have a more generic OS which allows you to install reader software that you want on it, rather than just what comes built in.

But, until then, you can always strip the DRM from your eReader files in order to read them on your eInk device.

BOb

[DaleDe]

Originally Posted by Trono

Thanks Dale. I made the jump, and you are correct - mobi and fb2 is still readable

I was, however, rooting for something else as well, regarding pdb-files. Seeing it mentioned several places in the list got my hopes up.

Question - again - is due to my long list of books bought at eReader.com. My understanding so far is that it is unlikely that the "secure files" will be readable (ever?) on the e-ink devices. I was, however, hoping that 1, 5 and/or 7 in the list would mean I could read the none-drm'ed ones on my V3. This, I find, is not the case, and I'd like to learn what these improvements in the Hanlin firmware list actually does:

1. Add pdb parser
....
5.Support pdb files which use "REAd" as create id
..
7.Support readable pdb files recognize automatically

Can anyone explain?

The Aztak mentor device will been shown at CES in January. It is rumored that it will be able to read eReader files. All Palm derived formats typically has the ability to read PDB files with the REAd creator id in addition to whatever format they are designed for. In a few cases the porting to a new device misses this fact and forgets to allow this format. Such was the case here and Mobipocket format is a superset of basic PalmDOC so just permitting it to read this format was enough to make it work. eReader format is a different superset of basic PalmDOC.

Dale

[redbaron101]

hmmm, I presumed the bebooks firmware was just jinkes firmware with extras, but their last update was also 2.01NL (i presume NL for Netherlands). Could it be that bebooks firmware is just jinkes firmware with their logo on it? Im using bebooks firmware, and was surprised when I could use jinkes logomaker to add custom startup/shutdown screen on the bebook firmware.