Windows 7 compatibility

[pary]

When a Labview built executable tries to create/ edit its .ini file, located in the same directory as the .exe, and when this all happens in "C:\Program Files", Windows doesn't provide this previlege for a standard user and labview doesn't create this 'application.ini' in any other location other than the exe's directory. What is the solution to this problem? is there a way to store 'Application.ini' in any folder other folder Program Files?

[MarkMoss]

The simplest solution would be to distribute application.ini along with application.exe.  Whatever puts applicaiton.exe into C:\Program Files\Whatever can simply install application.ini in the same location.

Generally, there is no reason why a LabVIEW program needs to write to the INI file at run time.

[Joseph_Loo]

Mark,

I wish that was true, but that is not necessary the case. There are many times when you need to update the ini file in order to supply additional information on subsequent run. I have needs that need to set the initial paramtrs after the installation.

[MarkMoss]

---

@Joseph Loo wrote:

Mark,

I wish that was true, but that is not necessary the case. There are many times when you need to update the ini file in order to supply additional information on subsequent run. I have needs that need to set the initial paramtrs after the installation.

---

If you just need to update it once following installation, the newer versions of app builder allow you to run the EXE immediately following installation under (I presume) the credentials of the installing user which should have write access to the INI file.

I'm curious (not doubting or judging, just curious) what you need to change in the INI file at run-time.

[Matthew_Kelton]

Typically you would put config files in the User App Data or Public App Data.  Create a directory in either of those for your Program, then write to them.  Public would work for all users.  Other users won't have access to other user's User App Data, so you can have different configs for each user if you use that location.

[Matthew_Kelton]

In this case, you will need two INI's - one that LabVIEW creates for your app, and then the one you use for yourself.

If you want to, not that I am suggesting it, you can click the Unlock checkbox in the Source File Settings in the Installer Properties.  It will allow general access to the file.  You may have to do that for the Public App Data directory as well.

[Wayne.C]

All my apps use the Public App Data directory as a place to store things like .ini's, templates, etc that are a accessed/modified by the program.  The programs install and run with no problems on either WinXP or Win7 32. 

The  LV Installer Builder will let you build an installer that automatically selects the right location for user config files based on what OS you are installing on.  You can use the 'Get System Directory.vi' in your program so that your code adapts to the OS it is running on as well.

[pary]

Thank you all, but I still don't get the solution to my problem. I ll try to restate my problem for better understanding.

Any Labview executable creates a 'yourapp.ini' while it is built or when the exe is run. This ini has information to properties of the executable, like fonts. I want it to be editable. Now how should this AUTOMATICALLY created ini file, be created in any location with right permissions?

Please refer to: http://digital.ni.com/public.nsf/websearch/65F76F247012DF68862562C70073BE06?OpenDocument

[Matthew_Kelton · Accepted solution]

Did you try the unlock option I mentioned?

[pary]

Thanks a lot. That worked. One small problem still persists. if someone deletes the file, my application is not able to create it again during runtime (unless it is run as admin). think there is no other go.