• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 4775
  • Last Modified:

how i can install many program (winrar, realplayer,jetaudio,,.........etc)automatic in different computer in fasterway

hi all
i have many program in same (CD)(winrar, realplayer,jetaudio,adobe ,.........etc)and  i want to install these program in many  computer and these computer not same spesification i do not want use norton ghost i want to install these program automatic one after one mean i want to to put (CD) and press install and the program install automatic one after one(i see like this (CD)) how i can make like this CD

thanks
0
nasemabdulla
Asked:
nasemabdulla
  • 4
  • 3
  • 2
  • +5
1 Solution
 
nltechCommented:
http://wpiw.net/
and related forum:
http://www.msfn.org/board/index.php?showforum=93

"windows post install wizard" lets you create a menu-driven cd for installing apps and drivers (after windows install or anytime)...  you'll find tips and help in its forums for creating 'silent' installers for many apps and configuring wpiw itself.


also perhaps of interest is "nlite" for creating custom windows install cd's, including integrating updates, drivers & apps:
http://www.nliteos.com/
and its forum:
http://www.msfn.org/board/index.php?showforum=89


both programsare free.
0
 
Dushan De SilvaCommented:
Installsheild is best.

BR Dushan
0
 
nepostojeci_emailCommented:
:)
create a .BAT file on a install CD containing these lines:

//////////////////////
@echo off
call install_folder\winrar\setup.exe
call install_folder\realplayer\install.exe
call install_folder\jetaudio\jsetup.exe
...
//////////////////////

blah blah :)
I hope you get the point? :)
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
scrathcyboyCommented:
add to above comment, put PAUSE between each CALL line.  That give you chance to exit if one install go wrong, which often happens.  If you know they all install correct, then use comment above, it works!
0
 
nasemabdullaAuthor Commented:
hi nepostojeci_email
i try the code but it not work my i made mistake i do not know

thanks
0
 
nepostojeci_emailCommented:
First of all, you must make sure that all those installation executables
have an option to install silently (with the default settings), you need
to check that in the documentation of every installation, otherwise,
you'll see the installations dialogs appearing, waiting for you to press
Next..

Second, you need to copy/paste the exact path to your install files in
the .bat file. For example, suppose you have theese folders on a CD:

+ winrar
+ realplayer
+ jetaudio

and lets assume that the installation executables are:
+ setup.exe (for winrar)
+ install.exe (for realplayer)
+ autorun.exe (for jetaudio)

your .bat file should look like this:

@echo off
call winrar\setup.exe
call \realplayer\install.exe
call \jetaudio\autorun.exe


do you get the point? in the .bat file there are just lines
that call all those executables to run. But, it would be
far more efficient if you manage to find out what are
the switches for the silent install (without dialogs displayed)
when you find out those switches for each installation
your bat file will look something like this (for ex.):

@echo off
call winrar\setup.exe /silent
call \realplayer\install.exe /quiet
call \jetaudio\autorun.exe /noshow

or something similar.
0
 
nepostojeci_emailCommented:
sorry, typo. It should look like this:

@echo off
call winrar\setup.exe /silent
call realplayer\install.exe /quiet
call jetaudio\autorun.exe /noshow


(removed the backslash in front of install folders)
0
 
BillDLCommented:
nasemabdulla,
I agree with nepostojeci_email in recommending that it is VERY important to ascertain the possible setup switches that are available for ALL of the programs and applications that you intend to try and install sequentially (either from a DOS batch file or by some other scripted method).

There are some install routines that require a reboot to run a command from a script or from one of the registry's "RunOnce" keys.  Usually this reboot is required to do something like update a Windows System File or a program file that otherwise might resist being updated while in Windows mode, or while some components of related software is being used.

You mention "adobe" as one of the programs you may wish to install in this way, but you haven't said whether you mean Adobe Acrobat Reader or some other Adobe application.  The reason I mention this is that you MAY, without being fully aware of it, have some other Adobe application installed eg. an image editor that came with a scanner or something.  Programs by the same makers often use "shared" files, and that is what I was meaning when I spoke above about having to "update a file".  Perhaps Adobe is a poor example, but take another example of a "Multimedia" application that decides it wants to update some of the multimedia files installed by Windows and shared with other applications and Windows itself.  The last thing you would want to do is to tramp on with the next multimedia program installation in case that also wants to try and update the same files.  Windows wouldn't know where it was at when it was eventually rebooted, and wouldn't have a clue what versions of the files should be present.  Hmm, maybe that's a poor example also, but hopefully you will follow the idea of what I am saying.

Although BR Dushan maybe didn't catch the drift of what you asked, or just didn't expand on how you would use his suggestion, he he did mention something that is important, ie. "InstallShield".  Some installation setup.exe files are nothing more than a self-extracting zip file that unpacks to a folder (or as loose temporary files) in the C:\Windows\TEMP folder, and then runs setup from there using an .INF, .INI, or other instruction file for the required steps to take.  More recent ones use an .MSI file that is loaded and run by the "Windows Installer" program file msiexec.exe.

There are a LOT of possible setup switches that can be used with msiexec.exe which allow you to take more control over how the installation proceeds.  One of these is the switch that tells it to "reboot only if required", whereas another is "always force reboot".

See here:
http://msdn.microsoft.com/library/en-us/msi/setup/command_line_options.asp

The actual "package" that you double-click to install the program may have been written with InstallShield (or any number of other "installer makers"), and may offer different command line options to run that "package" than from the setup options that it uses internally when it temporarily unpacks and then runs its own setup.exe.

Probably the best way to determine what different setup processes do for different program installers is to any of the following (in no particular order of preference):

1. Go to the program creator's support website and see if they list command line options for their program installer files.

2. Read the "readme" files to se if they provide something like "setup options for system administrators".

3. Start the installer but stop before it actually begins to run the proper install routine.  Open Windows Explorer (use Alt + Tab or Ctrl + Esc if the installer page dominates the screen) and go to your "TEMP" folder to see what components it has unpacked.  Copy them out to a neutral folder and then either cancel or continue the installation.

4. Extract the files from the setup.exe or install.exe files to their own folders if this is possible (using WinZip or WinRAR), and read any .ini, inf, stf, etc files in notepad to try and get an idea what they do.  If they mention the installation of files that you know to be Windows System Files, then there it is probably best that this installer be allowed to reboot the system when it prompts you to (in which case perhaps it shouldn't be installed in sequence with other programs).

5. After installation, try and locate an installation log that may provide details of exactly what it did.

6. If an installer prompts you to reboot, don't click the OK button immediately.  Instead open REGEDIT and see if it has created any commands in any of the following registry keys:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\RunOnce
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunOnce
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunOnceEx
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunServicesOnce
Export that key to a .REG or .TXT file and close REGEDIT, then allow the reboot to continue.
Any command added to these keys is, as the name implies, run just once at the next reboot.  This can give a better picture of whether an immediate reboot is preferable, or whether it could wait until other programs are installed in sequence.

In case you are wondering why nepostojeci_email used the "CALL" at the start of each line, this is to do with the way a batch file processes itsa commands.  When you CALL an outside program, it passes control over to that process and waits for it to finish. The batch file is still open, but it SHOULD have waited until that outside process ended and control was returned to the batch file.  Without this, it would start up each installation right on top of the other.

Another way that batch files can force a pause in the proceedings is to use the START command with the /wait switch, eg.
start /wait setup1.exe
start /wait setup2.exe
etc.

In general, I think the kind of CD's you have probably seen that allow you to install a number of programs at one time are like the "Chipset Driver" CD's that come with a new motherboard, or maybe CD-Writer Software where you tick the boxes for what programs you wish to install, and then click the "OK" button.  These usually CREATE a "Script" based on your choices, and that then provides the instructions to the installer so it knows what to do.  That's where BR Dushan's suggestion of "InstallShield" comes in, because that is not really something you could do with a simple batch file and is why software developers are paid so much :-)

No harm in trying the batch file method out, but DON'T test this on a computer containing valuable data, because one or other of the program installers might mess it up.  Do it on a test computer.

Bill
0
 
BillDLCommented:
nasemabdulla,

scrathcyboy also made an important observation about what would happen if something went wrong with one of the program installers, and suggested that you put a line containing the PAUSE command after each command to run an installer.  That way, it stops on the line "press any key to continue" and you could just close the DOS Window to stop further installation commands.

In batch code, processes use what are known as "Exit Codes".  This is the code returned to the program that called the process so that it knows what the status is.  In general, a returned code of Zero means that the process or command completed successfully, and anything other than that can mean an error or any other thing that is written into that program for a particular reason.

Using this MIGHT help to prevent the batch file from proceeding if an error occurs, but not all programs work the same way.  An example of this would be (taking the example batch file code from Comment from nepostojeci_email)

@echo off
call winrar\setup.exe /silent
if not errorlevel 0 goto :ERROR
call realplayer\install.exe /quiet
if not errorlevel 0 goto :ERROR
call jetaudio\autorun.exe /noshow
if not errorlevel 0 goto :ERROR
goto :SUCCESS
::
:ERROR
cls
echo.
echo  An error has occurred - Unable to continue
echo  Aborting batch file
PAUSE
goto :END
:SUCCESS
echo Success
PAUSE
:END
EXIT
 
In THEORY, if an error situation arose that returned any code other than the successful Zero one, then the batch file  would tell you this and abort the sequence.  That's the theory, but as I said this might not work with some processes, and it may well just interpret the fact that setup.exe was just CALLED successfully whether or not it installed and ended successfully.  It's something to consider though, and if any of the program installers caused you problems like this enough that you needed to go into it this deeply, you would be better off buying a program that allows you to BUILD proper 32-bit Windows installation packages for CD yourself.

Bill
0
 
nltechCommented:
why mess around with batch files, when the windows post install wizard http://wpiw.net/ takes care of all the dirty work?  it includes settings for some popular programs to silently install (and help for others can be found in its forums)...  you end up with a nice cd that you can use on any system, whether it's a fresh install or not; has a menu-driven interface in case you want to change what gets installed, and you can set it to auto-execute your default selection after a timer countdown.

and nlite http://www.nliteos.com/ can add extra program installers to a customized windows install cd, and incorporate drivers and windows updates too.

good peer-to-peer help can be found in both programs' message forums. and they're both *free*
0
 
nasemabdullaaCommented:
hi  nltech
thanks all for your comment
dear  nltech iam download windows post install wizard and it very good program
and i try to use it and i enter to form but i do not know how i can use it can you help me

thanks
0
 
nepostojeci_emailCommented:
nasemabdullaa, you can't use double accounts here.. if you have problems logging
with your first account, contact the admins to solve that problem, but with this
second account, you're acting like an anonymous, not the author of this question.
0
 
turn123Commented:
nepostojeci_email,

Thanks for pointing out the dupe account issue.  Just thought I'd make the general comment that these things get resolved a lot quicker if you report them to http://www.experts-exchange.com/Community_Support/ so a Mod can handle them.

There isn't really any guarantee that anyone will see your helpful comment buried in a thread like this and it might tend to offend the user it's directed at.

I appreciate your trying to help this user :)
turn123
0
 
Dushan De SilvaCommented:
Helllo nasemabdulla,

Did you tried with my comment?

BR Dushan
0
 
BillDLCommented:
Yes, I tend to agree that nltech's suggestions are probably the best way to automate custom installations.
In reality, it may actually take as long (or longer) to configure the WPI installer package as it would to create a batch file, but the end result would certainly be more professional and would probably be able to accommodate other options not possible from a batch file. WPI is a lot less hit-and-miss than writing and testing a batch file while keeping your fingers crossed.
0

Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

  • 4
  • 3
  • 2
  • +5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now