Doug,

The reference I read related to the last Beta before the RC, but it referred specifically to files created during installation, not files created manually. (It was also a Delphi discussion, but I would expect MSI is MSI...) It may be that the system second guesses what the installer is doing or that the installer knows this is Vista and needs to set permissions. But it was pre-RC, so things may have changed as well.

I hope to set up my Vista test system in the next couple days. Unfortunately, I have to boot my principle desktop to Vista as none of my test systems look like they will pass muster. (400 MHz, less than 1GB Ram) I think I can configure my Asus MB to boot clean via BIOS options from either my SCSI drive for XP or my IDE drive for Vista without having to worry about dual booting. Hopefully I can hide my XP drive from Vista and vice-versa by disconnecting the SCSI drive during install and not setting it up in Vista. If my current client decides to go with the replacement project I'm spec'ing right now, I can build a new system for Vista for real, including Aero...

In any case, I look forward to what you learn, as I too have several apps out there that somebody will want to run on Vista eventually.

...Jim

>Hi Jim.
>
>I did a little playing tonight and found that files created in subfolders of ProgramData could only be written to by the creator user. Even admins can't modify a file created by another user. I haven't tested this with an installer, but I suspect the rules will be the same -- if the installer runs elevated as an admin user, any files it creates in ProgramData will be read-only to other users.
>
>I also found that files and folders in \Users\Public are read-write to all users, so perhaps that's the place to store global data.
>
>Still playing ...
>
>Doug