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

Make 100% x64 compatible. #3

Closed
erfg12 opened this issue Aug 23, 2017 · 5 comments
Closed

Make 100% x64 compatible. #3

erfg12 opened this issue Aug 23, 2017 · 5 comments

Comments

@erfg12
Copy link
Owner

erfg12 commented Aug 23, 2017

Might already be done, just needs to be tested.

@erfg12
Copy link
Owner Author

erfg12 commented Sep 15, 2017

Was having issues with overflow if the application opened was x86, so I added a new function is64bit() to divert 64bit apps to the get64bitcode() function instead of getcode().

Still needs to be tested though.

@erfg12
Copy link
Owner Author

erfg12 commented Sep 19, 2017

Apparently MEMORY_BASIC_INFORMATION has both a 32bit and 64bit structure. That new is64bit() function came in handy for switching this around.

https://msdn.microsoft.com/en-us/library/windows/desktop/aa366775(v=vs.85).aspx

@erfg12
Copy link
Owner Author

erfg12 commented Sep 19, 2017

Also had to fix is64bit() as I assumed WoW64 meant the program was 64 bit. It actually means Windows 32bit on Windows 64bit. So I swapped that boolean around and fixed it.

For more info - https://en.wikipedia.org/wiki/WoW64

@erfg12
Copy link
Owner Author

erfg12 commented Sep 19, 2017

When making a trainer for a 64bit game, you have to uncheck the "Prefer 32-bit" checkbox in the build options. Memory.dll does not need to be re-compiled, it will work for both 32-bit and 64-bit applications.

https://github.com/erfg12/memory.dll/wiki/64bit-Games

@erfg12
Copy link
Owner Author

erfg12 commented Feb 21, 2018

I'm going to close this issue since all of this has been fixed to my knowledge.

@erfg12 erfg12 closed this as completed Feb 21, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant