FEX VS x64dbg

"A fast usermode x86 and x86-64 emulator for Arm64"

Could try this https://github.com/FEX-Emu/FEX + wine/proton. But as always keep in mind that playing on non-supported platforms can lead to bans in future (never happened but who knows).

It's explained in the video, it uses https://github.com/FEX-Emu/FEX

Steam is also funding an x86 tn ARM game emulator, which opens up the potential for it working on Android.

Valve is funding developers working on an x86-to-ARM layer, FEX. I'm assuming that the eventual end goal would be to run Steam on Android, one of the FEX developers was commenting on trying to get FEX to work on an S8 Tab Ultra.

Valve is also funding another translation layer, from x86 to ARM (see FEX).

Additionally, game emulation won't be optimal until someone fixes this issue from FEX-Emu, which will allow that emulator to run on Apple Silicon. QEMU-user is currently your best option though it is dead slow. Box64 is currently pretty capable, however, it will not be able to run any 32-bit libraries (which even modern games ship a few of).

I have never heard anyone say anything good about the Visual Studio debugger before. Now, I'm not a Windows person but I'm not gonna argue for gdb or lldb here. RemedyBG and x64dbg are the two debuggers I've heard good things about though I've never used them because, again, not a Windows person.

[1] https://remedybg.handmade.network/

[2] https://x64dbg.com/

I'd help you out but because of circumstances I have no laptop with me. You need x86/x64 debugger to do this. This one for example Find a registration procedure and look for possible brenching to other parts of code in assembly. It's probably somewhere in the beginning. Exclude code validation and export new program version.

One interesting thing you can do is download an app like https://x64dbg.com/ or cheat engine, which will let you see the memory. You can look at the process for something you’ve made and explore it. Log a memory address from your app then go find it in the tool and interpret the bytes as an integer. Find a string and see how that works. Find a pointer, read the address it’s pointing then go look at that address. You start to see how different containers store data. I find it fascinating.

If you want to also do dynamic analysis (debugging) you can use https://x64dbg.com.

close origin and download this debugger https://github.com/x64dbg/x64dbg/releases

.exe is a complex format and not something you're going to extract raw instructions from using a hexdump. What you need is a "disassembler". For Windows I'd recommend x64dbg.

Patch the DayZServer_x64.exe, change "test al, al" to "cmp al, 2". i used x64dbg (https://x64dbg.com) a good video for the whole process: https://drive.google.com/file/d/1F1A0lpumREPXtVeoTMq1HiEnvaZp-NUU/view