Thanks - and Install Shield x 6??? (OpenInsight 16-Bit Specific)
At 08 OCT 2002 05:52:04PM Robert Lee wrote:
Happily it is now time to publish the latest app. Thanks to everyone in the Rev community for your contributions over the last five years or so. I'm not sure how we programmers ever survived without a forum like this.
Of course, I am wanting Install Shield to handle the installation (OI 3.7.5).
Please correct me if I am wrong, but for a fresh installation, I have to run 4 OIPI Setup programs?
1. OIPI 4.0.1
2. OIPI 4.0.1 Pro (which must be installed over an existing non-Pro)
3. OIPI 4.0.2
4. OIPI 4.0.3
I then have to run the Setup Program in the Oinsight directory to enable the access to the long filenames (Utility_GetFolder etc.). That makes 5 Install Shields…
This would all presumably be after running my own customised Install Shield for copying the app off the CD and setting up the icons etc., which is a total of 6 times Install Shield gets to run.
If I am understanding this correctly, then all this seems just a bit excessive to me. Is there a way for me to combine all these into one Install Shield Session or is this a job for Revtech? For new installations, is everyone else running all these Install Shield sessions?
TIA
Robert Lee
At 09 OCT 2002 08:19AM Don Miller C3 Inc. wrote:
Yup and I add one more since I deploy the data files in a separate installation. It is possible, however to chain them together.
Don M.
At 10 OCT 2002 12:27AM Donald Bakke wrote:
Robert,
I guess I'm missing something here. If this is a "fresh" installation then why don't you install the OIPI upgrades locally so your clients don't have to? Just deploy an already updated OpenInsight. If you are creating your own InstallShield setup then you can simply combine the critical DLLs/OCXs from both OI and OIPI into the one and same setup. This is exactly what we do.
At 14 OCT 2002 01:35AM Robert Lee wrote:
Hi Don
]I guess I'm missing something here. If this is a "fresh" installation then why don't you install the OIPI upgrades locally so your clients don't have to? Just deploy an already updated OpenInsight.
Are you suggesting that if the system I burn onto CD is uptodate with the latest OIPI, I don't have to run all four upgrades? I still would of course have to run at least one version of the OIPI on the clients machine. Which version would that be then?
]If you are creating your own InstallShield setup then you can simply combine the critical DLLs/OCXs from both OI and OIPI into the one and same setup. This is exactly what we do.
I am very new to Install Shield. The way you describe it sounds very simple and exactly what I would like to do. How then is that accomplished?
Robert Lee
At 14 OCT 2002 09:42AM Donald Bakke wrote:
Robert,
Are you suggesting that if the system I burn onto CD is uptodate with the latest OIPI, I don't have to run all four upgrades? I still would of course have to run at least one version of the OIPI on the clients machine. Which version would that be then?
Yes, that is what I am saying. If you wanted to still run the OIPI install (in order to avoid having to merge this installation with your own application's install) then just install the last OIPI that puts DLL's on to the system. I don't know which one that is since we went from OIPI 3.80 and OI 3.7.5 directly to OIPI Pro and OI 4.x.
If you are willing to do some investigative work, I would still recommend that you discover which DLL's and other system files the OIPI uses and just add those to the InstallShield that you'll use for your application. This will allow you to avoid a separate OIPI installation altogether. In our application installation we allow the user to select a "Full" or "Client" installation. Both the "Full" and "Client" installation installs OI/OIPI DLL's.
I am very new to Install Shield. The way you describe it sounds very simple and exactly what I would like to do. How then is that accomplished?
I have not seen InstallShield 6.x. We've worked with v5.x and are just about to work with v7.x. There appears to be a big difference in how the interface works so I don't want to give too much detail as it might confuse matters. Also, it will depend whether you are using the Professional version or the Express version. The Professional version gives you far more control over your InstallShield projects. Part of that control is the ability to specify File Groups. Each File Group will install specific files of your choosing. Typically you put files of like extension (e.g. *.exe, *.hlp, *.dll, etc.) in its own group. This way you can create your own install options (e.g. "Full", "Client") and choose which File Groups get installed with which install option.
I have never used the Express version so I can't tell you how flexible it is. I am almost certain others on this board have used InstallShield Express so someone should be able to let you know if you can do what I'm describing.
At 15 OCT 2002 06:49PM Robert Lee wrote:
]then just install the last OIPI that puts DLL's on to the system. I don't know which one that is since we went from OIPI 3.80 and OI 3.7.5 directly to OIPI Pro and OI 4.x.
Perhaps this thread deserves some input from Revsoft. There does appear to be a void of knowledge here. Perhaps a white paper on the subject would be helpful. What say you Mike?
Is anybody else using Install Shield / Install Shield Express to accomplish a full one-stage installation?
Thanks Don
Robert Lee
At 20 OCT 2002 06:34PM Robert Lee wrote:
Hi Don
Do you use Install Shield or Install Shield Express? What version? How does one go about chaining them together?
What are the critical .DLL and .OCX files that Don talks about?
Questions, questions, questions…
TIA
Robert Lee
At 21 OCT 2002 08:07PM Carl Harris wrote:
Hey Robert,
Long time no hear, see
Hope things are going well for you.
I guess I can help with this situtation this is a list of the files that will need to bee copied to the WINDOWS/SYSTEM directory in your install script:
COMPOBJ.DLL
CTL3DV2.DLL
OC25.DLL
SCP.DLL
STORAGE.DLL
TYPELIB.DLL
VB40016.DLL
VAEN21.OLB
STDOLE.TLB
OLE2CONV.DLL
OLE2DISP.DLL
OLE2NLS.DLL
OLE2PROX.DLL
OLE2.REG
OLE2.DLL
VSVIEW3-.OCX
SSUTIL.OCX
They will also need to be registered on that machine, Install Shield has a feature that automates this.
If you need any help call me at the office I am more than happy to try and assist.
Regards,
Carl
At 21 OCT 2002 08:48PM Robert Lee wrote:
Hi Carl
Good to hear from you and thanks for the response.
Are doing the "one stage" install? Are you using Install Shield or Install Shield Express?
Robert Lee
At 21 OCT 2002 11:01PM Carl Harris wrote:
We are using InstallShield Express 3.5 as we do not need to create web install packages nor do we need to create .NET compliant MSI's which the professional and development version do.
We have fine tuned the installation script so that to the end user it is a single process, including the installation of oipi. The only thing that was tricky was setting it up to handle a cocktail of Operating Systems.
If I can help futher let me know