Re: One package, three uninstalls

From: Chad (chad.varnerREMOVE_CAPS_BUT_DONT_OFFER_ME_AN_SMS_JOB_at_eds.com)
Date: 03/09/04 

Date: Tue, 9 Mar 2004 13:10:47 -0800

To expand a bit... the first component is my main
software package; the second component is a collection
of "runtime" files, supporting DLL's and such; the third
component is some communications software to assist the
main application with, uh, communicating. Depending on
the situation, the second and third components may or may
not be needed for a particular delivery. All three
components are conditionally compiled into the package.
For reasons difficult to explain, I cannot leave it up to
the user at the other end to decide which components to
install.

Upon further experimentation, it is only the main
component's logfile that disappears. If this particular
compilation includes only the main applicatoin software,
its logfile is created properly. If the second and/or
third components are also included, they get their proper
logfiles, but the main application does not.

Finally, this is unrealistic but theoretically possible,
if I don't include the main application, but include the
second and third components, they both get their proper
logfiles - so it doesn't seem to be a situation where the
first logfile used is discarded if subsequent logfiles
are also used. It appears to be something directly
related to my main component and its logfile. Darned if
I can figure out what, though.

>-----Original Message-----
>Hmm, interesting.
>You could create three scripts, one for each component,
compile them as
>exe's with the correct add/remove and uninstall info.
Then create another
>SMSI script that is just a wrapper script and contains
the three other
>setups and launch from within that?
>
>Or even just create the three scripts and deploy them to
the client
>separately??
>
>As for the modifications you are trying to make, I have
not tried to do that
>before. But I think the method above will work.
>
>Terry
>
>"Chad"
<chad.varnerREMOVE_CAPS_BUT_DONT_OFFER_ME_AN_SMS_JOB@eds.c
om> wrote
>in message news:9cf801c405e6$28bc69f0$a101280a@phx.gbl...
>> I have a single SMS Installer script that installs
three
>> separate components; I want the components to be
totally
>> separate applications, each with its own entry
>> on "Add/Remove Programs", each to be logged and
>> uninstalled separately.
>>
>> I've tried to accomplish this by slightly modifying
>> UNINSTAL.IPF, changing it to use a regular variable %
>> LOGFILE_PATH% instead of the default global variable %
>> _LOGFILE_PATH_% (note leading and trailing underscores.
>>
>> As I enter each section of the install, I set the
>> APPTITLE and LOGFILE_PATH variables appropriately,
>> I "open new installation log file %LOGFILE_PATH%", then
>> call uninstal.ipf.
>>
>> At the end of each section, I "Stop writing to
>> installation log".
>>
>> The end result is that sometimes it writes a log file
and
>> sometimes it doesn't. I tried adding a "Open new
>> installation log file" with no filename specified, at
the
>> end of each section, to try to force the old one closed
>> and flush it to disk. That had no effect.
>>
>> What am I missing?
>>
>>
>
>
>.
>

Relevant Pages