WPI and TGUP Offline Installers

[crunch81]

Something I'm trying to find out for a long time:

I'm using the Great GREAT great unattended project offline installers. It will make .bat scripts to install programs (Like Autoit)

Now my problem is that when I put the programs into WPI, Wpi will not wait with the next program untill the previous program has finished. What happens is

that multiple programs will start installing at the same time and errors will occure.

How can I bypass this???

Thanks for the reply.

[Kelsenellenelvian]

WPI by itself cannot bypass this.

You will HAVE to add a sleep command to wait until the installer is finished or correct the tgup commands so that the parent command (i.e. a .bat file or auto-it file) waits for the installer to finish before closing.

WPI waits for the installer (The original .bat or au3 file) not any sub-processes....

[crunch81]

WPI waits for the installer (The original .bat or au3 file) not any sub-processes....

This is strange because the "installer" finishes and closes with "done" and then the "Installer" dissappears. So why doesn"t WPI see this as a process?

Adding sleep commands is not an option for me because I'm making an unattended program with 6 different OS Software with WPI integrated in it. It will be used to install new computers at my work. When I add sleep command for 30 seconds and then with the next program for 50 seconds and so on.... Then it will not work the same on every computer.

Do you know how to change the inst.bat file that it will wait till it's done?

I also think it's strange that I coulnd't find it anywere on the forum, I thought that I would not be the only one with this problem.

I want to thank you very much for your reaction and I hope that you can send a reply on this post again.

Thank you!

[tecnikk]

This is strange because the "installer" finishes and closes with "done" and then the "Installer" dissappears. So why doesn"t WPI see this as a process?

Adding sleep commands is not an option for me because I'm making an unattended program with 6 different OS Software with WPI integrated in it. It will be used to install new computers at my work. When I add sleep command for 30 seconds and then with the next program for 50 seconds and so on.... Then it will not work the same on every computer.

Do you know how to change the inst.bat file that it will wait till it's done?

I also think it's strange that I coulnd't find it anywere on the forum, I thought that I would not be the only one with this problem.

I want to thank you very much for your reaction and I hope that you can send a reply on this post again.

Thank you!

Hello Mate

Im doing the same as you for multiple isntalls and i tried the sleep but it juast messes up most of the times.

TGUP wont tellyou how to do it becauseyou cant and they dont really want you toknow how to overcome it because

you can change all the code they used. but its easy and i figured it out.

When your the insatll with the wait option from a batch or even wpi- it does wait - butonly for the package to unpack but not for the batch that is run afterwords.. sooo

You need to unpack the installer file into your directory

and then run the batch file with start /wait inst.bat

[from wpi you might not need the start /wait command]

because this is the file that does all the work. If you want you can change a few things in the batch like remove

the line that deltes the desktop icon or change the title name.

or if you dont want any tweaks just copy the start /wait command from inside the batch and use that in your program / batch instead to do a normal silent install as intented by the orignal program.

Thanks to the TGUP Group for providing these files and all credits that belong to you are yours :]

Thwere is a program called ninite pro that does all this with automatic upated no tweaks or any other priogramming, but they recently started charging 20$ per month.. bit steep but they assured me they a reviasing the charges.

Have fun

[crunch81]

Thanks so much for sharing this info! I did reported this issue with the creator of the program. He already fixed it for us. When

you download the installers again, it will work.

Thanks!

Edited January 20, 2010 by crunch81