As this seems to be a problem caused by the installation launchpad, the following are some workarounds that could be considered. The idea is to skip the installation launchpad in the db2 install: (1) Do a response file based silent install: You can modify the sample response file that packaged in the install image, under ~ db2 windows samples, then execute the following command: setup.exe -u [rspFile] -t [traceFile] -l [logFile] (2) If you want to do a GUI install, launch the db2 install from wininst.exe, instead of setup.exe: wininst.exe is under ~ db2 windows in the install image. You can execute the following command to launch a GUI install. 1) Install to a new copy: wininst.exe -e [prodAbbrev] -t [traceFile] -l [logFile] 2) Install to an existing copy: wininst.exe EXISTING -e [prodAbbrev] -t [traceFile] -l [logFile] -n [copyName] For example, run a command: wininst.exe EXISTING -e ese -t D: db2.trace -l D: db2.log -n DB2COPY1. ![]() Aug 21, 2008 - There are many installshield applications (MSI)/ Other Vendor MSI which come wrapped in setup.exe. The packagers can extract the MSI easily.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |