Executable .ini file depending on target PC?

[Christ0phe]

Hello,

I am using the ole.authnlevel switch in the ini file of the executable that I am building. This executable is then installed on 150+ PCs. The problem is that depending on the target PC the value of this switch must be different (1, 2 or 5). Is there a way to keep having one app and .ini file but somehow case the content of the ini file based on the IP address of the machine on which the executable runs? Or any other method?

Thank you very much for any insights

Christophe

[paul_a_cardinale]

In your VI that reads the .ini file, have it check the IP then select the appropriate item.

[Christ0phe]

I am talking about the .ini file that is generated when compiling an executable. The switch that I referred to is one of its line.

[paul_a_cardinale]

Do you mean that you want different .ini files; customized at build time?

[Christ0phe]

Ideally I would prefer integrating a sort of 'scripting' inside of a unique .ini file. The scripting would include the case depending on the target PC IP addresses or other criteria...

[GerdW]

Hi Christophe,

---

@Christ0phe wrote:

Ideally I would prefer integrating a sort of 'scripting' inside of a unique .ini file. The scripting would include the case depending on the target PC IP addresses or other criteria...

---

Ideally you can create your own batch file and implement all the scripting you need, even based on IP addresses. That batch file may change the ini file as needed and then start your executable with the changed ini file…

[paul_a_cardinale]

---

@Christ0phe wrote:

Ideally I would prefer integrating a sort of 'scripting' inside of a unique .ini file. The scripting would include the case depending on the target PC IP addresses or other criteria...

---

You can't have scripting inside a .ini file.  They don't execute.

If you want a single .ini file that handles all cases, see my original response.

[Yamaeda]

You can have a network accessed file with e.g. a section with computer name [Pcname] and have the program look for a key there.