This chapter describes the procedure for installing GemBuilder for C, the Windows client component for GemStone/S 64 Bit version 3.3.
This client installation provides shared libraries that can be used to log in from a client running on Windows to a GemStone/S 64 Bit server on a server machine, utilities such as topaz, gslist, and VSD that can be run on the Windows client, and provides the include files used to link client GCI applications on the Windows client.
The GemStone/S 64 Bit server does not run directly on the Windows platform.
The following system requirements are for the GemStone/S Server component and shared libraries.
For system requirements for the client Smalltalk Environments, and for GemBuilder for Smalltalk (GBS) supported platforms, refer to the documentation that is provided with your client smalltalk product, and to the GemBuilder for Smalltalk installation Guide.
GBS depends on the client shared libraries provided by this distribution; support for GBS client platforms is limited to platforms that are supported by the GemStone/S 64 Bit server as documented in this installation guide.
If you are using GemBuilder for Smalltalk, you should also ensure that your version of client Smalltalk – VisualWorks or VisualAge – is supported on the given OS version, and that GemBuilder for Smalltalk is supported on that version.
GemStone requires a C/C++ compiler only if you are developing C or C++ code for a GCI application. The compiler is required only for development work, not for execution.
Perform the following steps to install GemStone/S 64 Bit Windows client components.
1. As the Windows Administrator account or as an account that belongs to the Administrators group, log in to the client machine.
2. Select an installation directory, InstallDir, and make this directory the current working directory.
3. GemStone/S 64 Bit is provided as a zipped archive file with a name similar to GemStone64BitClient3.3.0-x86.Windows_NT.zip. Extract the contents of this archive into the directory location in which GemStone will be installed, InstallDir.
You may perform this extraction using unzip or another uncompress application, or using Windows Explorer.
4. Verify that InstallDir now contains a GemStone directory with a name similar to GemStone64BitClient3.3.0-x86.Windows_NT.
The following directories and files are included:
There are several other empty standard directories included.
Perform the following steps to properly configure the operating environment.
You may not need to do this if you are not running the GemStone/S 64 Bit services, such as topaz and gslist, on the Windows client. However, you may need to configure your windows path to include the directory containing the shared library files.
1. Add or update the %GEMSTONE% environment variable. This is required only if you will be executing topaz or gslist on the windows client, or linking a shared library.
b. From the Control Panel, double-click the System icon.
c. Click on the Advanced tab, then on the Environment Variables button.
d. Set the environment variable GEMSTONE to the full pathname of your new GemStone installation directory.
If this is a new installation, in the System Environment Variables list, click on the New button, and enter the full path, starting with the drive, of your new Gemstone Installation directory.
If you are updating an existing installation, select GEMSTONE in the System Environment Variables list. Click on the Edit button, and update the value with your new GemStone new installation directory
2. Add or update the %path% environment variable. This is required if your client Smalltalk library loading uses the %path% to locate the client shared libraries, as well as when running topaz, gslist, or linking a shared library.
b. From the Control Panel, double-click the System icon.
c. Click on the Advanced tab, then on the Environment Variables button.
d. In the System Environment Variables list, select the path variable, and click on the Edit button. Add the full path, starting with the drive, to the bin directory of your new Gemstone installation to the front of the path string.
If you are updating an existing installation, remove the previous GemStone directory from the path.
To log in remotely to a GemStone/S 64 Bit server, there must be a NetLDI service running on the server machine. A NetLDI is not needed and can not be run on the Windows client.
By default, the server NetLDI name is gs64ldi. In order to log in using the name of the NetLDI service, either gs64ldi or the name you select, this service name should be defined in your Windows client TCP/IP network database, and define the same port number as defined on the server.
If you do not define the NetLDI name and port on the Windows client, you can still login using the port number within your login parameters, rather than the name.
To define a NetLDI name on the Windows client:
1. Open the TCP/IP network database, which is located at:
C:\WINDOWS\system32\drivers\etc\services
2. Add an entry similar to the following :
gs64ldi 50377/tcp #GemStone 3.3
This port number must be the same as the NetLDI service you will connect to on the GemStone/S 64 Bit server machine.