PRODUCT : Borland C++ NUMBER : 1738 VERSION : All OS : DOS, WIN DATE : January 11, 1994 PAGE : 1/8 TITLE : Installing and Running Borland C++ on a Network This document will provide information about installing Borland C++ (BC++) in a network environment. It covers all versions up to 4.0. (Note: Even though this document addresses Borland C++, this information can be used with other Borland Language products as well.) Overview ======== To start, it is important to note that Borland C++ was designed with the desktop user in mind, thus the product does not offer specialized network support. This does not mean BC++ cannot be used on a network; many people (including Borland) run BC++ successfully in a network environment. The basic premise behind running Borland C++ from a network is accessibility. Access is provided by the PATH environment variable. The PATH statement provides a gateway that local machines can use to access the network image of Borland C++. It is critical that each machine wanting to access BC++ on the network includes the network drive and directory in its path statement. For example if you installed Borland C++ to network drive I: under the directory BC, then a local machine wanting access to BC should have I:\BC\BIN in its path. General Instructions ==================== The instructions in this section give you a general idea of how to install BC++ to a network. There are several special cases that require you to add to and/or modify these instructions. Review these instructions, then read the special cases that apply to you and perform the necessary steps. 1) All versions require that you use the install program provided. Run the install program and specify a network drive for the destination drive. (Make sure you have write access to that drive.) If you are installing BC++ version 3.0 or later, be sure to review the specialized instructions for your particular version. 2) After installing, set the access rights to all files in the BC++ directory (and all files in its subdirectories) PRODUCT : Borland C++ NUMBER : 1738 VERSION : All OS : DOS, WIN DATE : January 11, 1994 PAGE : 2/8 TITLE : Installing and Running Borland C++ on a Network to read only. This will prevent anyone (without proper access) from modifying the BC++ files. In addition it will prevent configuration files from being placed in the BC\BIN directory (where most of the BC++ executables reside). By default BC++ will place most of its internal configuration files in this directory. These files change depending on the way BC++ is used. Because multiple users may be accessing BC++ at the same time, it is imperative that configuration files be placed in the users local directory. By preventing BC++ from writing to BC\BIN on the network, BC++ will write its configuration files to the current drive and directory on the users machine. Because of this, it is a good idea to make a "work" directory on the users local machine. Borland C++ should be started from this directory to ensure that the configuration files will be written to the proper location. Since each configuration file is different, the users settings can be saved in his/her own work directory. 3) After installing and setting access rights, update the path on each local machine to include the BC\BIN directory on the network drive to which BC++ was installed. For example, if the user's PATH was C:\WINDOWS;C:\DOS;D:\, update it to read C:\WINDOWS;I:\BC\BIN;C:\DOS;D:\ (This assumes BC++ was installed to network drive I:.) Specialized Instructions ======================== The instructions above gave you a general idea of how to install BC++. The instructions that follow detail changes that need to be made when installing certain versions of Borland C++. All Versions Prior to 3.0 ------------------------- No additions and/or modifications are required. Version 3.0 ----------- PRODUCT : Borland C++ NUMBER : 1738 VERSION : All OS : DOS, WIN DATE : January 11, 1994 PAGE : 3/8 TITLE : Installing and Running Borland C++ on a Network Because version 3.0 offers a Windows hosted IDE for Windows development, several support files need to be placed in the WINDOWS/SYSTEM directory. In addition, several Windows configuration files also need to be updated. Running Windows from a Network? If you are running Windows from a network, you may not have write access to the WINDOWS and WINDOWS\SYSTEM directory. Because of this, the install program cannot update the files automatically. You should contact your network system administrator to install the product for you. If you have write access to the WINDOWS and WINDOWS\SYSTEM directories, run the install program as you normally would. Make sure you specify the WINDOWS directory on the network drive rather than a possible local copy of Windows. Running BC++ from a network? Once you have installed BC++ to a network drive, you must make sure each machine is configured to run it correctly. If each machine has a local copy of Windows, you will need to place several support files on their system and modify a few configuration items. Listed below are all of the changes BC++ v3.0 makes to the Windows system. Use this information to update each machine accessing BC++ v3.0: Files added to the WINDOWS directory: tddebug.386 groups.b$$ groups.exe bc.ico win.old [orig. copy of win.ini] system.old [orig. copy of system.ini] bc.pif Files changed in the WINDOWS directory: system.ini: [386Enh] device=tddebug.386 win.ini: [windows] PRODUCT : Borland C++ NUMBER : 1738 VERSION : All OS : DOS, WIN DATE : January 11, 1994 PAGE : 4/8 TITLE : Installing and Running Borland C++ on a Network load= groups.b$$ [Extensions] b$$=groups.exe ^.b$$ Files added to the WINDOWS\SYSTEM directory: bwcc.dll Version 3.1 ----------- BC++ version 3.1 also offers a Windows hosted IDE for Windows development. Several support files also need to be placed in the WINDOWS/SYSTEM directory. In addition, several Windows configuration files also need to be updated. Running Windows from a Network? If you are running Windows from a network, you may not have write access to the WINDOWS and WINDOWS\SYSTEM directory. Because of this, the install program cannot update the files automatically. You should contact your network system administrator to install the product for you. If you have write access to the WINDOWS and WINDOWS\SYSTEM directories, run the install program as you normally would. Make sure you specify the WINDOWS directory on the network drive rather than a possible local copy of Windows. Running BC++ from a Network? Once you have installed BC++ to a network drive, you must make sure each machine is configured to run it correctly. If each machine has a local copy of Windows, you will need to place several support files on their system and modify a few configuration items. Listed below are all of the changes BC++ v3.1 makes to the Windows system. Use this information to update each machine accessing BC++ v3.1: Files added to the WINDOWS directory: tddebug.386 groups.b$$ groups.exe PRODUCT : Borland C++ NUMBER : 1738 VERSION : All OS : DOS, WIN DATE : January 11, 1994 PAGE : 5/8 TITLE : Installing and Running Borland C++ on a Network bc.ico help.ico bcw.ini tdw.ini win.old [orig. copy of win.ini] system.old [orig. copy of system.ini] bc.pif Files changed in the WINDOWS directory: system.ini: [386Enh] device=tddebug.386 win.ini: [windows] load= groups.b$$ [Extensions] b$$=groups.exe ^.b$$ Files added to the WINDOWS\SYSTEM directory: bwcc.dll Version 4.0 ----------- BC++ 4.0 provides a LAN Windows Configuration option during installation. This option must be used when you run Windows from a network or plan to install BC++ 4.0 to a network. If you run Windows from a network, this option is required because access to the WINDOWS\SYSTEM directory is usually read-only. If you plan to install BC++ 4.0 to a network, the LAN Windows Configuration option centralizes the location of these files to a location on your hard disk that can be read from and written to. The LAN Windows Configuration option places the following files normally installed to the WINDOWS\SYSTEM directory in the BC4\BIN subdirectory. BW32000C.DLL BW320007.DLL BW320009.DLL BWCC.DLL BWCC000C.DLL BWCC0007.DLL PRODUCT : Borland C++ NUMBER : 1738 VERSION : All OS : DOS, WIN DATE : January 11, 1994 PAGE : 6/8 TITLE : Installing and Running Borland C++ on a Network BWCC0009.DLL BWCC32.DLL CTL3DV2.DLL CTL3D32.DLL You will want to ask your Network Administrator to move the files listed above to the WINDOWS\SYSTEM directory to maintain standard file locations. If you are installing BC++ 4.0 to a network, you will also want to use the LAN Windows Configuration option. If all users who will be running BC++ 4.0 from the network copy the files listed above into their own WINDOWS\SYSTEM directory on their local machine, they can be removed from the BIN directory on the network. The exact changes BC++ 4.0 makes to the Windows system is listed below: (Note: These instructions assume a complete install. This includes installing Win32s.) Files added to the WINDOWS directory: help.ico dosapp.ini borhelp.ini winhelp.ini bcw.ini tdw.ini bcw40.grp win32app.grp system.old [orig. copy of system.ini] Files changed (or updated) in the WINDOWS directory: system.ini: [boot] drivers=mmsystem.dll winmm16.dll [386Enh] device=C:\WINDOWS\SYSTEM\WIN32S\W32S.386 device=C:\BC4\BIN\WINDPMI.386 device=C:\BC4\BIN\TDDEBUG.386 win.ini: [Extensions] IDE=BCW.EXE^.IDE [BCW4.0 INSTALL] Reserved1=C:\BC4 PRODUCT : Borland C++ NUMBER : 1738 VERSION : All OS : DOS, WIN DATE : January 11, 1994 PAGE : 7/8 TITLE : Installing and Running Borland C++ on a Network progman.ini: [Settings] Order= {changes will vary} [Groups] GroupX=C:\WINDOWS\BCW40.GRP {X will vary} GroupX=C:\WINDOWS\WIN32APP.GRP Files added to the WINDOWS\SYSTEM directory: bwcc.dll olecli.w31 bwcc.dll bwcc0007.dll bwcc0009.dll bwcc000c.dll bw320007.dll bw320009.dll bw32000c.dll bwcc32.dll ctl3d32.dll ctl3dv2.dll owl.ini win32s.ini [Win32s install] win32s16.dll [Win32s install] w32sys.dll [Win32s install] olecli.dll winmm16.dll Files added to the WINDOWS\SYSTEM\WIN32S directory: (Created during the installation of Win32s) version.dll advapi32.dll w32s.386 comdlg32.dll w32skrnl.dll gdi32.dll win32s.exe kernel32.dll winspool.drv lz32.dll netapi32.dll mpr.dll wsock32.dll ntdll.dll sck16thk.dll crtdll.dll winmm.dll olecli32.dll c_1252.nls olesvr32.dll c_850.nls shell32.dll c_437.nls user32.dll unicode.nls PRODUCT : Borland C++ NUMBER : 1738 VERSION : All OS : DOS, WIN DATE : January 11, 1994 PAGE : 8/8 TITLE : Installing and Running Borland C++ on a Network DISCLAIMER: You have the right to use this technical information subject to the terms of the No-Nonsense License Statement that you received with the Borland product to which this information pertains.