Save INI data to exe. (while open)

[nullschritt]

Hello all, this script(wrapper) uses Alternative Data Streams to store INI formatted data in the active executable even while it is running. This is great for standalone executables, or storing data you don't want a user being able to edit!

There are four simple commands:

Func _iniwrite($section, $key, $value, $stream = "DEFAULT")
    return IniWrite(@ScriptFullPath&":"&$stream, $section, $key, $value)
EndFunc

Func _iniread($section, $key, $default = "", $stream = "DEFAULT")
    return IniRead(@ScriptFullPath&":"&$stream, $section, $key, $default)
EndFunc

Func _inidelete($section, $key = "", $stream = "DEFAULT")
    if $key <> "" Then
    Return IniDelete(@ScriptFullPath&":"&$stream, $section, $key)
Else
    Return IniDelete(@ScriptFullPath&":"&$stream, $section)
    EndIf
EndFunc

Func _inirenamesection($section, $newsection, $flag = 0, $stream = "DEFAULT")
    return IniRenameSection(@ScriptFullPath&":"&$stream, $section, $newsection, $flag)
EndFunc

Simply copy and paste these functions into your script!

Edited October 24, 2013 by nullschritt

[JohnOne]

Struggling here to think of a use.

To me, you might as well use regular variables.

Unless I'm missing something.

[nullschritt]

Struggling here to think of a use.

To me, you might as well use regular variables.

Unless I'm missing something.

I personally use the method to store product keys of programs which require an active subscription to work.

Not to mention it quite literally associates the data with the exe, so programs that store user data can be made completley standalone, and still have redundant setting storage.

And there's also the fact that the user can't delete or edit the data directly, so as not to cause any errors by invalid config settings.

I know it's a really simple wrapper, but it does have practical uses.

[guinness]

Of course this has its limitations.

[nullschritt]

Of course this has its limitations.

Yes, Alternative Data Streams only work with NTFS file system (which is can be a positive as well as a negative) [data is lost when the file is copied to another pc] *(under MOST conditions)

But that's the only "limitation" I can think of (:

[stealthmsgr]

Thanks for submitting this. I have used INI's off and on. I have hidden them within the OS or create a temp INI and then kill if off. This makes it much more straightforward.

Cheers.

[joseLB]

As I know nothing about Alternative Data Streams, if the idea is what I think it is, it could be a great and simple way to store .ini at the .exe

1- how do I embeb my ini lines at the .exe, supposing I have a previous .ini? This data becomes part of the .exe?

2- once embebed it will stay there? Even betwen runs?

3- if I copy this .exe to another PC, you told that the data will not be at the other PC. Can you tell why?

Thanks

Jose

[jchd]

joseLB,

googling "Alternative Data Streams" would answer all your 3 questions, and more.

[nullschritt]

As I know nothing about Alternative Data Streams, if the idea is what I think it is, it could be a great and simple way to store .ini at the .exe

1- how do I embeb my ini lines at the .exe, supposing I have a previous .ini? This data becomes part of the .exe?

2- once embebed it will stay there? Even betwen runs?

3- if I copy this .exe to another PC, you told that the data will not be at the other PC. Can you tell why?

Thanks

Jose

1)If you want to copy a previous INI to the exe, you will have to write a code to read the previous ini file then write then to current exe using some sort of loop. The data is not actually stored inside the executable code, but rather along side it.

2)Yes the data is persistent between runs.

3)The data is only lost when the exe file is copied to a filesystem which doesnt support Alternative Data Streams (webservers, most flash drives, and discs)

Ex: Copying from point A to point B on the same pc wouldnt cause data loss, but coping from pc1 to pc2 would.

Hope this helps!

Edited October 26, 2013 by nullschritt

[JohnOne]

2)Yes the data is persistent between runs.

Now that's a decent use for this.

EDIT:

For example if you wanted to invisibly keep track of how many times a user runs your script.

Edited October 26, 2013 by JohnOne

[FireFox]

Nice idea

[joseLB]

1)If you want to copy a previous INI to the exe, you will have to write a code to read the previous ini file then write then to current exe using some sort of loop. The data is not actually stored inside the executable code, but rather along side it.

2)Yes the data is persistent between runs.

3)The data is only lost when the exe file is copied to a filesystem which doesnt support Alternative Data Streams (webservers, most flash drives, and discs)

Ex: Copying from point A to point B on the same pc wouldnt cause data loss, but coping from pc1 to pc2 would.

Hope this helps!

Thanks nullscritt, it become clear

Do you think there is a way to include the .ini, and also images/icons, (used in gui´s for example) and even sounds in the .exe?

I mean, to have just one file (.exe) with all these items, so if I send this .exe file, for example, zipped thru an email, it will work?

Better, if I do not have to modify my gui created with Koda, for example

Thanks

Jose