Multiple Installations

[chaitanya051]

Sequential Installations

Hello,
This here is an arbitrary scenario.
I am looking for some information on multiple installation or sequential installation operations.
Like when an installer has to deal with more than one application in an installation package, how does it respond.
Does it roll back the entire operation if one of those applications is faulty or just may be not compatible er just doesnt work!
I would also like to know about conflicts that arise during such installations. Whether they would happen in a series or try to clash by getting parallel.
What steps are to be taken to ensure smooth installation of such packages?
I would want my installation to go on even if one the application fails to get installed. I would want my installer to ignore that instance and carry forward to other applications waiting in the sequence.
Any info would be appreciated.
Sorry the question is vaguely framed.
Please do share your thoughts on this.
Thanks in advance.

 

[LiquidSnak]

Well, if a program is written well, it will install sequentially, not simultaneously. However, it is the tendency of coding to come to a stop if something goes wrong, as the code has been interrupted. Usually a goto feature, or something of that nature. If you are writing the coding for an installer program, you could avoid the installer coming to a close by making the call or goto function lead straight into the next installation, but make a note of the failure in a log file.

 

[chaitanya051]

Well i would like to know how can we bring about a smooth installation in such situations
what modifications are to be made to the code in order to avoid conflicts during installation and freezing or roll back?

 

[LiquidSnak]

With my programming experience, I think it would be best to write several separate installers. One program (say, setup.exe) would then call each installer in sequence (say inst1.exe, inst2.exe, etc), without being given a report whether the installer failed or not. Though, I would also have each installer write its results in a single log file. That way, if the installer fails, and closes itself, the original .exe will not know and move onto the next line of code, which would be the next program to install in the sequence.

That way, you will not know until the log file is produced by all the individual installers whether an installation had failed, and could go back and manually run the installer again

 

[chaitanya051]

thanks for that snak
well that should do it then, though a little round about
but i will take it
what generally goes around in the industry in such situations??
how do major players tackle these problems?
would it be by proper coding or the fool proof methods you suggest
just curious

 

[LiquidSnak]

I have no idea, as my training in C and other code is limited to my own studies

Though I do know that Betheseda Softworks has used this method before on Oblivion GOTY edition to install expansions and the game at one time. One expansion failed for me, but the other one installed as well as the game last time.