Reboot in CMDLINES.TXT

[Ascii2]

If I include a command to reboot computer during the execution of CMDLINES.TXT, would CMDLINES.TXT run again from its beginning?

Should a reboot occur at all?

Would setup not function correctly if a reboot is invoked in CMDLINES.TXT?

[MCT]

i dont think setup would function right, it'd just loop

[Ascii2]

Looping is also what I though would happen.

I thought that it may be that an exception for such a thing may have been built-in.

[MCT]

if u really wanted to force a reboot i would do it after the 1st logon.. but i dont see the point

[Yzöwl]

I've had an installation hang from scvpack, (roughly T13 as cmdlines), and when the reboot was forced setup continues again from T39, suggesting that it should loop.

[Ascii2]

if u really wanted to force a reboot i would do it after the 1st logon.. but i dont see the point

I was wanting to apply updates to system applications and components that require a reboot after the application installations prior to first logon.

Normally with attended installations of components or applications of DirectX 9.0c, Internet Explorer 6 SP1, and Microsoft Java Virtual Machine complete, a reboot is required by the setup.

Edited October 29, 2008 by Ascii2

[Christine_ts]

Why force a reboot ?

The installation doing the last "Registration Component, then save and so reboot anyway

[Ascii2]

Why force a reboot ?

The installation doing the last "Registration Component, then save and so reboot anyway

The only reason I can think of is to be able to run commands or installations early in Windows GUI setup for which prior components must already exist for the installations or commands to be sucessfull (like installing something dependent on network components); the components may already exist from a previous loop. Conditional statements would have to be used to not remain indefinately looping.