Software Deployment

I don't like doing setup captures Why ever not? How do you normally deal with legacy/non-MSI-based installs?

The one piece of advice I'd give you is, depending on which tool you're using, to turn off any use of self-registration. Make the tool use the advertising tables instead.

The only way you don't have to repackage but package is that they provide you the files, the locations and the registry settings, you can forgot that they can provide that to you because that also requires a capture. I recently created a package that installed through a webpage, it was a piece of cake. Ensure your O/S is very clean...

[quote]I was able to create the msi from the extracted files, and configured c:\windows\downloaded program files as the destination directory for the files to be copied too, only when I check the folder the files arent there, yet IE will download them to the folder no problem, also I have no permissions to the folder to change the attributes
[/quote]
Downloaded Program Files (the ActiveX Cache Folder) is a special folder (as identified by the hidden desktop.ini file). When you open this folder in Windows Explorer, you get an interpreted view. What you get in this case is a list of registered add-ons. You either have to access the folder from DOS (which doesn't adhere to desktop.ini) or temporarily remove/rename/alter desktop.ini to allow you to view it as a normal folder in Explorer.
BTW, the reason why you don't see your add-on is probably because you excluded the add-on registration information in your package.

Hi, figured it out, when I ran the installer the downloaded program files folder attribute is set to read only | hidden in windows, ran dir from good old dos and viewed the folders contents.
Sooooo, looks like the install is doing as it is intended...
Thanks