[Pliek]

Have been testing on two latest versions today with same config.js
Version 5.0.1 takes 20 seconds (looks normal to me) to close after 192 programs, but 5.1 takes 25 minutes.??????
So I stick with version 5.01 because this is for sure a version related problem to me, maybe it's a bug...that I can't tell.
Anyone??????????

This post has been edited by Pliek: 27 July 2006 - 06:02 AM

[Djé]

Pliek, on Jul 27 2006, 12:55 PM, said:

Version 5.0.1 takes 20 seconds (looks normal to me) to close after 192 programs, but 5.1 takes 25 minutes.??????

Pliek, can you please just confirm that the 20 seconds you're talking about are taking place AFTER all the installations are finished (and that it's NOT the TOTAL installation time). Sorry to inquire about this, but I'd prefer not to follow a dead track if I'm to investigate on this issue.

Installer in 5.2 will be somewhat different but we'd better be sure that this problem is 5.1 specific.

[Pliek]

Yes After installing all the programs the waiting to close mshta.exe is 20 seconds in version 5.0.1
In the latest ( 5.1 ) It's mutch longer like I told above here.
The 20 secs. do not get less if I install. 5 apps. or 10.. in version 5.0.1 it stay's stable (20 seconds) no matter how mutch software I install.
So there is a different between these two installer going on...

Thanks Djé for your reply, hope to hear soon from you.

[mritter]

In core.js make sure the Pause() function is like this:

function Pause(secs,milli)
{
	position="core.js";
	whatfunc="Pause()";

	var SleepShell = new ActiveXObject("WScript.Shell");
	var duration, sleepCmd;

	duration="-m " + ((secs*1000)+milli);
	sleepCmd=wpipath+"Tools\\Sleep.exe";
	SleepShell.Run('"'+sleepCmd+'" '+duration,0,true);

}

The duration line had an issue earlier.

[Pliek]

Mine looks the same:

function Pause(secs,milli)
{
	position="core.js";
	whatfunc="Pause()";

	var SleepShell = new ActiveXObject("WScript.Shell");
	var duration, sleepCmd;

	duration="-m " + ((secs*1000)+milli);
	sleepCmd=wpipath+"Tools\\Sleep.exe";
	SleepShell.Run('"'+sleepCmd+'" '+duration,0,true);

// If you have any issues with security prompts on Server 2003, use this line
//	SleepShell.Run('cmd /c "'+sleepCmd+'" '+duration,0,true);
}

When testing this problem in 5.1, I saw in taskmanager sleep.exe appear an again disappearing many times like its in a loop.

Hoop this is helpfull information?

This post has been edited by Pliek: 27 July 2006 - 12:02 PM

[Pliek]

Could someone please try out my WPIScript folder.
I have posted it on rapidshare.
http://rapidshare.de...cripts.rar.html
Try out the debug mode and find out yourself.

This post has been edited by Pliek: 27 July 2006 - 02:16 PM

[sadicq]

It looks like the error is related to SetScriptWaitTimeout() and its call inside generate.js. <-wrong
I'll post back as soon as I discover the exact cause.

This post has been edited by sadicq: 27 July 2006 - 03:35 PM

[sadicq]

Hmz ... interesting .. I found the problem, I don't know if what I'm doing is right, but hell it works!
Open installer.js, search for

if (!InstallWindow.closed)
		InstallWindow.close();

and replace it with

//if (!InstallWindow.closed)
		//InstallWindow.close();

And I must say I'm impressed about how fast it disappears ...

This post has been edited by sadicq: 27 July 2006 - 04:25 PM

[Djé]

@Sadicq: you may well be true.
@Pliek: sorry, I did not investigate too much in this direction because this code won't exist anymore in 5.2. (the bug seems to be specific to 5.1).
In the next version, the installer code will be quite simpler and thus more robust (or at least one can hope so ).

While waiting for 5.2, you may want to give a try to sadicq's fix.
Like he said, it may not be right, but hey, if it works...

Please keep on reporting your success/failure here.

[Pliek]

Both...sadicq and Djé thanks ..........
Will try out right away, and post results today.

[Pliek]

And you both did it again, you solved the problem.
Restarting takes now 2 seconds.......COOL.
Stick with 5.1 now.
Thanks sadicq and Djé.....where would this end without you 2.

This post has been edited by Pliek: 28 July 2006 - 04:15 AM

[sadicq]

I know that removing that code is not what a programmer would suggest, but if you look closer, the way the installer window is created permits you to skip the install close part.
I don't know exactly what you guys are working on (we are working separately), but if the installer window will remain the same, you should skip the part with the installer window closing... or at least make the wpi not create the layout and check boxes again (for a large config that takes quite a while). That was the main reason why the installer stalled. I did not write these explanations together with the fix because I was not sure whether it will work.

This post has been edited by sadicq: 28 July 2006 - 04:58 AM

[Pliek]

Doesn't matter you both made me glad again and it's working great now, isn't this topic therefore.
Thanks