Search the Community
Showing results for tags 'x86'.
Heres a function for searching for a bitmap within another bitmap. The heart of it is written assembly (source included) and working pretty quick I feel. I have included an example which is pretty basic and should be easily enough for anyone to get the concept. You will be given a small blue window that will take a screencapture of that size: It will then take a full screenshot and highlight all locations that it found Please let me know if you have any issues or questions. Thanks! Update 8/5/2019: Rewrote for fasmg. Added full source with every
I developing simple script for one program to do the automatic clicks. Now I developed on xp and win 7, but on win 10 gives me error. But the point for me to make it clear and not having basic mistake with choosing x64 and x86 system. So if I choose x64 system, does it going to work on x86? when compiling do I need to check or uncheck x64 compatibilities? Right now I'm installing new autoit v3 full install and it ask me what version to do like: - use native x64 tools by default - Use x86 tools by default (recommanded for compatibility) I assume I should use x86,
Special thanks to Ward for his udf and Trancexx for her assembly examples as they have played a huge role in my learning of asm. UDF Requires >Beta version 220.127.116.11 or higher. Also Requires >Wards Fasm UDF. Direct Download Link FASMEx.zip FasmEx 9-29-2013.zip This is dead. See new version here :
As documented here, it is possible to bypass registry redirection when running a 32bit application on a 64bit Windows installation, using HKLM64 or HKCR64. I quote: In this thread, >this feature's existence is denied. Also, if this feature exists and works, does it work on both production and beta? And can I also specificy HKEY_LOCAL_MACHINE64 and HKEY_CLASSES_ROOT64 instead of HKLM64 and HKCR64?