I think you might be applying the patch to
json.dll
that has already been patched. I just downloaded
json130W3x64.zip from Far PlugRing and tested it out. Here is the output showing the SHA-1 hash and the Git command.
Code: Select all
[E:\Downloads\json130W3x64]sha1sum json.dll
80be59e1e7c11bcf96efbc6bdc387622a61bf7ba json.dll
[E:\Downloads\json130W3x64]git apply JSON-Browser-v1.3-x64.patch
[E:\Downloads\json130W3x64]sha1sum json.dll
50f14b30a2f722af73f575924cc05a905d4bc616 json.dll
As you can see, before applying the patch, the SHA-1
80be59e1e7c11bcf96efbc6bdc387622a61bf7ba
matches yours from
json.dll
If you try to apply the patch again, on an already patched file, you will get an error as seen here.
Code: Select all
[E:\Downloads\json130W3x64]git apply JSON-Browser-v1.3-x64.patch
error: the patch applies to 'json.dll' (19007fd832161308c173f31f209c6ba346fdfd78), which does not match the current contents.
error: json.dll: patch does not apply
However, if you reverse the patch, it should give you back the original file, which you can verify by checking the SHA-1 hash again.
Code: Select all
[E:\Downloads\json130W3x64]git apply -R JSON-Browser-v1.3-x64.patch
[E:\Downloads\json130W3x64]sha1sum json.dll
80be59e1e7c11bcf96efbc6bdc387622a61bf7ba json.dll
Manually Patching
If you're still running into issues, you can apply the patch manually by making the following changes in
json.dll
using any Hex editor, like Hexitor.
Code: Select all
File Offset: 0000EC02
Original Bytes: 33 DB 48 89 5D F7
Patched Bytes: E9 CB 4F 00 00 90
File Offset: 00013BD2
Original Bytes: CC CC CC CC CC CC CC CC CC CC CC CC CC CC CC CC CC CC
Patched Bytes: 31 DB 48 89 5D F7 48 85 C0 75 02 FE C0 E9 24 B0 FF FF
After making the above changes, the SHA-1 of
json.dll
should be
50f14b30a2f722af73f575924cc05a905d4bc616