Re: [Unattended] Multiple-step setups, problem with "visibility" of new environment variables

> The reboot is necessary because the Ingres-Client software defines a
> new environment variable II_SYSTEM (pointing to the Ingres
> installation path) and the Ingres-Client-Servicepack setup *must see*
> that variable in order to run through. If I leave out the reboot, the
> service pack installation does not work.
>
> So the question is: how can I achieve in "multiple step" scenarios
> that the second step will see environment variables set by the first
> step *without* having to reboot?
>
>    
well, try to add  a path for the user:

set II_SYSTEM=C:\Ingres

|reg add HKCU\Environment /v PATH /d "%II_SYSTEM%;%path%" /f|



http://superuser.com/questions/65816/setting-or-modifying-a-system-wide-environment-variable-in-cmd-exe

------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d