Mobipocket Decoder Tool

[JSWolf]

Using Windows command prompt, you don't need any quotes around the PID eevne if the PID has a $ in it.

[llasram]

Originally Posted by JSWolf

Using Windows command prompt, you don't need any quotes around the PID eevne if the PID has a $ in it.

Oh, whoops. Someone else who had been having a similar problem was on OS X, where one would require the quotation marks. My mistake.

-Marshall

[nekokami]

The fact that some folks are getting it to work on a PC but then it fails on a Mac when the file has been transferred between the two systems makes me suspect that something to do with differences between those two platforms might be involved, e.g. the byte order or line ending characters. But that's just a wild guess.

[garygibsonsf]

Words cannot express my relief; it finally worked, by the simple act of placing single quotes around the PID in the command line version. Thank you, llasram, for your help in that corner, and thank you, pdurrant, for your offer of help; I tried running your script on my mac and putting single quotes around the PID when the box popped up, but unfortunately that didn't work. But, most importantly ... I got my book, and I can now buy mobi books and be able to read them on my Sony 500, despite owning an ibook.

Ah, the overwhelming sense of relief. I feel like a nice cup of tea and a read.

[pdurrant]

Many thanks to JSWolf for helping me see what's going wrong with the 0.02 (& my 0.03 patch version) of the MobiDeDRM script.

Since I now have examples of files that work with 1 but not 2 and 2 but not 1, and a little more experience with the Mobipocket file format, I think I've got to the bottom of the problem, and so I now have a new set of patches for the original 0.02 code. Here's the instructions for my new patch, line by line.

Also thanks to others who helped find a problem with the 0.04 patch version. These instructions now convert 0.02 to 0.05.

change line 165:
print "MobiDeDrm v0.02. Copyright (c) 2008 The Dark Reverser"

to
print "MobiDeDrm v0.05. Copyright (c) 2008 The Dark Reverser"

just so that you don't get confused at the command line.

Add a tab and make changes to line 136:
[tab][tab]extra_data_flags, = struct.unpack('>L', sect[0xF0:0xF4])

to make it
[tab][tab][tab]extra_data_flags, = struct.unpack('>H', sect[0xF2:0xF4])

After line 135:
[tab][tab]records, = struct.unpack('>H', sect[0x8:0x8+2])

add in the following three lines
[tab][tab]mobi_length, = struct.unpack('>L',sect[0x14:0x18])
[tab][tab]extra_data_flags = 0
[tab][tab]if mobi_length >= 0xE4:

(note that tricky comma after the first instance of mobi_length)

And finally, after line 63:
[tab][tab]bitpos, result = 0,0

add in the following two lines:
[tab][tab]if size <= 0:
[tab][tab][tab]return result

These changes should mean that any file that works with either 0.01 or 0.02 will work with 0.05. I'd love to hear about any problems.

Paul

Originally Posted by JSWolf

Actually, I've come across a couple of eBooks that your mod caused to actually break the eBooks so that it causes Mobipocket Reader to crash every time you try to view it.

I used MobiDeDRM.py version 0.01 on those eBooks without a hitch.

[igorsk]

Use [code] tags to keep the tabs.

[IceHand]

Haven't had any problems with your last patch, pdurrant, but thanks for the new one.

[wallcraft]

Originally Posted by nekokami

The fact that some folks are getting it to work on a PC but then it fails on a Mac when the file has been transferred between the two systems makes me suspect that something to do with differences between those two platforms might be involved, e.g. the byte order or line ending characters. But that's just a wild guess.

I think it is the "$" in the PID that is causing the problem, this does not matter under Windows but requires single quotes (double quotes won't work) on a Mac or under Linux.

[pdurrant]

I've uploaded a new version of my Applescript that can cope with $ in PIDs, and yes, it does that by enclosing the PID in single quotes.

It's worth a download even if your PIDs don't have $ in them, as it also now reports errors returned from the python script, and the readme has the new fix instructions for the 0.02 version of the MobiDeDRM.py script.

https://www.mobileread.com/forums/sho...&postcount=103


Paul

Originally Posted by wallcraft

I think it is the "$" in the PID that is causing the problem, this does not matter under Windows but requires single quotes (double quotes won't work) on a Mac or under Linux.

[JSWolf]

pdurrant ... Thanks for fixing things. Glad I could help you debug the problem. I'm hoping this is it and we have one program for now.

[FizzyWater]

I'm not a python programmer (have some exposure to VBA and VbScript only), so my notes below may be obvious to those of you who are, but for "idiots" like me, who are just trying to make a great tool work even better:

Originally Posted by pdurrant

Here's the instructions for my new patch, line by line.

After line 63:

Don't know why they'd be different, but when I displayed this in Pythonwin, this was line 62 for my copy.

Originally Posted by pdurrant

After line 135:
Add a tab to line 136:
and change line 165:

The rest of the line numbers matched in my copy...BUT!...only if I worked the corrections from the bottom up. As soon as you follow the first correction's suggestion (to add three rows of code after line 62/63), the line numbers no longer match up.

Just thought I'd share it for the other novices like me, who might have tried this and gave up when it didn't seem to line up.

[pdurrant]

Thanks for the clarification. I should have mentioned that any line numbers was the line numbers or the original file. Hopefully by quoting each line that I also referenced by number I didn't confuse too many.

Paul

Originally Posted by FizzyWater

The rest of the line numbers matched in my copy...BUT!...only if I worked the corrections from the bottom up. As soon as you follow the first correction's suggestion (to add three rows of code after line 62/63), the line numbers no longer match up.

Just thought I'd share it for the other novices like me, who might have tried this and gave up when it didn't seem to line up.

[pdurrant]

I bought the Chambers 10th Edition dictionary. A DRMed Mobipocket book over 40MiB in size.

I'm glad to say that the new version worked perfectly on it, although it did take over 80 minutes running on a 2GHz Dual Core machine.

Paul

Originally Posted by pdurrant

Many thanks to JSWolf for helping me see what's going wrong with the 0.02 (& my patch version) of the MobiDeDRM script.

Since I now have examples of files that work with 1 but not 2 and 2 but not 1, and a little more experience with the Mobipocket file format, I think I've got to the bottom of the problem, and so I now have a new set of patches for the original 0.02 code.

[IceHand]

Originally Posted by pdurrant

I bought the Chambers 10th Edition dictionary. A DRMed Mobipocket book over 40MiB in size.

I'm glad to say that the new version worked perfectly on it, although it did take over 80 minutes running on a 2GHz Dual Core machine.

Huh? I bought the Chambers too, but my version is only 24.7 MB in size. And MobiDeDrm worked here too, but took even longer (140 minutes with a 1.4 Ghz Celeron M).

[pdurrant]

You're right. I was typing from memory and my memory was faulty. The time is about right though.

Paul

Originally Posted by IceHand

Huh? I bought the Chambers too, but my version is only 24.7 MB in size. And MobiDeDrm worked here too, but took even longer (140 minutes with a 1.4 Ghz Celeron M).