|
VFP 愛用者社區 本討論區為 Visual Foxpro 愛用者經驗交流的地方, 請多多利用"搜尋"的功能, 先查看看有無前例可循, 如果還有不懂的再發問. 部份主題有附加檔案, 須先註冊成為社區居民才可以下載.
|
上一篇主題 :: 下一篇主題 |
發表人 |
內容 |
Ruey
註冊時間: 2003-03-12 文章: 1698 來自: tunglo
第 1 樓
|
|
回頂端 |
|
|
Ruey
註冊時間: 2003-03-12 文章: 1698 來自: tunglo
第 2 樓
|
發表於: 星期五 九月 19, 2003 1:39 am 文章主題: |
|
|
最小Client端安裝方法
最小安裝的檔案跟GDS32.DLL, INTERBASE.MSG, & MSVCRT.DLL有關
Installing GDS32.DLL
GDS32.DLL is the interface library used by client applications. If you install GDS32.DLL, be sure that you install INTERBASE.MSG as well (see Installing INTERBASE.MSG below).
Before you attempt to install GDS32.DLL you should verify that it does not already exist on the system. You should look in the following locations for GDS32.DLL:
Windows system folder
This is the %SYSTEM32% folder (see Definitions for details).
InterBase 6.x (and 4.x) installation folder
Read the registry value HKEY_LOCAL_MACHINE\SOFTWARE\Borland\InterBase\Current Version and then look in the bin folder under the folder specified by that key.
InterBase 5.x installation folder
Look at the registry value HKEY_LOCAL_MACHINE\SOFTWARE\InterBase Corp\InterBase\Current Version and then look in the bin folder under the folder specified by that key.
Path Environment
Most installation packages can search for a file in the path for you automatically.
Session Manager Environment
This is applicable for Windows NT or Windows 2000 only. This is listed in the InterBase 5.5 Embedded Installation Guide, but I'm not sure that I've ever seen GDS32.DLL in this path. You can get the folder for this from the registry value HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Environment
Borland Database Engine folder
Look at the registration value HKEY_LOCAL_MACHINE\SOFTWARE\Borland\Database Engine\DLLPATH
If you found an existing GDS32.DLL, you should check the version information. If there is no version information then GDS32.DLL is from InterBase 4.0 or 4.1. If you found an InterBase 4.0 or 4.1 installation, you should abort the installation and instruct the user to remove the previous version of InterBase before running the Installation program. Tip: Tell them where you found the existing version of GDS32.DLL so they don't have to search for it.
Most installation packages have file replacement options to allow you to check the file version information automatically before replacing a file. You can replace GDS32.DLL with a newer version, but you should never replace an existing DLL with an older version.
If you have determined that it is okay to install GDS32.DLL, you should install it in the %SYSTEM32% folder.
Be sure that you update the SharedDLLs registry key (reference count) for GDS32.DLL.
Installing INTERBASE.MSG
INTERBASE.MSG contains the text used in the InterBase client and server error messages. It is important that you install the same version of GDS32.DLL and INTERBASE.MSG on the system.
If you install GDS32.DLL, you should also install INTERBASE.MSG. If you do not install GDS32.DLL (because your version is older), you should not install INTERBASE.MSG.
If an existing version of InterBase already exists, you should install INTERBASE.MSG in that folder. To see if an existing version of InterBase exists, look at the folder specified by the following registry values HKEY_LOCAL_MACHINE\SOFTWARE\
Borland\InterBase\CurrentVersion\Root Directory
and
HKEY_LOCAL_MACHINE\SOFTWARE\
InterBase Corp\InterBase\CurrentVersion\Root Directory
If an existing version of InterBase is not found, install InterBase in the %INTERBASE% folder.
Be sure that you update the SharedDLLs registry key (reference count) for INTERBASE.MSG.
Installing MSVCRT.DLL
MSVCRT.DLL is the Microsoft C Runtime Library DLL. More than likely you already have the DLL on your system. My home PC has 7 different versions of this DLL in various directories (most of them are improperly installed since it should be installed in the Windows system folder). InterBase requires version 5.00.7303 or later of this DLL. Borland shipped this version of the DLL with InterBase 6 beta. This version of MSVCRT.DLL is quite old so it is crucial that you check the version of this DLL installed on the local machine to avoid overwriting it with an older version.
Note: If you use the Microsoft installer (which is what the Borland binary package installer uses) to install MSVCRT.DLL on Windows 2000 Server, there are bugs in MSI when run on Windows 2000. In this configuration, even though the installer checks the version information, MSVCRT.DLL will be overwritten with the older 5.00.7303 version. This causes other applications such as Microsoft SQL Server to stop working. This problem does not exist if you are not using the Microsoft installer. Because there were so many problems with MSI overwriting MSVCRT.DLL, Borland updated their installer so InterBase 6 Certified no longer attempts to install this DLL under Windows 2000.
You should install MSVCRT.DLL in the %SYSTEM32% folder. Be sure that you update the SharedDLLs registry key (reference count) for MSVCRT.DLL.
Registry entries
Once you have installed the InterBase Client, you should update the registry entries used by InterBase. The following registry entries should be created/updated:
The data value of HKEY_LOCAL_MACHINE\SOFTWARE\Borland\
InterBase\Current Version\RootDirectory should be set to the %INTERBASE% folder.
Note: If you are installing InterBase on Windows 95, Windows 98, or Windows Me, the InterBase Server Manager will not be able to start the InterBase Server unless you have a trailing backslash ("\") at the end of the path assigned to the RootDirectory registry key. Until Borland has fixed this bug, I suggest that you use a trailing backslash ("\") in the path assigned to the RootDirectory key.
The data value of HKEY_LOCAL_MACHINE\SOFTWARE\Borland\
InterBase\Current Version\Version should be set to the version of GDS32.DLL.
As an alternative to setting the keys programmatically, you can use the INSTREG.EXE program to create the registry keys for:
HKEY_LOCAL_MACHINE\SOFTWARE\Borland\
InterBase\Current Version\RootDirectory
and
HKEY_LOCAL_MACHINE\SOFTWARE\Borland\
InterBase\Current Version\Version
You can see the syntax for running instreg by running instreg from the command prompt with no parameters.
Note: instreg does not maintain the reference counts on the shared files.
Updating the TCP/IP SERVICES file
If your client application will be using TCP/IP to connect to the InterBase Server, you must verify that the SERVICES file contains the gds_db entry. The SERVICES file is called "SERVICES" (no extension). The SERVICES file is located in the Windows folder on Windows 95, Windows 98, and Windows Me. Alternatively, the SERVICES file is located in the System32\drivers\etc folder on Windows NT and Windows 2000. If the SERVICES file does not contain an entry for gds_db, then you must add the following line to it:
gds_db 3050/tcp # InterBase
WARNING: It is crucial that you add the gds_db line to the existing SERVICES file. You do not want to overwrite an existing SERVICES file with a new one containing just the gds_db entry. Doing so will likely cause other applications using the TCP/IP protocol to stop functioning.
Note: If you are installing InterBase on Windows NT or Windows 2000, a standard user does not normally have rights to modify the SERVICES file. To modify the SERVICES file, the user running the installation program must have Administrative rights.
I have been told that Firebird has been modified so that if there is not an entry found in the SERVICES file, that it will default to use port 3050. This will eliminate the need to update the SERVICES file during installation. Hopefully the InterBase team at Borland will follow and implement the same change.
This is all that is needed to install the InterBase client. See the Complete Client Installation for additional options for installation the InterBase client. _________________ #############################
快樂媽咪系列幸福宅配,喝十全雞湯~原來幸福那麼簡單!!
學會VFP使用者社區的搜尋,Code才會更有趣~
############################# |
|
回頂端 |
|
|
|
|
您 無法 在這個版面發表文章 您 無法 在這個版面回覆文章 您 無法 在這個版面編輯文章 您 無法 在這個版面刪除文章 您 無法 在這個版面進行投票 您 無法 在這個版面附加檔案 您 無法 在這個版面下載檔案
|
|