Note: There is a known bug with SGI evaluations of Builder Xcessory that is fixed in the next release. For now, if you are evaluating Builder Xcessory on SGI, please see the question: Why does my BX Evaluation on SGI always start up in Demo mode? and then proceed with step #3 below.

Full operation of a BX PRO evaluation requires the installation of two evaluation license keys: one for Builder Xcessory and one for the bundled libraries (EPak and ViewKit). You should have received a separate email with both keys. If you did not, you can request another evaluation key at . The following instructions will help you properly install the keys.

1. Start BX by typing the following at the shell prompt:
   % bx
2. BX will startup and ask you for a license key. Open up the email containing the key and copy-paste it into the text entry field. If you do not yet have your key, you can click Cancel and continue in "Demo Mode" (i.e., you cannot save any user interfaces). BX will keep asking you for the Key on every startup until you install a Key.

   Note: The evaluation key format differs between Linux and UNIX. If you are installing a Linux evaluation key, it should look like (it is a single line, ignore any line breaks):

   LICENSE BuilderXcessory (key)

   And a UNIX evaluation key should look like (again a single line, ignore any line breaks):

   FEATURE BuilderXcessory ICSBX 6.000 (Date) (#licenses) (key) "ICS Builder Xcessory" DEMO

   Where (key), (Date), and (#licenses) are replaced by values appropriate for your environment. When asked to enter the Evaluation Key, enter the whole line starting with "LICENSE" for Linux and "FEATURE" for UNIX. It is highly recommended that you copy and paste the appropriate line from the email containing the key to avoid re-typing mistakes.

   Note: The Builder Xcessory evaluation key is stored in a subdirectory of ~/.builderXcessory6. This means that every person evaluating Builder Xcessory must install this key through the dialog box mentioned above. You do not need to request additional evaluation keys. The one that you used will work for them too.

3. The EnhancementPak and ViewKit libraries included with the BX PRO eval, also require a key to run applications. You can build an application using EnhancementPak widgets or the ViewKit Library, and you can even generate code, compile it and link it. However, when you try to run your application, a Dialog Box will appear and a Key will be requested (both EnhancementPak and ViewKit are enabled by the same Key). If you don't enter a key, the application will be terminated.

   Note: If you wish to avoid entering the EnhancementPak/ViewKit evaluation license key every time your run your test application, then simply make sure that the following commands are executed in the shell (or shell script) that runs your application:

   For csh (and its variants):
   % setenv ICS_EVAL_KEY (widget libraries evaluation key)

   For sh (and its variants):
   % export ICS_EVAL_KEY=(widget libraries evaluation key)