i think there is only one solution to this problem...
thoroughly test your silent install scripts before doing a full unattended
install
maybe the appsonly script can be useful for this
Michael
On Thu, Feb 21, 2008 at 12:12 AM, Spam Proof <[EMAIL PROTECTED]>
wrote:
> Quiet installs using msiexec become interactive installs if there is an
> error in the command-line arguments.
>
> For example the following quiet install:
>
> msiexec /qn /l* perl-log.txt /i ActivePerl.msi PERL_PATH=Yes PERL_EXT=Yes
>
> becomes interactive if a command-line error is introduced:
>
> msiexec /qn /l* /i ActivePerl.msi PERL_PATH=Yes PERL_EXT=Yes
>
> Is there any way to make msiexec quiet, completely quiet, no matter what?
> Is there a non-interactive version of msiexec? A single error in msiexec
> arguments can hang an unattended install indefinitely.
>
> Thanks
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> unattended-info mailing list
> unattended-info@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/unattended-info
>
>
--
Michael De Groote
ICT-coordinator Sancta Maria Basisschool Leuven
ICT-coordinator Sint-Pietersschool Korbeek-Lo
ICT-coordinator Scholengemeenschap Katholieke Basisscholen Leuven
ICT-coordinator Parkschool Leuven
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
unattended-info mailing list
unattended-info@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/unattended-info
