KryMemory Function problem

[deve]

I am trying to change bytes from an executable file with KryMemory.au3 . I have made up like this my function :

Func changef()
if $changef=1 then
Local $changef_OFFSET[2] = [0xEB 0x10]
$PROCESS = _Process_Open("test.exe", $PROCESS_ALL_ACCESS, False)
$changef = _Process_WriteMemoryPointer($PROCESS, 0x008D7F97, $changef_OFFSET, 0xEB)
$Label1 = GUICtrlCreateLabel("F1 changef  [ENABLED]", 16, 8, 264, 16)
GUICtrlSetColor(-1, 0xff0000)
ElseIf $changef=0 Then
Local $changef_OFFSET[2] = [0x6D 0x6B]
$PROCESS = _Process_Open("test.exe", $PROCESS_ALL_ACCESS, False)
$changef = _Process_WriteMemoryPointer($PROCESS, 0x008D7F97, $changef_OFFSET, 0xEB)
$Label1 = GUICtrlCreateLabel("F1 changef [DISABLED]", 16, 8, 264, 16)
 EndIf
EndFunc

The Problem is it does not write any bytes to address , second I can only enable and disable the function and then that was. Does not work for second enabling or disabling ?

Any help whould be nice ... attaching KryMemory.au3

KryMemory.au3

Edited March 13, 2019 by deve

[Nine]

what application are you trying to automate ? what is the real .exe you are trying to modify ?

[Melba23]

deve,

What he said - with bells on!

M23

P.S. And just to be absolutely clear - this is the Mod team determining the legality of the thread, so everyone else please keep out.

[deve]

19 hours ago, Nine said:

what application are you trying to automate ? what is the real .exe you are trying to modify ?

it is my solarenergie software I just trying to tweak it a little .

 

19 hours ago, Melba23 said:

deve,

What he said - with bells on!

M23

P.S. And just to be absolutely clear - this is the Mod team determining the legality of the thread, so everyone else please keep out.

I did not understand any of your writing ? explain please

[JLogan3o13]

@deve The question is why you need to "tweak" something on a running executable. There aren't many legitimate reasons to do this, so it necessarily raises red flags for the Moderation team. Please explain in detail what you are trying to accomplish.

Edited March 14, 2019 by JLogan3o13

[deve]

3 hours ago, JLogan3o13 said:

@deve The question is why you need to "tweak" something on a running executable. There aren't many legitimate reasons to do this, so it necessarily raises red flags for the Moderation team. Please explain in detail what you are trying to accomplish.

well there I found a adddress that holds the information about the invertor is returning to aku becoz no light but actually there is moon light and so there is no function in the software and I wont to try this via wireless to connect to running software and change the bytes that will say to the software to charge from outside. Hope you understand my english . default there is soem limit that the invertor wil lreturn to charge from sun . 

Edit : I did hexedit the address but then it is a problem when it is sun outside the software redirects the invertor nomore to charge from sun . Thats why I need to change the function manually ( when there is night and moon light ) .

Edited March 14, 2019 by deve

[Bilgus]

I was under the impression there wasn't enough light from the moon to offset the power lost trying to capture it

So in other words you want to alter the threshold of the inverter to make it cut off at lower amperage in order to try and capture

some usable electricity during cloudy days or at night with moon light

 

And... the control program runs on a windows pc??

Or is that like a configuration program that pushes new settings to the inverter??

[JLogan3o13]

@Bilgus What part of stay out of a thread when a Moderator is involved is so hard to understand?

On 3/13/2019 at 5:56 PM, Melba23 said:

deve,

What he said - with bells on!

M23

P.S. And just to be absolutely clear - this is the Mod team determining the legality of the thread, so everyone else please keep out.

 

[JLogan3o13]

@deve Even if you have no harmful intentions, the fact is you are trying to do the below, which is against the forum rules. This is not a discussion we are going to entertain.

 

Quote

• Automation of software/sites contrary to their EULA (see Reporting bullet below).
• Running or injecting any code (in any form) intended to alter the original functionality of another process.