Hi Stefan,
Pendl Stefan wrote:
> Hi Rainer,
> there is currently no upgrade task defined, so there would be nothing
> done.
> Hope this is no error for WPKG.
This is absolutely OK for WPKG (unless you discover an unexpected bug
;-)). WPKG should execute the upgrade commands (none in this cas
Hi Rainer,
there is currently no upgrade task defined, so there would be nothing done.
Hope this is no error for WPKG.
---
Stefan
Rainer Meier wrote:
Hi Stefan,
Pendl Stefan wrote:
> Hi,
>one last thing, since I already installed some machines using the package
> definition and altere
Hi Stefan,
Pendl Stefan wrote:
> Hi,
>one last thing, since I already installed some machines using the package
> definition and altered it now to use a batch file for the remove task, will
> it be sufficient to increase the version number of the package to get the
> remove information upda
Hi Stefan,
Pendl Stefan wrote:
> Hi Rainer,
> so if one uses batch files to choose the correct installer he has to use
> them for the other tasks too.
> Thanks for the info.
You don't need to use the same method for install/uninstall - you could
also hard-code it in the package. However I fo
Hi,
one last thing, since I already installed some machines using the package
definition and altered it now to use a batch file for the remove task, will it
be sufficient to increase the version number of the package to get the remove
information updated on the already installed clients?
Tha
Hi Rainer,
so if one uses batch files to choose the correct installer he has to use
them for the other tasks too.
Thanks for the info.
BTW, I noticed that your install batch file has a spelling error in the custom
installer procedure it set the exit code to ERRORLEEL (missing V) ;-)
---
Ste
Hi Stefan,
Pendl Stefan wrote:
> Currently I have the following two lines in the package:
>
>
>
>
>
> Is ther something similar like the following:
>
>
> path='%ProgramFiles(x86)%\UGS\Teamcenter
> 2007\Visualization\Program\PLMXMLConverter.dll' value='7.1.0.8338' />
> p
Hello,
I do have an application that has different application ID's for
MSIEXEC, one for the x86 and one for the x64 version.
I am installing both by running a batch file which runs the correct installer
based on the processor architecture.
Currently I have the following two lines in the