Have you solved the Indy 10 installation problem? Keyword *. BPI Indy installation error [reprinted Please attach my original address, thank you] -- programmer wood

This is the indy10 version I downloaded on the ccrun.
Installation method and steps in C ++ Builder6 (2006.12.17 ccrun genuine ):
1. decompress the ccrun compressed file. Uninstall Internet Direct (Indy)...
2. Copy the *. OBJ file under the directory ../lib/protocols/zlib to the ../lib/protocols directory.
3. Run fullc6.indy10. bat in the ../lib directory.
4. Copy idwinsock2.hpp in the ../lib/corrected. h file/bcb6 directory to the newly generated ../C6 directory, and overwrite the file with the same name.
5. All the. h/. OBJ/. lib/. BPL files are in the. ../C6 directory.
6. We recommend that you move the C6 directory to the installation directory of C ++ builder, so that you can use a short relative path in the path of the project options. For example
Move to D:/BCB/cb6/Borland/cbuilder6/projects.
7. In C ++ builder, set the path "project --> options --> directories/conditionals --> include path" and "library path" to add the C6 directory.
8. Open c ++ builder, component --> install packages --> Find dclindycore60.bpl and dclindyprotocols60.bpl under the C6 directory and add them to the component list.
First, declare that the old demon installation method is correct, but the installer may encounter various problems, and there is no comprehensive solution online or even now. After two days, I summarized a series of reasons and corresponding solutions:

(I usedC++ Builder6.0If not, just make changes)

 

Cause 1:

C ++ Builder6.0 has carried indy8.0 or other old versions, which must be uninstalled and must be thorough.

Solution:

Start c ++ Builder6. Click the File menu and select "close all ". Click the component menu and select "install packages ...". After the dialog box appears, in "design packages", find the original Indy design package (with Indy), select it, and click "Remove ". Remove the Indy design package from the original version.
Disable Borland C ++ Builder6. If there are other applications that use Indy Program You also need to exit.
Go to the Borland C ++ Builder6 installation directory and search for the following files:
Dclindy *. BPL; dclindy. *; dclindy *. BPL; Indy *. LIB; Indy *. BPL; Indy *. DLL; Id *. PAS; Id *. HPP; Id *. DCU;
Delete all the files found in the previous step (we strongly recommend that you delete them only to the recycle bin !).
Similarly, in the installation directory of Borland C ++ Builder6, search for ID *. OBJ separately.
Delete all the results found in the previous step except "idpas32.obj" (we strongly recommend that you delete them only to the recycle bin !).
Go to the System32 directory under the Windows Installation Directory and find the following file: Indy *. BPL; and then delete it.
Go to the Borland C ++ Builder6 installation directory, find the help directory, search for the following file: Indy. *; and then delete it.
Delete all files in source/Indy under the Borland C ++ Builder6 installation directory. Start c ++ Builder6. Click the File menu and select "close all ". Click the component menu and select "install packages ...". After the dialog box appears, in "design packages", find the original Indy design package (with Indy), select it, and click "Remove ". Remove the Indy design package from the original version.
Disable Borland C ++ Builder6. If other Indy applications are running, exit.
Go to the Borland C ++ Builder6 installation directory and search for the following files:
Dclindy *. BPL; dclindy. *; dclindy *. BPL; Indy *. LIB; Indy *. BPL; Indy *. DLL; Id *. PAS; Id *. HPP; Id *. DCU;
Delete all the files found in the previous step (we strongly recommend that you delete them only to the recycle bin !).
Similarly, in the installation directory of Borland C ++ Builder6, search for ID *. OBJ separately.
Delete all the results found in the previous step except "idpas32.obj" (we strongly recommend that you delete them only to the recycle bin !).
Go to the System32 directory under the Windows Installation Directory and find the following file: Indy *. BPL; and then delete it.
Go to the Borland C ++ Builder6 installation directory, find the help directory, search for the following file: Indy. *; and then delete it.
Delete all files in source/Indy under the Borland C ++ Builder6 installation directory.

Then follow the old demon method to check whether the operation is successful. Note that each time you follow the old demon method, you must first Delete the control that was last installed as successful.

Cause 2:

According to the old demon and the first reason above, the system prompts that the files indycore60.bpi, indysystem60.bpi, and indyprotocols60.bpi cannot be imported. Or what other files are missing;

This may be because of a problem in your c ++ Builder environment:

In the environment variables, carefully check which of the following environment variables is missing: (IN project-> options-> directories/conditionals)

Include path:

$ (BCB)/include; $ (BCB)/include/VCL; G:/Indy/C6;C:/Windows/system32// My Indy installation directory is on the G Disk

Library path:

$ (BCB)/lib/obj; $ (BCB)/LIB; G:/Indy/C6;C:/Windows/system32

If not, add them according to your installation directory and the corresponding file directory;

[Key part] Note: BCB cannot inport the above three files because these three files exist in system32 in the Windows directory. Add another environment variable: C:/Windows/system32in include path and library path. However, after the environment variable is successfully added, the installation is successful, after running, we found that these two environment variables lost the two variables we just added. This may be because BCB will access the system environment variables during compilation, you can view system variables in BCB in tools> environment variables. This indicates that this directory does not exist in your system variables.

Other reasons:

You may download the decompressed installation files specially designed for D7 or other single versions. You can download them to the third-party control of the ccrun,Www.ccrun.comSelf-Installed

[Tbwood offers for you-please pay the source address for reprinting :]

Http://blog.csdn.net/TBWood/archive/2009/07/14/4347656.aspx