It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
avatar
Maighstir: ...if you keep the default names, and keep al installers in the same folder.
avatar
JMich: Still Life 2 (and Syberia 2) would be triggered by that, but I just moved the v2.x "to be installed" files in a seperate folder. Still, thank you.
edited for rudimentary v2 checking, also, I'm quite sure cmd only uses normal parentheses. not curly braces. so fixed that too
Post edited February 04, 2014 by Maighstir
avatar
Maighstir: ...if you keep the default names, and keep al installers in the same folder.
avatar
JMich: Still Life 2 (and Syberia 2) would be triggered by that, but I just moved the v2.x "to be installed" files in a seperate folder. Still, thank you.
Here's an exe that lets you pick a directory and will rapid install them: https://www.dropbox.com/s/a8ex2zzbxxja97e/gogv2-automation.exe

v2 Installers only!
avatar
opticq: Here's an exe that lets you pick a directory and will rapid install them: https://www.dropbox.com/s/a8ex2zzbxxja97e/gogv2-automation.exe

v2 Installers only!
Got this functionality through cmd and for, though running 36 installers at the same time may not have been the smartest of moves. Does the tool run them one after the other or all at once?

Will try it later today, when I grab the next batch of v2.x to install from my backup drive.
avatar
opticq: Here's an exe that lets you pick a directory and will rapid install them: https://www.dropbox.com/s/a8ex2zzbxxja97e/gogv2-automation.exe

v2 Installers only!
avatar
JMich: Got this functionality through cmd and for, though running 36 installers at the same time may not have been the smartest of moves. Does the tool run them one after the other or all at once?

Will try it later today, when I grab the next batch of v2.x to install from my backup drive.
Hmm, the batch should continue only when the launched application finishes... but I forget how Windows work, perhaps the GUI process is completely detached from the cmd.
avatar
Maighstir: Hmm, the batch should continue only when the launched application finishes... but I forget how Windows work, perhaps the GUI process is completely detached from the cmd.
Using for %i in (setup*.exe) do %i /silent launched everything, probably because the setups are not run in the prompt, but are separate programs. On the other hand, since the /silent doesn't exit the installers when they are completed, I guess I will have to use fewer installers per batch (or make sure I don't need the computer for the next few hours).
avatar
Maighstir: Hmm, the batch should continue only when the launched application finishes... but I forget how Windows work, perhaps the GUI process is completely detached from the cmd.
avatar
JMich: Using for %i in (setup*.exe) do %i /silent launched everything, probably because the setups are not run in the prompt, but are separate programs. On the other hand, since the /silent doesn't exit the installers when they are completed, I guess I will have to use fewer installers per batch (or make sure I don't need the computer for the next few hours).
Hmm, so Autohotkey (which I guess opticq is using) is a better solution, as it can automate the GUI and wait for each program to finish before launching the next.
avatar
Maighstir: Hmm, the batch should continue only when the launched application finishes... but I forget how Windows work, perhaps the GUI process is completely detached from the cmd.
avatar
JMich: Using for %i in (setup*.exe) do %i /silent launched everything, probably because the setups are not run in the prompt, but are separate programs. On the other hand, since the /silent doesn't exit the installers when they are completed, I guess I will have to use fewer installers per batch (or make sure I don't need the computer for the next few hours).
I just tried, seems like the only downside to the v2 installers is that its harder to figure out how to close the installer with the application finishes. It was much easier in the v1 installers. As of now, its one after the other.

EDIT: Its AutoIt, but yeah general idea
Post edited February 04, 2014 by opticq
avatar
opticq: EDIT: Its AutoIt, but yeah general idea
People still use AutoIt? I thought Autohotkey was practically a fork and successor of it, and that development of AutoIt had stopped.

*checks web* Oh, seems it had stopped, was forked, then resumed. Oh well, I started using Autohotkey way back when, then didn't bother looking at alternatives as it did what I wanted... and now I no longer run Windows, so neither is of much use to me.