/bundles/itninjaweb/img/Breadcrumb_cap_w.png
I'm packaging some of (the dozens of) IBM driver apps. They use some system type services so I can't repackage into MSI directly. I am however making an MSI wrapper for their silent install/uninstall. Here is the dilema:

We have two installs essentially. The MSI wrapper and the original Installscript exe. If I delete the setup files after the CA install then I don't have them for a potential uninstall. If I keep them I get partial duplicate files (IS install keeps some of the install files), where should I put them? Temp directory is bad place and a tech may update a drivers folder and break it. Any best practices?

Also should I replace the add/remove entry of the original IS install with the MSI uninstall? If I don't then it breaks upgrades, etc. if someone manually uninstalls. If I do then I would have to have the source file available. I guess I am looking for a best practices. Thanks ahead of time.

(Also I'm not using WWIW because it doesn't seem to grab the extra files besides setup.exe)
0 Comments   [ - ] Hide Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity

Answers

0
Hi,

How about a special drivers folder in C:\windows that you make hidden say called ibm_driver_apps that way you can still maintain the uninstall, it keeps the files out of general harms way and you can have the source there too.

Cheers,

Barry
Answered 08/03/2006 by: BarryB
Orange Belt

Please log in to comment
0
Well, I did find a cool little trick to use the Support Files. This allows the files to be extracted to a temporary directory at the start of the install and then deletes them at the end. It is really handy, however right now I am trying to work out why the uninstall isn't working. The result code I get back from the legacy installscript set up is -5.
Answered 08/03/2006 by: wheelz
Yellow Belt

Please log in to comment