Subject | Re: Install problem on W2K Firebird 1.5.2.4731 while testing |
---|---|
Author | Eduardo A. Salgado |
Post date | 2005-08-22T14:46:51Z |
--- In firebird-support@yahoogroups.com, Helen Borrie <helebor@t...>
wrote:
Yes'm. Using the W2K Control panel, Add/remove Programs, remove the
installation of Firebird chosing to completely remove all files when
prompted.
Then use the Win installer for 1.5.2.4731, and install the full
installation of SuperServer or Classic. Reboot and check for
performance increases and resources being used for a day or more.
What I am looking for is the promise that we can install SS on a site
(which is our default installation) and then, if Classic may be
better (like in a multi processor environment) change to Classic. If
it turns out later that Classic is not better, then revert to SS and
live with a one processor affinity.
-Eduardo
wrote:
> Could you describe what you do when you talk about "a completeuninstall"?
Yes'm. Using the W2K Control panel, Add/remove Programs, remove the
installation of Firebird chosing to completely remove all files when
prompted.
Then use the Win installer for 1.5.2.4731, and install the full
installation of SuperServer or Classic. Reboot and check for
performance increases and resources being used for a day or more.
What I am looking for is the promise that we can install SS on a site
(which is our default installation) and then, if Classic may be
better (like in a multi processor environment) change to Classic. If
it turns out later that Classic is not better, then revert to SS and
live with a one processor affinity.
-Eduardo