Главная страница | назад

Article #17715: Network Install with Borland C++ Builder 3.0

 Question and Answer Database

FAQ2715C.txt   Network Install with Borland C++ Builder 3.0
Category   :Install Issues
Platform    :Windows NT
Product    :   C++Builder3.x

How do I do a netowrk install of Borland C++ Builder 3.0?

       C + +  B u i l d e r   3 . 0   N e t w o r k   I n s t a l l

WARNING:  C++Builder 3.0 was not intended to be used over a network.  I strongly 
          recommend that C++Builder is installed on every machine that it is to 
          be used on.  

   This document explains how to install C++Builder on a network and what needs to 
be done so that the product will work over the network.

Server Installation:

   On the server the system administrator must install C++Builder, make the Cbuilder3 
directory shared, and give all users read write access to it.  It is understood that 
this defeats many reasons why one would want a network install, but like is stated 
above C++Builder 3.0 is not intended to be installed on a network.  The reason for 
full access will become clear as the installation process continues.  If you choose 
a custom install TAKE NOTES on what was installed and not installed.  These notes 
will be very useful in the to you as the install process continues.

Client Installation:

   The Client Installation gets tricky.  I suggest reading though the steps once and 
then walking though the install.

1) Choose a drive letter for C++Builder.  For example choose M: as the C++Builder 
   drive and then stick with this drive FOR ALL MACHINES that C++Builder is going to 
   be installed on.  Map the chosen drive to the Cbuilder3 directory on the server.  
   The reason why all machines have to have the same drive letter for C++Builder is 
   due to pathing issues.  C++Builder uses a default project, that is stored on the 
   server machine, to store the default library, include, and packages paths.  If 
   the path to C++Builder is different on any machine then the path will have to be 
   reset every time a new project is started on any machine, and will cause lots of 

2) Install C++Builder from the client machine over the existing install of C++Builder 
   on the server machine.  For example if we choose M: to be the drive for C++Builder,
   when installing on the clients we would set the install path to M:\.  This will set
   up the registry on the clients and also install all the runtime packages that need 
   to be installed locally.   This is also one of the reasons why the server must give 
   all users read write access.  The install must be the exact same as the previous 
   install.  This is where if you chose a custom install the notes come in handy.

   The BDE (Boland Database Engine) must be installed locally on each client machine.

3) Once the install is finished run C++Builder and see if you can compile and run 
   just a blank form.  Chances are you will get errors.  Most of these errors are 
   due to the project path.  Check the project path by going to Project | Option in 
   the menu.  Make sure that the include path includes m:\include;m:\include\vcl, 
   where m is the drive that we choose to map to the Cbuilder3 directory.  Also make 
   sure that the library path includes m:\lib;m:\lib\obj;m:\lib\release;m:\lib\debug, 
   where m is the drive that points to the Cbuilder3 directory.

That should do it.  You should now be able to run C++Builder 3 over the network.  
Although it is not recommended, this should make it possible.  If you have further 
problems with the network installation call (408)461-9144. 

5/20/98 12:31:48 PM

Last Modified: 01-SEP-99