Save/burn a string into a compiled script?

[nyke0]

It's hard to explain, but I will try. After compiling a script I will run it, and with the first run it will create a string, like a key. The script shall keep this string for ever, but it's should'nt be saved in a txt file or somewhere, only in the exe. Is taht possible?

[computergroove]

Why do you need to do this? I suppose you could make sure that autoit was installed and you could make your script copy your entire code with the new variable and recompile your code to a new exe and then delete the old one. It's very messy and unnecessary. Just use a  text file.

Edited September 5, 2014 by computergroove

[nyke0]

I know that way, thanks. But I asking for a hard save without to recompile for just 1 string.

Edited September 5, 2014 by nyke0

[computergroove]

Once the exe has been compiled it no longer gets written to. The answer is no.

[MikahS]

Absolutely not

[jchd]

Adding a resource could work but probably not while the .EXE is running. Another very different (naïve) possibility to attach a licence or something like that is to store it in an ADS (Alternate Data Stream) "under" the .EXE but it only works with NTFS.

[jguinch]

I don't know the risk, but what about adding some text into the .exe (at the end) ?

This text could be crypted.

Of course, it's not really secure, but it's an idea...

[jchd]

AVs frown on that.

[jguinch]

Even if we can store an information into the exe file, copying the file on a different computer will copy the key to.
So if you need to prevent the exe file copy (with the embedded key), then you will have to store the key outside the exe, or work with an unique computer ID (GUID).

JCHD suggestion seems to be a good way.

Edited September 6, 2014 by jguinch