Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Windows Server 2012 R2 - Wrong Offsets GTX 1070 #136

Closed
NeSmo1 opened this issue Jul 24, 2019 · 3 comments · Fixed by #138
Closed

Windows Server 2012 R2 - Wrong Offsets GTX 1070 #136

NeSmo1 opened this issue Jul 24, 2019 · 3 comments · Fixed by #138
Assignees

Comments

@NeSmo1
Copy link

NeSmo1 commented Jul 24, 2019

Heya!

First off wanted to say - This looks awesome and i cannot wait to try it.

However, with windows server 2012 r2 i am getting an offset [E35F7] Wrong...... Set 0x5 -> I Expected 0x74.

Bare in mind, Server 2012 r2 runs on a windows 8 kernel meaning i have to install the windows 8 GTX 1070 driver for it to work properly.

Using the 431.60 driver also.

Thanks and i am looking forward to your reply and insights!

@Snawoot Snawoot self-assigned this Jul 24, 2019
@Snawoot
Copy link
Collaborator

Snawoot commented Jul 24, 2019

Hi!

Try this one and tell me if it works. I'll merge it into master branch then and consider support for legacy systems on regular basis.

@NeSmo1
Copy link
Author

NeSmo1 commented Jul 25, 2019

Hi Snawoot,

Worked a dream!

May i ask, what is this actually doing? Is it changing certain hexadecimal code that allows it to unlock?

@Snawoot
Copy link
Collaborator

Snawoot commented Jul 25, 2019

Hi!

Thanks, that means we can proceed with Win7-Win8 support.

May i ask, what is this actually doing? Is it changing certain hexadecimal code that allows it to unlock?

It's an edit of conditional jump in x86 assembly. "See Also" section on main page contains link to original research behind this patch, which briefly describes how this patch was inferred on Linux 4 years ago. Long story short: GDB and direct assembly edit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants