Latest MobiDeDRM Patch

[pdurrant]

Thanks to a sample of a Mobipocket ebook for which MobiDeDRM 0.04 didn't work properly, I've made a slight adjustment to the code. The new code should work with all the ebooks that 0.04 worked with, and a few more.

For Mac users I have two useful AppleScripts. The first will take MobiDeDRM 0.02 and patch it to MobiDeDRM 0.05. The second, when MobiDeDRM.py is added to the package, will give drag & drop unlocking of Mobipocket files.

For Windows and Linux, I have a diff files created with the standard POSIX diff on Mac OS X 10.5.6, and when used with the standard patch tool on MobiDeDRM 0.02 should produce version 0.05.

For those who were happy with the line-by-line instructions, I have new ones here. I've reversed the order (last line patched first) to make the line numbers constant while patching.

Source code lines removed. Please don't post them here in the forums. -- Alex

[nohmi2]

Originally Posted by pdurrant

Thanks to a sample of a Mobipocket ebook for which MobiDeDRM 0.04 didn't work properly, I've made a slight adjustment to the code. The new code should work with all the ebooks that 0.04 worked with, and a few more.

For Mac users I have two useful AppleScripts. The first will take MobiDeDRM 0.02 and patch it to MobiDeDRM 0.05. The second, when MobiDeDRM.py is added to the package, will give drag & drop unlocking of Mobipocket files.

For Windows and Linux, I have a diff files created with the standard POSIX diff on Mac OS X 10.5.6, and when used with the standard patch tool on MobiDeDRM 0.02 should produce version 0.05.

For those who were happy with the line-by-line instructions, I have new ones here. I've reversed the order (last line patched first) to make the line numbers constant while patching.

I have gone into Active Python, and I am afraid that I am still flummoxed about how to even start correcting MobiDeDRM4.py.
Smart, I'm not...willing to try, I am.
Please help(don't even know about the line numbers).

[devinoneill1]

Pdurrant
I've been having some difficulty with your mobidedrm002to005 script, I pm'd you about it
but maybe there's an applescript pro who can walk my dumb @$$ though it in the mean time.

[daviddem]

Good job dude. Are you starting work on epub and lrf any time soon?

[pdurrant]

I didn't do any of the hard work in the Mobipocket decoder code, just fixed a few minor bugs.

Paul

Originally Posted by daviddem

Good job dude. Are you starting work on epub and lrf any time soon?

[Justy]

This sounds like a great patch. Is it possible to post the lines of code in a different thread, perhaps the "Mobipocket Decoder Tool" thread where the Admins seem to have accepted code in the past? Or in a Wiki so that we can see them again?

[pdurrant]

I'm reluctant to repost anything that has been removed from Mobileread. The administrators have to make a judgement as to what's permissible.

It is much better to have the Mobileread forums without the Mobipocket Unlocker code, than to have no Mobileread forums at all.

Paul

without

Originally Posted by Justy

This sounds like a great patch. Is it possible to post the lines of code in a different thread, perhaps the "Mobipocket Decoder Tool" thread where the Admins seem to have accepted code in the past? Or in a Wiki so that we can see them again?

[FizzyWater]

I didn't see your original post, but I thought the update from 003 to 004 was posted with as little code as possible, for example:

[line 25] replace "a@18" with "a@@18"

But maybe you already were cryptic?

[devinoneill1]

I'm really dying here guys. I have no idea what I'm doing with this applescript for mobidedrm002to05. Is there anyway somebody can walk me through running it?
I'm sure its all my slow headedness, but when I try to put the code in applescript editor I get error messages stating unexpected characters, end of line expected something or other.
Any Suggestions?
Thanks,
Devin

[wallcraft]

Originally Posted by devinoneill1

I'm really dying here guys.

The best place to start to look for copies of MobiDeDRM python scripts is in the responses to DarkReverser's Weblog. Since 0.05 is new, start with the most recent responses.

[Striking Claw]

Originally Posted by wallcraft

The best place to start to look for copies of MobiDeDRM python scripts is in the responses to DarkReverser's Weblog. Since 0.05 is new, start with the most recent responses.

I tried the version mentioned in the blog and got the following error message:
File "MobiDeDrm05.py", line 100
assert off + in_off + len(new) <= endoff
^

I have the version 0.04 which works.
Does someone know where to find a listing of the differences between 0.04 and 0.05?

[pdurrant]

There is only one line that changed between 0.04 and 0.05, barring comments and help info.

You should be able to find the information on the internet somewhere.

Paul

Originally Posted by Striking Claw

I tried the version mentioned in the blog and got the following error message:
File "MobiDeDrm05.py", line 100
assert off + in_off + len(new) <= endoff
^

I have the version 0.04 which works.
Does someone know where to find a listing of the differences between 0.04 and 0.05?

[JSWolf]

I'm wondering why the code snippt to allow 0.02 to be updated to 0.04 was allowed on MR while the code snippit to go from 0.02 to 0.05 is not allowed.

[pilotbob]

Originally Posted by JSWolf

I'm wondering why the code snippt to allow 0.02 to be updated to 0.04 was allowed on MR while the code snippit to go from 0.02 to 0.05 is not allowed.

Probably because one was buried in a semi-related "help" thread so not as visible?

BOb

[bbusybookworm]

Originally Posted by pilotbob

Probably because one was buried in a semi-related "help" thread so not as visible?

BOb

And also probably as it did not include scripts to do it automaticley as the original post did.

The one to change 0.2 to 0.4 required you to go find the script, and then apply the changes your self, i.e. no code was directly provided.

so a post just mention ing the additional step might be permissible, but providing a tool to do it for you might not be.

Its a bit of a blurry line, but ....