We've just upgraded to LabVIEW 2009 and have started receiving requests to install our applications onto VISTA and Windows7. As far as I can tell the only thing different from previous installers for Windows XP and before is where we can store our Configuration files. Uptil now we have installed them in the C: Program Files directory, but I believe we can't or shouldn't do this anymore. My questions are: 1) Using the Get System Directory VI there is about a dozen directories listed (User Home, User Desktop.Public Application Data etc.) I presume for Single (User) Or Multiple (Public) Users we use the Application Data directories to store our Configuration data? 2) For the Public folders why does the NI Help file say that it is readable but sometimes writable. Is it because two users could be logged in at the same time and one of them is running the application preventing the other user from writing to the Config file? 3) Assuming we can't write to files stored in the C: Program Files directory, what happens if we want to modify the.ini file that is associated with the.exe file?

And of course if we don't include an.ini file in the installation process when the executable is run for the first time, if there is no *.ini file present, it creates it's own one, but will the OS allow this to happen? 4) We installed an application onto a VISTA machine using the 'Public Application Data' system directory type, but trying to find the actual config file proved a nightmare. On my XP machine in Windows Explorer I can easily navigate to C: Documents and Settings All Users Applicaiton Data, but in VISTA it appears to be totally hidden and access is denied even with adminstrator rights. Remote Desktop Connection Windows 7 32 Bit.

Is this Windows7 normal security settings - sort of defeats the purpose of having human readable/editable config files if the user can actually see them to modify them. Thanks for any help you can provide - Chris. We've just upgraded to LabVIEW 2009 and have started receiving requests to install our applications onto VISTA and Windows7. As far as I can tell the only thing different from previous installers for Windows XP and before is where we can store our Configuration files. Uptil now we have installed them in the C: Program Files directory, but I believe we can't or shouldn't do this anymore.

Is this a 64 bit OS? The config.nt file is used only to configure the 16 bit subsystem. This system does not exist in a 64 bit OS. In 32 bit Windows you will find.

My questions are: 1) Using the Get System Directory VI there is about a dozen directories listed (User Home, User Desktop.Public Application Data etc.) I presume for Single (User) Or Multiple (Public) Users we use the Application Data directories to store our Configuration data? Briggs And Stratton Single Cylinder Repair Manual 270962 Pdf. 2) For the Public folders why does the NI Help file say that it is readable but sometimes writable. Is it because two users could be logged in at the same time and one of them is running the application preventing the other user from writing to the Config file? 3) Assuming we can't write to files stored in the C: Program Files directory, what happens if we want to modify the.ini file that is associated with the.exe file? And of course if we don't include an.ini file in the installation process when the executable is run for the first time, if there is no *.ini file present, it creates it's own one, but will the OS allow this to happen? 4) We installed an application onto a VISTA machine using the 'Public Application Data' system directory type, but trying to find the actual config file proved a nightmare. On my XP machine in Windows Explorer I can easily navigate to C: Documents and Settings All Users Applicaiton Data, but in VISTA it appears to be totally hidden and access is denied even with adminstrator rights.