Software Deployment

Look for any condition preventing the file (component) from being installed, could be using the VersionNT property.

Can you elaborate on that thought? Not really my area of expertise. I am familar with msi PROPERTY's. is it possible that VISTA is having difficuly translating the old profile path to the new "VISTA" profile path? Because not only does the settings.sol file not get created but the entire structure (under XP Application Data\Macromedia\....) does not show up under the VISTA Program Data profile structure.

Thanks for the response

Install the MSI with verbose logging to find out how the component holding the "settings.sol" file isn't installed correctly on Vista.

John has blogged some excellent information regarding "Understanding the Windows Installer Logs"
http://johnmcfadyen.spaces.live.com/blog/cns!9DD01136FC094724!213.entry

If I had an .msi that would be fine BUT I am installing the flash player active X which is an executable which does not appear to extract an msi

It shows up a Adobe Flash player Active X 9.0.124

I thought I might try to manually create the profile structure that is created in XP and see if that works.

Hi Keith,
have been looking at the package KB: http://itninja.com/link/adobe---player-licensing
There, you should find all the info, you need.
Regards, Nick

Thanks

I will see if I have better luck with the .msi