Hi all,

Thanks Matt and Steve, your comments were greatly useful.
I was looking into msiexec options and didn't think to make use of the
perl scripts provided by unattended.
The reboot-on directive works fine in my case, I just tested it this
morning. :-)
Thanks a lot. :-)

Cheers,

Oliver

Dans sa grande sagesse, Matt Hyclak a écrit, le 19.05.2008 16:10 :
> On Mon, May 19, 2008 at 09:55:45AM -0400, Stephen Kojoukhine enlightened us:
>> >From http://unattended.sourceforge.net/apps.php:
>>
>> "...
>> For example, suppose you have an installer foo.exe which always exits with 
>> status 37. You would schedule it for invocation like this:
>>
>>     todo.pl ".ignore-err 37 foo.exe"
>>
>> This will add ".ignore-err 37 foo.exe" to the to-do list. When todo.pl 
>> processes this line, it will invoke foo.exe, silently ignoring exit status 
>> zero or 37. It will still treat other status codes as errors.
>> ..."
>>
>> Hope that helps you with ignoring the error, however I don't know why the 
>> installer fails otherwise.
>>
> 
> I think in general an exit status of 194 indicates the machine needs to be
> rebooted in order for the install to complete. You probably want
> 
> todo.pl ".reboot-on 194 ..."
> 
> Matt
> 

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

-------------------------------------------------------------------------
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

Reply via email to