Errors After Installation

[Shahram]

I have set the WPI batch file to restart the computer after the installations are done,

I noticed there are some errors coming up that I guess are due to shutdown,

one of them complaining about Rundll32.exe:

I remeber some errors about "advpack.dll" too,

How can I avoid those.

Edit:

they disappear immediately because windows restarts and there is no side effects , I could catch this screeb by taking a movie of the screen.

Edited March 22, 2006 by Shahram

[Shahram]

Got the two other errors ,

and

These are after the installation, and there is nothing to be installed at that time.

I have no Idea where these came from.

I guess the first one might be related to IE7 that I am installing.

[Avneet]

wat command are u sing to retsart the computer

[Shahram]

simple "shutdown -r -f -t 0"

[Avneet]

ok

shutdown.exe -r -f -t 30 -c

i think the problem is that windows starts loading sum applications.. so u need to give it some time ..maybe 30 seconds

example is given above

[Shahram]

I don't want the windows to start anyways,

cause I have applications that I do not want them to run on the first start, infact their first start is important which should be after a restart,

30sec? isn't that almost windows starts running completely, and then you are looking at the windows loaded and waiting for the restart?

or does it wait for the shutdown?

hmmm...

[Shahram]

Ok,

I guess all the problems were related to ADVPACK.DLL

the ADVPACK.DLL which was in the System32 folder was :

6.00.2900.2180 (xpsp_sp2_rtm.040803-2158)

But the ADVPACK that "Internet Explorer 7" contained and needed and many other programs also needed was:

7.00.5296.0 (winmain(wmbla).060125-1505)

I just compressed the new version to ADVPACK.DL_ and replaced the original in I386 folder.

Edited March 26, 2006 by Shahram

[Shahram]

the same about , WININET.DLL

[BoardBabe]

You should still give windows some time to load, reboot/shutdown with no delay are likely to cause problems.

[Shahram]

Since runonce is before starting of windows, it should not cause any problems,

Thise DDL problems were happening even if there was no restart,

First I was thinking silently unlock those old DLL files and copy the new ones at the end of WPI,

But Now, I am thinking of starting the shutdown process from the WPI batch file and waiting for it, that means, the installation never gets finished to start the windows files,

And the DLL erros does not show up again, cause the first time windows loads up, they are not registered, but a restart fixes the problem without the need of manually putting the DLLs there,

Infact I think, giving time for windows to start could cause problems, as there will be programs like IE7, that if installed from RunOnce, their files are not in place (registered) untill a restart.

and starting of windows without a restart can be problematic.

[BoardBabe]

After RunOnceEX ends it will start launching Windows, you abort this operation when you call your restart. personally I would recommend letting Windows fully load before you call that system reboot...

[Shahram]

Ok

I think the best is to restart the windows without letting the windows to finish with RunOnceEx and start initializing windows components, with this command at the end of WPI.CMD

start /w shutdown -r -f -t 00,

(waiting for shutdown)

There should be No Errors, No side Effects, No event logs, No early intialization of the programs specially if they need a restart to function properly.

Edited March 30, 2006 by Shahram

[Shahram]

or this autoscript should take care of it, making sure the shutdown doesn't close the original process causing starting of the windows in slower computers,

$run= @ComSpec & " /c " & @ScriptDir & "\WPI.CMD"
RunWait($run,"",@SW_HIDE)
Shutdown(6)

only the exe remians, that I am thinking of moving to windows folder for execuation.

[Avneet]

where do u put that script