Hi,
Just in case anyone is interested:
There is a difference betweene CyberPatcher and OxyPatcher.
And there is also another tool, part of MMULib (aminet) called MuRedox, which is free, works in a way of OxyPatcher, but requires MMULib installed.
OxyPatcher is more sophisticated - it recognizes missing instructions by OPCODES, then generates a stub for the required arguments (most often - CPU registers).
This way it is able to patch any OPCODE it can recognize, but generating of the stub (once, when the instruction is executed for the first time) may be slower - but this is really not a big drawback.
CyberPatcher is simpler - it recognizes complete bit-templates, OPCODE together with arguments. Author decided which are most oftenly used and hardcoded them in the program. So the recognition and patching is faster, but if you meet that one opcode that could be patched, but uses argument (CPU register) that was not judged to be used frequent enough by the author of CyberPatcher, it will be left untouched, degrading the system performance forever.
Good example for that - Duke Nukem 3D Amiga free port. Even with running CyberPatcher, it keeps emulating those few instructions.... (Easy to be verified with tools included in MMULib package).
Cheers
PiR
