How to prevent renaming of autoit exe scripts?

[clifox]

Hi all,

I have a autoit executable script that runs as a process. The idea is that I don't my users to be able rename the executable as it is not going to be launched again with windows. How can this be done?

Thanks in advance!

[MHz]

Check @Scriptname.

[iceberg]

hi,

try @ScriptName

[GEOSoft]

Hi all,

I have a autoit executable script that runs as a process. The idea is that I don't my users to be able rename the executable as it is not going to be launched again with windows. How can this be done?

Thanks in advance!

Without actually writing the code for you, take a look at

WinGetTitle

If WinExists

ProcessList

Work with those then post what you have come up with and we can look at refinements.

EDIT: Add ProcessClose into the mix

Edited April 16, 2007 by GEOSoft

[clifox]

I knew about this. But there is another executable that is working with the first one and how @scriptname is going to work the second.

It's there and way to make it unrenameable?

Thanks!

[MHz]

Err, 2nd process?

Edit:

Your script can check it's own name.

Edited April 16, 2007 by MHz

[clifox]

Err, 2nd process?

What do you mean by this?

[MHz]

What do you mean by this?

Same, what 2nd process in #15 are you describing? Are we using 1 file as in 1 process?

[clifox]

Same, what 2nd process in #15 are you describing? Are we using 1 file as in 1 process?

I will try to describe again: there are 2 autoit executable scripts that works like processes and from time to time checks for the existence of one another.

[MHz]

Why 2? Only need 1 using @scriptname?

[GEOSoft]

You could also take a look at writing a registry value on first run and then checking that value at the begining of the script.

$MyVal = RegRead("HKLM\Whateverkey", "FirstRun")

If $MyVal = 1 AND ProcessExists("Explorer.exe") Then

Exit

Else

RegWrite("HKLM\Whateverkey","FirstRun","REG_SZ","1")

EndIf

Edited April 16, 2007 by GEOSoft

[clifox]

I want to thank you very much, you are very nice people and more very fast also!

The 2 processes I was talking about they both doing a different job, but they need one another, so if the user chances one of them name and kills it then the second cannot do his job anymore.

[MHz]

Bye...

[clifox]

One of them is in charge of the GUI and the other is doing the real job

[GEOSoft]

I want to thank you very much, you are very nice people and more very fast also!

The 2 processes I was talking about they both doing a different job, but they need one another, so if the user chances one of them name and kills it then the second cannot do his job anymore.

OK now I understand what you are trying to do (I THINK!!). This may involve changing the name of your script back to what it should be, more than preventing a rename. You can not prevent a file from being renamed by the user but you certainly can force a rename back to the original file name.

Let me give this some thought. In the meantime someone else may have the code at the ready.

[clifox]

This is a good idea indeed GEOSoft to rename it back to original name. I will try it!

Thanks

[clifox]

This is a good idea indeed GEOSoft to rename it back to original name. I will try it!

Thanks

[clifox]

I have tried it, but the autoit remembers only the initial @scriptname, it does check it every time the variable is checked. So it will always return the initial name.

[Jos]

I have tried it, but the autoit remembers only the initial @scriptname, it does check it every time the variable is checked. So it will always return the initial name.

Now why would somebody want to rename the script ?

[clifox]

The program runs for the whole time windows is running and a reason would be to stop it start with windows once it's name is changed.