| Subject | Re: [ib-support] Location of gds32.dll |
|---|---|
| Author | Paul Reeves |
| Post date | 2002-05-11T10:36:04Z |
On Fri, 10 May 2002 23:05:54 -0400, R. Tulloch wrote:
It should be noted, though, that instreg.exe does not currently maintain this new key - it is only placed there by the install routine. For now, please do not take the values in this key seriously. They are really no more than an indication that Firebird is installed, not InterBase.
It is anticipated that the next major release of Firebird (ie, one that undergoes extensive beta testing) will abandon all the legacy keys and exclusively use the Firebird ones. However, it was decided not to do this for v1.0.
Everyone knows that making last minute changes to something that works is a guaranteed way of breaking it. We didn't get around to sorting out the registry key mess until last December. We could have done a thorough job then, but the changes wouldn't have been tested very well. To have tested properly we would have had to delay the release for another month or two.
Paul
--
Paul Reeves
http://www.ibphoenix.com
Supporting users of Firebird and InterBase
>Hi:There has been no real change. However, the install also puts down a 'marker' for the future - under HKLM it creates a FirebirdSQL/Firebird key.
>
>IB Installation & Deployment Options paper defines where to look for
>gds32.dll based on reg entries/version.
>
>What are equivalent reg key names for Firebird?
>
It should be noted, though, that instreg.exe does not currently maintain this new key - it is only placed there by the install routine. For now, please do not take the values in this key seriously. They are really no more than an indication that Firebird is installed, not InterBase.
It is anticipated that the next major release of Firebird (ie, one that undergoes extensive beta testing) will abandon all the legacy keys and exclusively use the Firebird ones. However, it was decided not to do this for v1.0.
Everyone knows that making last minute changes to something that works is a guaranteed way of breaking it. We didn't get around to sorting out the registry key mess until last December. We could have done a thorough job then, but the changes wouldn't have been tested very well. To have tested properly we would have had to delay the release for another month or two.
Paul
--
Paul Reeves
http://www.ibphoenix.com
Supporting users of Firebird and InterBase