Subject | Re: Firebird 2.0 Super Server Scripted Install |
---|---|
Author | bartnickw |
Post date | 2007-04-05T13:53:50Z |
Answering my own question...
After browsing CVS, I found the issue. The Super Server component is
actually a subcomponent of Server, so the correct component name is
"ServerComponent\SuperServerComponent". The following command line
worked (updated to 2.0.1 since last post):
Firebird-2.0.1.12855-1-Win32.exe
/components="ServerComponent\SuperServerComponent,DevAdminComponent,ClientComponent"
-Wayne
--- In firebird-support@yahoogroups.com, "bartnickw" <bartnickw@...>
wrote:
After browsing CVS, I found the issue. The Super Server component is
actually a subcomponent of Server, so the correct component name is
"ServerComponent\SuperServerComponent". The following command line
worked (updated to 2.0.1 since last post):
Firebird-2.0.1.12855-1-Win32.exe
/components="ServerComponent\SuperServerComponent,DevAdminComponent,ClientComponent"
-Wayne
--- In firebird-support@yahoogroups.com, "bartnickw" <bartnickw@...>
wrote:
>/components="SuperServerComponent,ServerComponent,DevAdminComponent,ClientComponent"
> Hi,
>
> I'm trying to get a scripted install, based on the
> installation_scripted.txt document, to install Super Server. It
> appears that the "SuperServerComponent" component of the "components"
> command-line parameter doesn't actually work.
>
> I've tried any number of combinations, with or without spaces between
> delimiters, but it ALWAYS installs Classic. The full command I issue
> is straight from installation_scripted.txt, and follows:
>
> Firebird-2.0.0.12748-0-Win32.exe
>
>
> Any ideas?
> -Wayne
>