New Error Found

[Astalavista]

ERROR

a script on this page is causing Internet Explorer to run slowly. If it continues to run, your computer may become unresponsive.

SOLUTION

[HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Styles]
"MaxScriptStatements"=dword:ffffffff

i can install all 50 programs,

including my huge programs like norton internet security 2005, corel draw 12, photoshop cs, office 2003, frontpage 2003, net framework.

for those of u going to install huge applications u need to add this to your regtweaks.reg

-----------------------------------------------------------------------------------------------------

in cleanup.cmd

add this code

reg delete "hkcu\software\microsoft\internet explorer\styles"

[hasi001]

That's a prob with 3.2

That's because of the new dependency checking. Recursions make it slow, it seems....

[Astalavista]

removed

[hasi001]

3.2.0 is a tryout. Stick to Version 3.1.3a meanwhile.

[Astalavista]

removed

[Astalavista]

removed

[bonedaddy]

Man I'm so glad to hear this, it just so happens I made a new msi and tried

it as well as 3.12 and got that slow down message, thought it was the new

msi...............

BD

[Astalavista]

removed see first post

[BritishBulldog]

worked perfect for me with the config.js from the downloaded version

[Astalavista]

see first post

[BritishBulldog]

@Astalavista

i just tried yours out but without installing the progs as i have not got them all.

It just added everything to the registry and went on from there

no probs, maybe that is because of memory probs after installing so many programs?

[bonedaddy]

I'm not sure about this, I'm going to test this out now......

I know Asta and I use wait.exe, the popup comes right after

or during the program with wait, it's set for 60sec.

I'm going to change it to 35sec should get away with that time..

I'll let ya know..............

BD

[hasi001]

The prob could come because WPI running in background. WPI utilizes IE - so the command prompt says it's IE. Could really be that Wait thing. - nothing happens, time elapses, WPI in background running --> Windows might think WPI is doing this. Since WPI waits 'til the runonceex process is finished windows thinks WPI makes that wait - not the runonceex process.

I don't think it's WPI's failure ... but I also cannot prove that. Have you tried without wait.exe ?

[Astalavista]

see first post

Edited January 2, 2005 by Astalavista

[Astalavista]

There appears to be a threshold on how long WPI can wait for a certain process to finish.

Example if I have A , B , and C

If let say A install finishes, and for whatever reason B takes a long time to finish, like wait command 1000 or it hangs bec. There is an error. You will get that message pop up.

So to resolved the issue I decreased my wait to 400