[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Progress batch installation
Jest to parametr -r . Przyklad wywolania:
setup.exe -r -f1C:\<path-to-file>\setup.iss
[-f2C:\<path-to-file>\setup.log]
Ponizej fragment z installation notes.
Pozdrawiam,
Marek Prokop
2.10.1 Running the InstallShield Silent Utility
Follow these steps to run the InstallShield Silent utility:
1 ¨ Create a Response file. You can produce this file either automatically
(recommended method) by using the InstallShield Response (-r) command-line
parameter or manually by editing a setup.iss file. For more information on
automatically creating a response file, see "Creating the Response File
Automatically." For more information on manually creating a response file, see
"Creating the Response File Manually."
2 ¨ Play back the Silent Installation using the Silent (-s) command-line
parameter. The InstallShield runs on its own without your intervention:
drive:\setup.exe -s -f1C:\<path-to-file>\setup.iss
[-f2C:\<path-to-file>\setup.log]
In the above sample, path-to-file indicates the location of the setup file. The
default location of the setup.iss file is the directory where you placed the
Progress setup.exe. If you have moved this file to a different directory, you
must specify the path to that directory here.
The setup.log file is by default created in the same directory as the setup.iss
file. You can use the optional -s -f2 command line parameter to specify a
different location for the setup.log file.
NOTE: You must launch the InstallShield Silent installation utility by using
the setup.exe -s -f1 command-line parameters.
Creating the Response File Automatically
InstallShield creates a response file for you by recording all your
installation choices in the setup.iss file and places the file in the Windows
directory. Use this syntax to initiate an InstallShield response file:
drive:\setup.exe -r -f1C:\<windows directory>\setup.iss
Creating the Response File Manually
You can create and edit a response file (setup.iss), which is similar to an
.ini file. Note that this file requires you to add the necessary sections in a
predefined order.
Follow these steps to create a response file manually:
1 ¨ Create a new text file named setup.iss using any text editor.
2 ¨ Enter InstallShield response file (setup.iss) required sections in the
following order, noting that Section names are contained in square brackets,
for example, [InstallShield Silent]:
a) Silent Header Section [InstallShield Silent]
b) Dialog Sequence Section [DlgOrder]
c) Application Header Section [Application]
d) Dialog Data Sections, for example [Welcome Dialog-0]
3 ¨ Edit the necessary data within each section name. Data entries consist of
name=value pairs, such as Dlg0=Welcome-0.
4 ¨ Save and close the setup.iss file and place the file in the Windows
directory.
jsapinski@amadeus.net wrote:
> Witam,
>
> dziekuje za odpowiedz. Przegladnalem Installation and Configuration Guide.
> Niestety nie znalazlem tam informacji o tym z jakim paramatrem nalezy
> uruchomic instalacjie, aby zostal utworzony plik, ktory pozniej mozna
> wykorzystac do instalacji typu batch . Moze kto sie orientuje co to za
> parametr.
>
> Podrawiam,
>
> Jacek Sapinski
>
> From: "Marek Prokop" <mprokop@progress.com>@zeto.bydgoszcz.pl on
> 08/07/2002 15:11 ZE2
>
> Please respond to progress@zeto.bydgoszcz.pl
>
> Sent by: owner-progress@zeto.bydgoszcz.pl
>
>
> To: progress@zeto.bydgoszcz.pl
>
>
> cc:
>
>
>
>
>
>
> Subje Re: Progress batch installation
> ct:
>
>
> Jedyne, co moge poradzic w tym temacie, to nie robic pliku recznie (tj.
> edytorem, a tak sadze z Pana listu, ze Pan zrobil),
> bo plik podany w installation notes jest tylko przykladem
> (historycznym z momentu pisania dokumentacji) i moze nie byc w pelni zgodny
> z
> aktualnym formatem tego pliku.
>
> Plik taki powstanie sam jesli wykona sie zwykla (interaktywana) instalacje
> (z
> odpowiednim parametrem opisanym w installation notes).
> Instalacja powinna byc wzorcowa i fizycznie przeprowadzona do konca, z
> podanieniem wszystkich parametrow, ktore potem chce sie odtworzyc podczas
> instalacji silent (w trybie batch).
> Edycja tak powstalego pliku - poza drobnymi szczegolami typu zmiana litery
> dysku - w wiekszosci przypadkow prowadzi do niepowodzenia instalacji
> silent.
>
> Pozdrawiam,
> Marek Prokop
>
> jsapinski@amadeus.net wrote:
>
> > Witam,
> >
> > usiluje zainstalowac Progress 91c w trybie batch (silent instalation). W
> > oparciu o Installation Guide stworzylem plik .ini. NIestety kazda proba
> > instalacji konczy sie niepomyslnie. Jedyny komunikat jaki dostaje to
> >
> > PROGRESS INSTALL UTILITY LOG <VERSION 9.1C> (Thu Jun 27 14:21:01 2002)
> > Could not find the company name entry
> >
> > Nadmienie, ze parametr name zostal zdefiniowany.
> > Ponize j zamiesczam moj plik ini.
> > Moze ktos ma doswiadczenia w tej dziedzinie. Bede wdzieczny za wsazowki.
> >
> > [Configuration Count]
> > NumberofConfigurations=3
> >
> > [ProductConfiguration 1]
> > name="Amadeus"
> > serial=XXXXXXXXXXXXXXX
> > control=XXXXX XXXXX XXXXX
> > version=9.1C
> > prodname=4GL Development
> >
> > [ProductConfiguration 2]
> > name=Amadeus
> > prodname=Enterprise DB
> > serial=XXXXXXXXXXXXXXX
> > control=XXXXX XXXXX XXXXX
> > version=9.1C
> >
> > [ProductConfiguration 3]
> > name=Amadeus
> > prodname=Progress AppServer
> > serial=XXXXXXXXXXXXXXX
> > control=XXXXX XXXXX XXXXX
> > version=9.1C
> >
> > [Language Choice]
> > lang=English - American
> >
> > [Language Default]
> > _szDefaultLanguage=English - American
> >
> > [Internatioal Settings]
> > cpinternal=ISO8859-1
> > cpcollation=Basic
> > cpcase=Basic
> > dateformat=dmy
> > numsep=46
> > numdec=44
> >
> > [Server Engine]
> > type=BOTH
> >
> > [Type and Destination]
> > type=TYPICAL
> > path=/aceeu/dlc91c17
> > workpath=/tmp
> >
> > Pozdrawiam,
> >
> > Jacek Sapinski
> >
> > Amadeus Data Processing
> > Berghamer Str. 6
> > 85435 Erding, Germany
> > tel. +49 8122 43 3500
> >
> > Important: This e-mail transmission is intended only for the use of the
> > indidvidual or entity to which it is addressed. It may contain
> information
> > that is privileged, confidential, or otherwise protected from disclosure
> > under applicable law. If you are not the intended recipient (or an
> employee
> > or agent responsible for delivering the transmission to the intended
> > recipient), you are hereby notified that any dissemination, distribution,
> > copying or use of this transmission or its contents is strictly
> prohibited.
> > If you have received this transmission in error, please delete it
> > immediately from all files or folders where it appears (including any
> > archive and backup folders) and notify us immediately by replying to this
> > e-mail.
> >
> > ------
> > Strona WWW: http://pluton.pol.lublin.pl/pugpl/index.htm
> > Obsluga listy: listserv@zeto.bydgoszcz.pl
> > Archiwum listy: http://www.zeto.bydgoszcz.pl/progress/index.html
> > ------
>
> ------
> Strona WWW: http://pluton.pol.lublin.pl/pugpl/index.htm
> Obsluga listy: listserv@zeto.bydgoszcz.pl
> Archiwum listy: http://www.zeto.bydgoszcz.pl/progress/index.html
> ------
>
> ------
> Strona WWW: http://pluton.pol.lublin.pl/pugpl/index.htm
> Obsluga listy: listserv@zeto.bydgoszcz.pl
> Archiwum listy: http://www.zeto.bydgoszcz.pl/progress/index.html
> ------
------
Strona WWW: http://pluton.pol.lublin.pl/pugpl/index.htm
Obsluga listy: listserv@zeto.bydgoszcz.pl
Archiwum listy: http://www.zeto.bydgoszcz.pl/progress/index.html
------