Complex Hardware application to package
We are trying to package an RITS application (a hardware based application) ,the source of which can be downloaded from http://www.rba.gov.au/rits/software/. (The installation doesnot need the hardware to be available)
We have tried taking capture by WISE 5.6 with all possible options i.e no exclusion list for files/registry, included files & reg deleted during capture, captured h/w entries, Allow root to be watched, capture non-microsoft odbc entries, enable self registration. All of the listed options above were tried with snapshot only capture, smart monitor capture, smart monitor + snapshot capture. But none of the capture works OK, the package shortcut when launched, doesnot recognise the h/w device. (The testing and capture are taken on a clean XP build)
As the capture didn't work, so we wanted to use the vendor MSI and create a transform. (by searching I found that RITSClientWISE_v1-9_20060629.exe copied from http://www.rba.gov.au/rits/software/ extracts setup.exe, CIP.msi & other components in C:\temp\RITS\iKey2000SDKMU18.) When tried to install CIP.msi it doesn't allow us to run directly and needs to run from setup.exe only (though ISSETUPDRIVEN=1 property value makes the CIP.msi run, but it tries to install all features of which source files are not available) now when the setup.exe is passed "/v l*v C:\temp\Rits.log" as parameter it creates a log file (I am sorry that I cannot attach the log file, request you to please run the command for genearting the log file)
The log file shows that setup.exe passes command line parameter to the CIP.msi, and when we try to pass the same command line parameter from a command prompt, to the MSI, the command gives error and cannot continue.
How can we make the vendor MSI install?
Can you please advice if this kind of applications can/should be re-packaged, if yes then what should be best way.
May I know if any one has done, has done this application
Thanks and Regards
Anu
We have tried taking capture by WISE 5.6 with all possible options i.e no exclusion list for files/registry, included files & reg deleted during capture, captured h/w entries, Allow root to be watched, capture non-microsoft odbc entries, enable self registration. All of the listed options above were tried with snapshot only capture, smart monitor capture, smart monitor + snapshot capture. But none of the capture works OK, the package shortcut when launched, doesnot recognise the h/w device. (The testing and capture are taken on a clean XP build)
As the capture didn't work, so we wanted to use the vendor MSI and create a transform. (by searching I found that RITSClientWISE_v1-9_20060629.exe copied from http://www.rba.gov.au/rits/software/ extracts setup.exe, CIP.msi & other components in C:\temp\RITS\iKey2000SDKMU18.) When tried to install CIP.msi it doesn't allow us to run directly and needs to run from setup.exe only (though ISSETUPDRIVEN=1 property value makes the CIP.msi run, but it tries to install all features of which source files are not available) now when the setup.exe is passed "/v l*v C:\temp\Rits.log" as parameter it creates a log file (I am sorry that I cannot attach the log file, request you to please run the command for genearting the log file)
The log file shows that setup.exe passes command line parameter to the CIP.msi, and when we try to pass the same command line parameter from a command prompt, to the MSI, the command gives error and cannot continue.
How can we make the vendor MSI install?
Can you please advice if this kind of applications can/should be re-packaged, if yes then what should be best way.
May I know if any one has done, has done this application
Thanks and Regards
Anu
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
karan_gupta
17 years ago
Anu , I checked the application that you mentioned and found out that the package has 2 parts
1) the first part goes for installing Java Runtime Envrionment which is in form of an Msi
2) The second part is in the form of an exe , which has been made using Installshield . You can try to capture that exe using setupcapture, and if you are not successful than you can try to make a response file of this application.
1) the first part goes for installing Java Runtime Envrionment which is in form of an Msi
2) The second part is in the form of an exe , which has been made using Installshield . You can try to capture that exe using setupcapture, and if you are not successful than you can try to make a response file of this application.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.