Mobipocket Decoder Tool - Page 11

igorsk · 10-24-2008, 06:34 PM

Something like this should work out of box, though it's not very pretty:

Code:

fc /N mobidedrm04.py mobidedrm04_1.py

See fc/? for more options.

pthwaite · 10-25-2008, 03:36 PM

Well I've just successfully, after a lot of reading and running Pdurrant's little script, done my first de drm

Like most of you, I don't mind paying for books, but I feel it is up to me what I do after I've got them, ie swap, share. or throw out etc. DRM stifles the spread of literature

JSWolf · 10-25-2008, 07:45 PM

Quote:

Originally Posted by robcohen

It probably wouldn't be difficult to port diff from *nix over to Windows. I'm surprised this hasn't been done by someone. Not that it would be trivial for me necessarily, but sort of recall some info about diff from an intro programming class decades ago :=)

I use WindowsXP Pro and I have a program called ExamDiff. There is a pro version you can purchase, but I find the non-pro version just fine for my needs.

http://www.prestosoft.com/edp_examdiff.asp

adinb · 11-14-2008, 01:48 AM

Hmm, looks like I've run across a fictionwise mobipocket book that doesn't successfully decrypt (though the script runs/works fine).

I've successfully utilized mobidedrm many times -- and reran the scripts against old books just to make sure I hadn't dorked something up. I also brought out fresh versions of the scripts just to make absolutely sure.

Inspecting the file with a hex editor, everything looks good until a bit after the <head> element, with parts of text that are fine and parts that are garbled. Looks like either something odd with the copy I bought from fictionwise, or there's a weird variant that the script isn't picking up.

Since I'm on OSX, I'm sorta hosed for reading my book -- anyone out there interested in taking a gander at before/after versions of the book? This might be something that a certain someone might want to take a look at for additions to the script.

JSWolf · 11-14-2008, 02:52 AM

If you only have MobiDeDRM.py version 0.01 or 0.02 then yes, that sort of thing can happen where it appears to run with no error, but the resulting eBook is hosed. Only 0.04 has so far not had any errors that I know of.

So if you have 0.01, you also need 0.02 and if you have 0.02, you want to find the thread here with the patches to apply to convert 0.02 into 0.04.

adinb · 11-14-2008, 05:18 AM

nope, I'm ran it against V4 (old books and new) *as well as* virgin V1 & V2 scripts with no dice.

From what I got partially running in crossover (my parallels machine is at home), the file appears to be valid encrypted mobipocket (though I'm not 100% sure since running inside a crossover bottle is a finicky affair).

So, it looks to be a mobipocket variant that's potentially not being handled by the script. Hmmm.

pdurrant · 11-14-2008, 10:47 AM

Having looked at this, it seems that there is no problem with the decoded ebook, but just a bug in the Stanza desktop reader.

Quote:

Originally Posted by adinb

nope, I'm ran it against V4 (old books and new) *as well as* virgin V1 & V2 scripts with no dice.

From what I got partially running in crossover (my parallels machine is at home), the file appears to be valid encrypted mobipocket (though I'm not 100% sure since running inside a crossover bottle is a finicky affair).

So, it looks to be a mobipocket variant that's potentially not being handled by the script. Hmmm.

JSWolf · 11-14-2008, 01:16 PM

That would have solved all the problems had we known that Stanza buggered it up. In order to verify that a Mobipocket eBook works properly is to view it using official software such as Mobipocket Desktop.

pilotbob · 11-14-2008, 01:21 PM

Quote:

Originally Posted by JSWolf

In order to verify that a Mobipocket eBook works properly is to view it using official software such as Mobipocket Desktop.

Which doesn't run on a Mac.

BOb

adinb · 11-14-2008, 05:18 PM

Quote:

Originally Posted by JSWolf

That would have solved all the problems had we known that Stanza buggered it up. In order to verify that a Mobipocket eBook works properly is to view it using official software such as Mobipocket Desktop.

Which I would have attempted to do if I were at home with parallels installed. As it is, I'm on the road on a family emergency and the best I could try was crossover pro, which works with mobipocket *except* for the actual display panes.

If mobipocket reader worked on OS X (::hint:: ::hint::!), I wouldn't have a need to use the scripts in the first place.

As it is, I tried to confirm the format by comparing different .prc mobipocket books in a hex editor (something that most users wouldn't do). I was thrown off by several books having a fairly simple ascii/unicode html layout...and this book *not* following a similar layout.

Many thanks to @pdurrant for his assistance last night in helping check the validity of the output file.

It looks like mobitohtml is stable/robust enough to use as a validity checker in situations where the official mobipocket reader is unavailable. (which is my lesson learned out of this). The only downside to using mobitohtml (IMHO) is that you lose a lot of the metadata tags.

The bug has been emailed to the stanza team (though I haven't received ack from them yet), so hopefully this particular issue will be resolved.

@JSWolf -- OT, and maybe a followup should be a thread link, but what tool would you use on OSX to verify mobipocket validity when the official reader isn't available?

wallcraft · 11-14-2008, 07:30 PM

Quote:

Originally Posted by adinb

what tool would you use on OSX to verify mobipocket validity when the official reader isn't available?

You might try FBReader, but it does not read MOBI files with high compression. The other option is to use Calibre and convert the MOBI to ePub. The ePub is then readable by Stanza, FBReader, Calibre, and Adobe Digital Editions.

pilotbob · 11-14-2008, 07:44 PM

Quote:

Originally Posted by wallcraft

You might try FBReader, but it does not read MOBI files with high compression. The other option is to use Calibre and convert the MOBI to ePub. The ePub is then readable by Stanza, FBReader, Calibre, and Adobe Digital Editions.

Actually, I think the newest version of calibre will display a mobi file in its new webkit based viewer.

BOb

JSWolf · 11-15-2008, 05:58 AM

Quote:

Originally Posted by adinb

@JSWolf -- OT, and maybe a followup should be a thread link, but what tool would you use on OSX to verify mobipocket validity when the official reader isn't available?

One thing you could do is to install Calibre and use mobi2oeb and see if the resulting HTML is good. If it is, then you'll know the file is good.

My guess is that you may have been comparing standard compress Mobi to a huffdic compressed Mobi and that would be why things looked different enough to suspect the eBook was corrupted. Could be that Stanza does not handle the higher compression.

IceHand · 11-15-2008, 06:04 AM

Quote:

Originally Posted by adinb

It looks like mobitohtml is stable/robust enough to use as a validity checker in situations where the official mobipocket reader is unavailable. (which is my lesson learned out of this). The only downside to using mobitohtml (IMHO) is that you lose a lot of the metadata tags.

Calibre's mobi2oeb is a better choice—you don't lose the meta tags and it works with huffdic compression too.

Btw, I have Mobipocket Reader running on Linux with Wine. You could try if it works for you with the latest version of Wine for Mac OSX.

AZed · 11-15-2008, 01:17 PM

Quote:

Originally Posted by IceHand

Calibre's mobi2oeb is a better choice—you don't lose the meta tags and it works with huffdic compression too.

Just to toot my own horn a bit, I'd point out the EBook::Tools unpacker keeps even more metadata than mobi2oeb, and as of v0.3.0 (just uploaded to CPAN, not yet indexed), supports HUFF/CDIC as well.

10-24-2008, 06:34 PM	#151
igorsk Wizard Posts: 3,442 Karma: 300001 Join Date: Sep 2006 Location: Belgium Device: PRS-500/505/700, Kindle, Cybook Gen3, Words Gear	Something like this should work out of box, though it's not very pretty: Code: fc /N mobidedrm04.py mobidedrm04_1.py See fc/? for more options.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
New Epub/Mobipocket creation tool: Jutoh	Julian Smart	ePub	78	03-28-2014 07:28 AM
eReader Decoder Tool	wallcraft	Workshop	177	09-27-2009 08:46 PM
Secure Mobipocket Decoder	ebookfab	Kindle Formats	3	12-09-2008 08:50 PM
Secure Mobipocket Decoder v0.3	Aenea	Kindle Formats	74	07-10-2008 09:57 AM
Secure Mobipocket Decoder is no more...	Aenea	Kindle Formats	26	04-12-2008 09:53 AM

10-25-2008, 03:36 PM	#152
pthwaite Fanatic Posts: 597 Karma: 430 Join Date: Aug 2008 Location: Ellesmere Port, UK Device: DR1000S Sony PRS505 iPad iPhone	Well I've just successfully, after a lot of reading and running Pdurrant's little script, done my first de drm Like most of you, I don't mind paying for books, but I feel it is up to me what I do after I've got them, ie swap, share. or throw out etc. DRM stifles the spread of literature

11-14-2008, 01:48 AM	#154
adinb RSS &amp; Gadget Addict! Posts: 82 Karma: 67 Join Date: May 2005 Location: Albuquerque, NM Device: Sony PRS-500, iPod Touch, iPhone	Hmm, looks like I've run across a fictionwise mobipocket book that doesn't successfully decrypt (though the script runs/works fine). I've successfully utilized mobidedrm many times -- and reran the scripts against old books just to make sure I hadn't dorked something up. I also brought out fresh versions of the scripts just to make absolutely sure. Inspecting the file with a hex editor, everything looks good until a bit after the <head> element, with parts of text that are fine and parts that are garbled. Looks like either something odd with the copy I bought from fictionwise, or there's a weird variant that the script isn't picking up. Since I'm on OSX, I'm sorta hosed for reading my book -- anyone out there interested in taking a gander at before/after versions of the book? This might be something that a certain someone might want to take a look at for additions to the script.

11-14-2008, 02:52 AM	#155
JSWolf Resident Curmudgeon Posts: 79,051 Karma: 144284074 Join Date: Nov 2006 Location: Roslindale, Massachusetts Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3	If you only have MobiDeDRM.py version 0.01 or 0.02 then yes, that sort of thing can happen where it appears to run with no error, but the resulting eBook is hosed. Only 0.04 has so far not had any errors that I know of. So if you have 0.01, you also need 0.02 and if you have 0.02, you want to find the thread here with the patches to apply to convert 0.02 into 0.04.

11-14-2008, 05:18 AM	#156
adinb RSS &amp; Gadget Addict! Posts: 82 Karma: 67 Join Date: May 2005 Location: Albuquerque, NM Device: Sony PRS-500, iPod Touch, iPhone	nope, I'm ran it against V4 (old books and new) as well as virgin V1 & V2 scripts with no dice. From what I got partially running in crossover (my parallels machine is at home), the file appears to be valid encrypted mobipocket (though I'm not 100% sure since running inside a crossover bottle is a finicky affair). So, it looks to be a mobipocket variant that's potentially not being handled by the script. Hmmm.

11-14-2008, 01:16 PM	#158
JSWolf Resident Curmudgeon Posts: 79,051 Karma: 144284074 Join Date: Nov 2006 Location: Roslindale, Massachusetts Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3	That would have solved all the problems had we known that Stanza buggered it up. In order to verify that a Mobipocket eBook works properly is to view it using official software such as Mobipocket Desktop.