What does the CA Error lead to?

[my80chevette]

I am getting ready to start the learning process for doing my own programming but untill my skills match my desires I am going to be asking some questions. The error referencing a memory address when you use a bypass to try to run hack dll's seems to be common to any bypass used. However, is this linked to the bypass dll's or is it a problem with where the injectors inject? If the bypasses are at fault this would obviously require a new set but if it relates to the injectors perhaps they could be reconfigured with new instuctions? I hate to ask these questions, as i would like to answer these myself but I still lack those skills. Anyone with an idea?

[why06]

I am getting ready to start the learning process for doing my own programming but untill my skills match my desires I am going to be asking some questions. The error referencing a memory address when you use a bypass to try to run hack dll's seems to be common to any bypass used. However, is this linked to the bypass dll's or is it a problem with where the injectors inject? If the bypasses are at fault this would obviously require a new set but if it relates to the injectors perhaps they could be reconfigured with new instuctions? I hate to ask these questions, as i would like to answer these myself but I still lack those skills. Anyone with an idea?

eh? So your asking if problems editing memory addresses are due to the bypass or the actual hack itself?

[my80chevette]

eh? So your asking if problems editing memory addresses are due to the bypass or the actual hack itself?

Exactly....... I am just wondering which one is really causing the problem with bypasses? Is there a common mem address that all bypasses attempt to edit or is the problem now in how the injectors are injecting the bypasses? I am too much of a noob at this to know exactly how this stuff works but if either the dll or the injector can be adjusted to a new area of mem or method of injection then all the old hacks and chams could be reused. Of course I realize that there are certain rules governing how and where these bits are placed so if the address that is now causing the difficulties is required no matter what........ well were double screwed!!!

[That0n3Guy]

Exactly....... I am just wondering which one is really causing the problem with bypasses? Is there a common mem address that all bypasses attempt to edit or is the problem now in how the injectors are injecting the bypasses? I am too much of a noob at this to know exactly how this stuff works but if either the dll or the injector can be adjusted to a new area of mem or method of injection then all the old hacks and chams could be reused. Of course I realize that there are certain rules governing how and where these bits are placed so if the address that is now causing the difficulties is required no matter what........ well were double screwed!!!

The method the bypass uses to exploit the anti hack becomes patched which makes the bypass unusable. Strings in the injector can ALSO become detected and cause the game to not work, even with the bypass.