IniWrite in vista

[BitByteBit]

I'm trying to write to an existing .ini file in Program Files on Vista, it doesn't write to the file and I'm not sure why not.

Any pointers?

Edit:

I needed to have full access rights to the folder, any way to automate this? Or does my .exe need to run with admin rights?

Edited November 25, 2009 by BitByteBit

[Melba23]

BitByteBit,

Vista blocks you from writing in the "C:\Program Files" folder - security don't you know! You will probably find your file somewhere in "C:\Users\user_name\AppData".

I use this code to get round the problem:

; Determine location for ini file
If StringInStr(@ScriptDir, "Program Files") Then
    ; If app in C:\Program Files need to save elsewhere
    If Not FileExists(@AppDataDir & "\App_Name") Then DirCreate(@AppDataDir & "\App_Name")
    $sAppData_Path = @AppDataDir & "\App_Name"
Else
    ; Can use app folder
    $sAppData_Path = @ScriptDir
EndIf

Then I at least know where my file will be and Vista does not get in the way. You can easily modify it to your own needs.

M23

[BitByteBit]

Melba23 to the rescue!

Great, now I know where my files went!

However,I use an installer to put the .ini file in Program Files and need to edit it through autoit.

Are you telling me that I have to use this work around?

Check for vista, if it is then always read/write that file?!

Surely I can change the permissions on the folder? I've been told that if I run the program as Admin, since that has write rights then it will in fact write the .ini, is the solution not here? IsAdmin()?

There must be hope!

Edited November 25, 2009 by BitByteBit

[Melba23]

BitByteBit,

Vista uses a clever trick called Virtualisation to store the file elsewhere while fooling file managers. Google offered this:

Virtualization Example

For example, take a legacy software application that attempts to write to a configuration INI file located in:

C:\Program Files\<application>\Setup.ini

Windows Vista automatically detects that you do not have permission to save to that location. Windows Vista then copies the file (if it already exists) to:

C:\Users\<your_account>\AppData\Local\VirtualStore\Program Files\<application>\Setup.ini

Windows Vista then allows the write operation to succeed at the new file in the VirtualStore folder. Subsequent read and write operations for that file will always use the file copy located in the VirtualStore folder. However, the application will continue to believe that it is accessing the Program Files directory.

So as I read this, you should be able to edit the ini file directly through AutoIt - it is just that you will not be editing the actual file, just the copy.

That is a far as my knowledge goes - I bow out here. Perhaps a Vista guru can go deeper.

M23

[AdmiralAlkex]

Try to run your script as an administrator

#RequireAdmin
;your script under here

[BitByteBit]

After more thought and debate I came up with this:

$Os = @OSVersion
if $Os = "WIN_VISTA" then
FileCopy(@ProgramFilesDir & "\FarmShark\FV.ini", @MyDocumentsDir& "\FarmShark\FV.ini",0+8)
Global $Location = @MyDocumentsDir& "\FarmShark\FV.ini"
;MsgBox(0,"",$Location & "1")
Else
Global $Location = @ProgramFilesDir & "\FarmShark\FV.ini"
;MsgBox(0,"",$Location)
EndIf

Thanks Melba, just the work around I needed. (+)

@OSVersion returns "WIN_VISTA" if your running windows 7, is this fixed in the beta by chance?

@AdmiralAlkex

Damn, should of seen that earlier would of saved me some hassle! Thanks though! (+)

[AdmiralAlkex]

@OSVersion returns "WIN_VISTA" if your running windows 7, is this fixed in the beta by chance?

Yes it was fixed months ago.