Landmark GeoProbe GF DataServer

GeoProbe
GF DataServer 1.6.2
Release Notes

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
System Requirements
SGI ..................................... 3
SUN .................................... 3
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Enhancements and New Functionality . . . . . . . . . 7
Fixed Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Known Problems & Issues . . . . . . . . . . . . . . . . . . . . 10
Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

1.6.2 Release Notes Page 1 of 17 December 2005

Landmark GeoProbe GF DataServer

Introduction
This document contains information pertinent to the GeoProbe GF DataServer 1.6.2 release. Both
system administrators and users should read it carefully. The Known Problems & Issues section is
particularly important. Reading this section prior to using the software will assist you in attaining
maximum performance from the application.

GeoProbe GF DataServer is used to move data between GeoQuests GeoFrame and Landmarks
GeoProbe; including seismic data from both Charisma and IESX. The 1.6.2 release supports the
transfer of the following data types:

Seismic Data
Using GeoProbe GF DataServer users can migrate their Charisma and IESX seismic data
to GeoProbe volume format (.vol), and vice versa.

Surfaces
GeoProbe GF DataServer allows users to transfer GeoFrame time/depth-based grids as
GeoProbe gridview surfaces (.gvw), and to transfer GeoProbe surfaces to the GeoFrame
database.

Faults
Fault data from GeoFrame can be transferred to GeoProbes Faults subdirectory as
ezFaults (.eds), and vice versa. In addition, GeoProbe GF DataServer allows the user to
transfer GeoFrame fault data as GeoProbe Shape files (Open Inventor .iv format).

Well Data
Using GeoProbe GF DataServer, well related data including well trajectory, well markers,
well logs, and checkshots in GeoFrame can be transferred to GeoProbe well formats (.wl,
.wl.dat).

GeoProbe GF DataServer uses the units of the GeoProbe Reference Volume in making data
transfers. The Reference Volume is the first volume listed in the GF DataServer display of the
GeoProbe Volumes directory that has defined units. From this Reference Volume, it takes the Z
domain (time or depth) and the X, Y, and Z units. In the case where there is no Reference Volume
(for example, a new GeoProbe project or one where the volumes do not have defined units), then
GF DataServer uses the GeoFrame project display Unit/Coordinate System.

GeoProbe volumes transferred by GF DataServer will have unit designations set to "Unknown" if
the GeoFrame display units are used and these units are not one of the predefined GeoProbe units.
It is important to keep track of units because GeoProbe Wells/Horizons/Faults do not carry unit
designations and these units may differ from the GeoProbe volume's units.

1.6.2 Release Notes Page 2 of 17 December 2005

Landmark GeoProbe GF DataServer

System Requirements
The hardware and software requirements for GeoProbe GF DataServer are listed below.

Operating Systems

SGI

IRIX version 6.5.11 or later operating system is required to run GeoProbe GF DataServer 1.6.2.

The best way to determine if an existing system can run GeoProbe GF DataServer is to check the
SGI system model and version of IRIX (the operating system). To determine the IRIX version of
an existing system, type the following command in a shell window:

% uname -R

SUN

Solaris 8, update 7 (2/02) operating system (which includes Sun OS 5.8) is required to run
GeoProbe GF DataServer 1.6.2 on SUN workstations.

The best way to determine if an existing system can run GeoProbe GF DataServer is to check the
SUN system model and version of Solaris (the operating system). To determine the Solaris version
of an existing system, type the following command in a shell window (8 or 5.8 may be returned,
either is correct):

% cat /etc/release

Software

GeoProbe GF DataServer 1.6.2 has been qualified for data transfers from GeoQuests GeoFrame,
version 4.0.4.2.

1.6.2 Release Notes Page 3 of 17 December 2005

Landmark GeoProbe GF DataServer

Installation
Installing GeoProbe GF DataServer requires several steps to copy files to the computer, check the
hardware and set environmental variables.

Before installing, it is a good idea to determine if the workstation can run GeoProbe GF
DataServer. Check the System Requirements first.

WARNING!

Do not install this software when running as root on your UNIX workstation.
Installing GeoProbe GF DataServer as root will limit the write permissions to the
data directories. Running the program as root is also not recommended.

Accessing the CDROM

The files on a CDROM drive are normally under /CDROM on IRIX and /cdrom/cdrom0 on Solaris.
After you place the CD in the drive, wait a minute before the files appear in this directory.

Some workstations may not have a CDROM drive. Check with the system administrator on how
to remotely mount the CDROM. As a last resort, use ftp to copy all the files from the CDROM to
a temporary directory and install from that directory.

Install GeoProbe GF DataServer

To install GeoProbe GF DataServer from the Distribution CDROM, perform the following steps
in a shell window. Please note that the directory /home/magic is used only as an example.
GeoProbe GF DataServer will install and run in any directory configuration, but it does need its
own directory. Make sure Read and Execute permissions are available to all users planning to run
this program.

Using an Appserver

When GeoProbe GF DataServer is installed, it determines the operating system

from the machine being installed upon. It is therefore important to install the
Solaris executable from a SUN and the IRIX executable from an SGI. The
installation can be put on any networked drive, even on Linux. This enables the
use of an Appserver, where all the installations are on a single server.

1.6.2 Release Notes Page 4 of 17 December 2005

Landmark GeoProbe GF DataServer

1. Go to the location where you wish to install the application. The installation script will create
a GeoProbe GF DataServer Install Directory in this location. For example:

% cd /home/magic

2. For IRIX: Determine the location of the installation media (such as /CDROM/
cd_gfds162Ir64_40x for Irix) and the Install directory (such as /home/magic). Run the
following command, optionally specifying the installation media as SOURCE and Install
directory as TARGET. Please specify the SOURCE and TARGET directories using absolute
paths (starting with /). If the TARGET directory is the same as your current working directory
(pwd), you may omit TARGET=/home/magic. If the path of the makefile (gpinst.mk) is the
same as the installation media, you may omit SOURCE=/CDROM/cd_gfds162Ir64_40x.

% /bin/make -f /CDROM/cd_gfds162Ir64_4042/gpinst.mk dataserver

[SOURCE=/CDROM/cd_gfds162Ir64] [TARGET=/home/magic]

Warning - SGI only

Be sure that all GF DataServer servers from previous versions are not running, as
this may cause the first set of wells transferred with the new server to have
Infinity in the well path name. See Known Problems - Wells.

3. For Solaris: Determine the location of the installation media (such as /cdrom/cdrom0/
gfds162Sn64_40x for Sun) and the Install directory (such as /home/magic). Run the following
command, specifying the installation media as SOURCE and optionally specifying the Install
directory as TARGET. Please specify the SOURCE and TARGET directories using absolute
paths (starting with /). If the TARGET directory is the same as your current working directory
(pwd), you may omit TARGET=/home/magic.

% /usr/ccs/bin/make -f /cdrom/cdrom0/cd_gfds162Sn64_4042/
gpinst.mk dataserver SOURCE=/cdrom/cdrom0/cd_gfds162Sn64
[TARGET=/home/magic]

Note

The specific location of the make file may be different on a machine to machine
basis. Check with your IT Administrator for the correct location.

1.6.2 Release Notes Page 5 of 17 December 2005

Landmark GeoProbe GF DataServer

Configuring the Environmental Variables

To set the environment variables needed to run GF DataServer, you must edit the following script
to set the LICSRV_LICENSE_FILE, GF_PATH, TWO_TASK, ORACLE_HOME,
TNS_ADMIN, and LM_LICENSE_FILE variables:

% /home/magic/GFDataserver/<OS>/bin/setGfEnv

where <OS> stands for the operating system, either irix or sun. This needs only to be run once, after
completing installation of GF DataServer.

LICSRV_LICENSE_FILE needs to point to the GF DataServer license file.

Starting GeoProbe GF DataServer

To start GeoProbe GF DataServer, type the following:

% /home/magic/GFDataserver/<OS>/bin/gqDataserver

1.6.2 Release Notes Page 6 of 17 December 2005

Landmark GeoProbe GF DataServer

Enhancements and New Functionality

The following section gives a brief overview of the new features and functionality of the GeoProbe
GF DataServer 1.6.2 release.

General Usability

On the GeoProbe project side of the GF DataServer main window, clicking MB3 will bring up
an edit menu that has a new option called Show All Extensions. When toggled on, all files
located in the GeoProbe directories will be displayed, regardless of their file extension.

Volumes

GeoFrame volumes with non-identical characteristics can now be transferred into the same
GeoProbe project. A grid comparison dialog will appear warning the user of the inconsistency,
but this is simply a warning, not a blocker to the transfer.

When transferring seismic volumes, the user is now given the option on whether or not to
display a histogram when scaling the volume. To view a histogram of the volumes values,
toggle on Show Histogram before launching the Scaling dialog. Be aware, however, that the
scaling dialog may be slow to appear, since the entire volume must be read to complete this
operation.

Data values outside of the default range of the data may now be entered in the scaling min and
max values. These larger values will be used to annotate the volume colormap when selected
in GeoProbe Volumes > Range dialog.

Wells

When transferring well data, the TD, pick, and log tables are now sortable by clicking on the
column name.

To improve efficiency when loading wells, the options of using a Time-depth table,
transferring picks, and transferring logs are now all toggled on by default. The users preferred
TD table is set by default, as are all picks and all logs.

Well markers located below the total depth value of the well in GeoFrame are no longer
transferred into GeoProbe.

Well information is now included in the well data transferred from GeoFrame into GeoProbe.
This information can be viewed using the Well Info option on the Wells Object Manager in
GeoProbe.

1.6.2 Release Notes Page 7 of 17 December 2005

Landmark GeoProbe GF DataServer

Fixed Problems
The following problems were fixed in the 1.6.2 release of the GF DataServer. Numbers in
parentheses indicate the defect id used in Landmarks tracking system.

General

When deleting selected files from the GF DataServer display using MB3 > Delete, the data files
were being deleted from not just the display. This is still the behavior, but the message has been
changed to warn the user that file will be deleted. (#709887)

The Refresh option did not work in version 1.6.1. It does work in 1.6.2 for GeoProbe
directories only. Both the GeoProbe and GeoFrame project directories are refreshed at the
end of each transfer, however. (#709717, #709733)

Volumes

GF DataServer would not transfer a volume with only one line of real data. (#711234)

When scaling input volumes, the data could always be scaled to smaller values; however, the
reverse was not true. You could not scale a volume to values higher than the original data
values. For example, if your original volume ranged from -32767 to 32767, you could rescale
this data to -25000 to 25000. You could not rescale it to -40000 to 40000. (#709822)

Changing the percentile of scaling, not clicking Enter but clicking in either the Min or Max
field, would not change the min and max values as expected. (#711354)

Transferring 16-bit volumes using 100% scaling would result in a GeoProbe volume
containing all values of -1. (#712834)

Faults

Faults were transferring into the incorrect position for locations in the southern hemisphere.
(#711468)

Faults were transferring from GeoProbe into GeoFrame in the wrong location for the
following survey types: LL_0, LR_7, UR_2, UL_5. (#712574)

Wells

When transferring wells in time which have multiple checkshots, but none selected as a
Preferred checkshot in GeoFrame, GF DataServer transferred the well using the first
checkshot in the list provided by GeoFrame. This first checkshot in the GeoFrame list

1.6.2 Release Notes Page 8 of 17 December 2005

Landmark GeoProbe GF DataServer

appears to be the oldest. This may give unexpected results. GF DataServer 1.6.2 will transfer
the well with no time-depth conversion to make the well more obviously in depth. (#711715)

Transferring wells into a GeoProbe project containing volumes of different sizes (in Z) would
cause the GF DataServer to disregard the active TD table. (#713483)

When selecting a well marker for transfer before selecting a well log, an error message would
appear even though the marker and log transferred as expected. (#711356)

Well markers in GeoFrame located below the Total Depth of the well were being transferred
into GeoProbe, causing a crash upon their selection. (#712671)

IESX Volumes

When exiting the GF DataServer, the xterm that appears when running IESX volume transfer
did not immediately close. (#711378)

When transferring IESX volumes with a non-zero start time, there was insufficient space on the
time axis text field to display the entire number. (#711443)

1.6.2 Release Notes Page 9 of 17 December 2005

Landmark GeoProbe GF DataServer

Known Problems & Issues

The following problems and any applicable workarounds can be found both in the IRIX and Solaris
versions of GeoProbe GF DataServer, unless otherwise noted.

General

GeoFrame data of one domain type (time or depth) cannot be transferred to a GeoProbe
project of a differing domain. (#701841, #709655)

Currently, map overlays are not available for transfer from GeoFrame to GeoProbe. For a
workaround using external processes, please contact Landmark Support. (#709944)

After making transfers using one GeoFrame project, selecting another GeoFrame project
may cause the GF DataServer to hang. (#712362)

When a user is in a GeoFrame project, a lock_dir file is created, locking other users out of
that project. Sometimes, the GF DataServer will exit without releasing the lock_dir file. To
remove any of these files that may be leftover, use the following steps: (#713091)

1. First, check the directory for a lock_dir file, and remove it:

% cd <project data directory>/CharismaProj

% rm lock_dir

2. In a GeoFrame xterm window, type:

% gf_users -v

to see if other users are using this project.

3. If no other users are using the project, type:

% da_clear -f <project name>

As of this release, GF DataServer does not support non-orthogonal surveys. If you are not sure
if your survey is non-orthogonal, complete the following steps:

1. Start GeoFrames Project Manager, log into the project of interest and start the
Application Manager.

2. Click on the Data icon to start the Data Manager.

3. Start the General Data Manager.

1.6.2 Release Notes Page 10 of 17 December 2005

Landmark GeoProbe GF DataServer

4. Select the project of interest, then select Expand by Type > Survey_3D_Area. All
surveys in the project are now displayed.

5. Select the survey of interest, then select Edit > General Attribute Editor.

6. Click Attributes, then toggle on code.

7. Click OK. For a non-orthographic survey, the code value would be

Seismic_survey_nonortho. To change the value of the code to an orthogonal survey,
simply edit the code to read Seismic_Survey or Seismic_3d_Survey.

When transferring volumes from GeoFrame to GeoProbe, GF DataServer always sets the
southwestern corner point of the volume as the origin. Similarly, while doing grid comparisons,
GF DataServer always recalculates the GeoFrame survey so that the origin is at the
southwestern corner.

For example,
D A

C B

If we have a GeoFrame survey with A as origin and X and Y increments of incX and incY,
when transferring from GeoFrame to GeoProbe, GF DataServer makes C the origin and
changes the X and Y increments to -incX and -incY.

This should not pose a problem if GF DataServer is used for all transfers, but could be an issue
if different applications are used to do transfers to the same GeoProbe project. If other
applications are used to transfer volumes from GeoFrame to GeoProbe, and then GF
DataServer is used to transfer surfaces, the transfer may fail if the volumes do not have a
southwest origin. GF DataServer will display an error message saying that the grids do not
match.

For GF DataServer to be able to see GeoFrame seismic surveys, the Source must be set to
either Charisma or IESX. This Source attribute can be found by looking in the General Data
Manager for the project, Expand by Type, and double clicking on the survey name. This
brings up a Grid Library Editor, select General Attribute Editor button, and if Source is not
displayed select Attribute button, and toggle on the Source Attribute.

When transferring an object from GeoProbe to GeoFrame and the object name already exists

1.6.2 Release Notes Page 11 of 17 December 2005

Landmark GeoProbe GF DataServer

in GeoFrame for any object, GF DataServer will not transfer the object until the user changes
the name in the transfer window.

Volumes

Volumes for Survey orientations of 5 and 7 transfer to the wrong location with incorrect values
for x and y. For a detailed workaround, see the following section called Transferring Volumes
in Surveys 5 and 7. (#712681)

The GeoProbe GF DataServer expects all the volumes in a GeoProbe project to be of the same
domain (time or depth) and same X, Y units. So when you transfer seismic from GeoFrame
into a GeoProbe project, it expects the domain of the volume to be the same as that of the
reference volume. (GFDS takes the first volume in the list of existing volumes in the GeoProbe
project as the reference volume.) If the domains are different, it wont let you transfer. If the X,
Y units of the volume being transferred are different from that of the reference volume, the data
server automatically does the unit conversion. (#710042)

When a volume is transferred from GeoProbe to GeoFrame, the amplitude values may report
to be 16- or 32-bit. However, since GeoProbe can only be 8-bit, any transferred volume will
have this dynamic range. (#710154)

GeoProbe volumes (.vol files) that have units set to Unknown in their header cannot be seen
by GeoProbe GF DataServer.

Horizons and Faults

GeoFrame horizons consisting solely of digitized lines do not transfer correctly into
GeoProbe, and may contain zero values instead of null values. These *.gvw files an be
manually edited, replacing the zero values with null values as defined in the file. (#717412)

When transferring surfaces and faults from GeoProbe to GeoFrame, the GeoFrame user
must include these objects in the Interpretation Model. In the IESX Session Manager select
Applications > Interpretation Model Manager. Select the appropriate model then click the
Select Horizons or Select Faults button. When the transferred horizon or fault appears in the
list for your model, be sure to select the Assign button. Check with your GeoFrame support
personnel if you have problem with this assignment. (#710156)

GF DataServer cannot transfer ezFaults created on oblique planes.

In GeoFrame, faults can have multiple segments on the same digitizing plane. GeoProbe GF
DataServer will output these faults and retain the multiple segments. However, GeoProbe will
only read the first segment on any plane and ignore the rest. At this time, no message is
provided to the user, either in GeoProbe GF DataServer or in GeoProbe.

Fault segments in GeoFrame may consist of several points, but can collapse to a single point

1.6.2 Release Notes Page 12 of 17 December 2005

Landmark GeoProbe GF DataServer

(voxel) when loaded into GeoProbe if all the GeoFrame points lie within a single voxel. In
GeoProbe v2.7, the fault will not be loaded and a message will appear that says "Wrong data
or duplicate points found. Cannot load this surface". In GeoProbe v3.0, segments with a single
point will be skipped and a fault surface created, if possible.

Wells

For GeoFrame projects where the Seismic Reference Datum is non-zero, well paths may
contain NaN values upon the transfer. In this instance, you must set the following
environmental variable before launching the GF DataServer to transfer the wells correctly:
(#712837)

% setenv DS_FLOAT_DATUM yes

SGI only. When transferring wells the first time after installing the GF DataServer on SGI
systems, the well path would contain the word Infinity instead of values and would transfer
into the wrong location. (#716347)

Entering Interpreter or Data Source during a well transfer doesn't work (#719734)

Well markers may not transfer into the correct positions if the deviation survey is sparse, since
the GF DataServer outputs well points only at points in this deviation survey. To avoid this
problem, it is advised to resample the deviation survey in GeoFrame prior to transferring the
well data into GeoProbe. (#712835)

IESX Volumes

You cannot create a new GeoProbe project from the IESX DataServer window as you can from
the GeoProbe GF DataServer window, under File > Add GeoProbe Project... You must create
the new GeoProbe project directory before entering the IESX DataServer. (#709727)

The IESX DataServer does not do a grid comparison before transferring volumes in either
direction. This could lead to corrupted data in the target project. (#711225)

IESX volume transfers have a character limitation on the names of seismic volumes. Currently,
a volume name can only be 16 characters long. (#710715)

1.6.2 Release Notes Page 13 of 17 December 2005

Landmark GeoProbe GF DataServer

Transferring Volumes in Surveys 5 and 7

A known issue exists in which volumes for Survey orientations of 5 and 7 transfer to the wrong
location with incorrect values for X and Y. This X, Y information can be changed using
GeoProbe's Utility Launcher. After the X, Y information is corrected, subsequent objects (wells,
horizons and faults) will transfer to the correct location. Below is a workflow designed to help
the user get all data for these surveys transferred correctly.

1. In GeoFrame, determine the survey orientation in which the seismic are loaded:

a. From the Application Manager, select Seismic -> Charisma Utilities -> Seismic Data
Management -> Survey Manager.

b. The Survey Manager window appears with list of Survey Names. Select (double click) the
survey of interest.

c. In the lower half of the window, Orientation is greyed out along with a number to the
right of itThis number is the survey orientation and if it is 5 or 7 this workflow will
apply

2. Get three corner points from the GeoFrame project, either by applying the three points
defining the survey in GeoFrame originally; or by using the following process:

a. From the Application Manager, select Seismic and display a map and the first seismic
Inline (INL) for the volume.

b. Display in the readouts INL, XLN, X and Y

c. Place the cursor at the first and last points of the seismic inline and record these four
values for each.

d. Display the first seismic crossline (XLN) and determine the four values for the first and
last points

e. You now have INL, XLN, X and Y info for four corners of the survey (you will only need
three to define the correct X,Y in GeoProbe)

3. In a new session of the GF DataServer, create a new GeoProbe project (we need to start with
an empty Volumes directory).

4. Select the desired GeoFrame project, and transfer the volume only, then exit the GF
DataServer.

5. Start GeoProbe, and select Tools > Utility Launcher.

6. Click on the Volumes tab of the Utility Launcher, and select Edit Header.

1.6.2 Release Notes Page 14 of 17 December 2005

Landmark GeoProbe GF DataServer

7. Select the newly transferred volume, and insert the three GeoFrame corner points from
above, making sure to change the name of the volume to reflect that the edits have been made.

8. Select the Merge Header into Volume green button. Your new volume has been created.

9. We need to move the original volume out of the Volumes directory, into a subdirectory, so that
the GF DataServer only sees the volume we just created. In the Volumes directory of the
GeoProbe project, type the following:

% mkdir originalvolume

% mv <original volume> originalvolume/.

Now only the edited volume with the correct X, Y information is available for the GFDS to use
as reference for other object transfers.

10. Start a new session of the GF DataServer.

11. Using the above GeoProbe project, transfer the Horizon, Faults and Wells objects from
GeoFrame to this GeoProbe project. Now you are ready to interpret in GeoProbe. These
objects and any new objects can be transferred back to GeoFrame correctly. However, any
new GeoProbe volumes will not transfer into GeoFrame correctly.

Please be aware that any volume taken from GeoFrame to GeoProbe for these 5 and 7
survey orientations will have the wrong X, Y information. We appreciate your patience and
are presently working on this issue.

1.6.2 Release Notes Page 15 of 17 December 2005

Landmark GeoProbe GF DataServer

Trouble Shooting

C-tree Server Error

When IESX DataServer is started, a process called C-Tree Server is a started by IESX (on the
same system) and this gets automatically shut down when the IESX DataServer shuts down.
But in instances where the IESX DataServer shuts down improperly the C-Tree server remains
running and could cause problems when you try to run IESX DataServer later. Symptoms for
this error are, you would see messages on your console that say "Waiting for C-Tree Server to
start up. 30 out of 180 seconds". If you run the kill_servers script, this problem should be taken
care of. If you still see the problem after running the script, then the C-Tree Server must be
running on a different system. If you know which other machine you would have used to run
the IESX DataServer, try running the kill_servers script on that machine. If this doesn't work,
then in a GeoFrame xterm, do the following:

1. % sqlplus <Project Name>/<Project password> ( the name and passwd of the

project)

2. select BULK_SERVER_ADDRESS, SUPER_SERVER_ADDRESS from project;

This should give you the name of the machine. Now you can go to that machine and run
kill_servers to shut down the C-Tree Server process. If this doesn't work, please contact your
GeoFrame System administrator.

Running on SGI machine with very little memory

GF DataServer expects that there is at least 512MB of memory available on the system. If you
are running on an SGI system with less than 512MB memory or on an SGI system which is
running lots of applications, you could encounter an "SIGSEV segmentation violation" error
during the GF DataServer start up. In that case, you need to edit the "bin/runGeoProbeServer"
script and change 512 to a smaller number ( preferably 256) and try running the GF DataServer
again. If you still see this problem, please contact Landmark support.

1.6.2 Release Notes Page 16 of 17 December 2005

Landmark GeoProbe GF DataServer

Support
Landmark/Asia Pacific Landmark/EAME Landmark/The Americas
11th Floor Menara Tan & Tan Hill Park South Building 1, Suite 200, 2101 CityWest
207 Jalan Tun Razak Springfield Drive Houston, TX 77042
50400 Kuala Lumpur Leatherhead, Surrey GU22 7NL P.O. Box 42806, Houston, TX 77242
Malaysia England U.S.A.

Tel: 011-60-3-2164-1121 Tel: 011-44 (0) 1372 868-600 Tel: 713-839-2000

Help Desk: 011-61-8-9481-4488 Help Desk: 011-44 (0) 1372-868-686 Help Desk: 713-839-2200
Email: [email protected] Email: [email protected] Email: [email protected]

Trademarks
3DFS, 3D Drill View, 3D Drill View KM, 3DView, 3D Surveillance, Active Field Surveillance, Active Reservoir Surveillance,
ADC, Advanced Data Transfer, ARIES, Asset Development Center, Asset Development Centre, Asset Performance, AssetView,
Atomic Meshing, BLITZ, BLITZPAK, CasingSeat, COMPASS, Corporate Data Archiver, Corporate Data Store, Data Manager,
DataStar, DBPlot, Decision Suite, Decisionarium, DecisionSpace, DecisionSpace AssetPlanner, DecisionSpace AssetView,
DecisionSpace Atomic Meshing, DecisionSpace Decision Management Systems(DMS), DecisionSpace PowerGrid, DecisionSpace
PowerModel, DecisionSpace PrecisionTarget, DecisionSpace Reservoir, DecisionSpace TracPlanner, DecisionSpace Well Seismic
Fusion, DepthTeam, DepthTeam Explorer, DepthTeam Express, DepthTeam Express3, DepthTeam Extreme, DepthTeam
Interpreter, Desktop Navigator, DESKTOP-PVT, DESKTOP-VIP, DEX, DFW, DIMS, Discovery, Discovery Asset, Drill-to-the-
Earth Model, Drillability Suite, Drilling Desktop, DrillModel, DSS, Dynamic Reservoir Management, Dynamic Surveillance
System, EarthCube, EDM, eLandmark, Engineers Data Model, Engineer's Desktop, Engineers Link, EOS-PAK, Executive
Assistant, ezFault, ezSurface, ezTracker, FastTrack, FieldWorks, FZAP!, GeoDataLoad, GeoGraphix (stylized), GeoGraphix
Exploration System, GeoLink, GeoProbe, GeoProbe GF DataServer, GeoProbe Integrated, GES, GESXplorer, GMAplus,
GRIDGENR, Handheld Field Operator, I2 Enterprise, iDIMS, IsoMap, Landmark, Landmark and Design, Landmark logo and
Design, Landmark Decision Center, LandScape, Lattix, LeaseMap, LMK Resources, LogEdit, LogM, LogPrep, Magic Earth,
MagicDesk, MagicStation, MagicVision, Make Great Decisions, MathPack, MIRA, Model Builder, MyLandmark, OpenBooks,
OpenExplorer, OpenJournal, OpenSGM, OpenVision, OpenWells, OpenWire, OpenWorks, OpenWorks Well File, PAL, Parallel-
VIP, PetroBank, PetroWorks, PlotView, Point Gridding Plus, Pointing Dispatcher, PostStack, PostStack ESP, PowerCalculator,
PowerExplorer, PowerHub, Power Interpretation, PowerJournal, PowerModel, PowerSection, PowerView, PRIZM, PROFILE,
ProMAGIC, ProMAX, ProMAX 2D, ProMAX 3D, ProMAX 3DPSDM, ProMAX MVA, ProMAX VSP, pSTAx, QUICKDIF,
QUIKCDP, QUIKDIG, QUIKRAY, QUIKSHOT, QUIKVSP, RAVE, RAYMAP, RTOC, Real Freedom, Real-Time Asset
Management Center, Real-Time Asset Management Centre, Real Time Knowledge Company, Real-Time Operations Center, Real
Time Production Surveillance, Real Time Surveillance, RESev, ResMap, RMS, SafeStart, SCAN, SeisCube, SeisMap, SeisModel,
SeisSpace, SeisVision, SeisWell, SeisWorks, SeisXchange, Sierra, Sierra (design), SigmaView, SimResults, SIVA, Spatializer,
SpecDecomp, StrataAmp, StrataMap, Stratamodel, StrataSim, StratWorks, StressCheck, STRUCT, Surf & Connect, SynTool,
System Start for Servers, SystemStart, SystemStart for Clients, SystemStart for Storage, T2B, TDQ, Team Workspace, TERAS,
Total Drilling Performance, TOW/cs, TOW/cs The Oilfield Workstation, TracPlanner, Trend Form Gridding, Turbo Synthetics, VIP,
VIP-COMP, VIP-CORE, VIP-DUAL, VIP-ENCORE, VIP-EXECUTIVE, VIP-Local Grid Refinement, VIP-THERM, WavX, Web
Editor, Web OpenWorks, Well Seismic Fusion, Wellbase, Wellbore Planner, Wellbore Planner Connect, WELLCAT, WELLPLAN,
WellXchange, WOW, Xsection, You're in Control. Experience the difference, ZAP!, and Z-MAP Plus are trademarks, registered
trademarks or service marks of Landmark Graphics Corporation or Magic Earth, Inc.

All other trademarks are the property of their respective owners.

1.6.2 Release Notes Page 17 of 17 December 2005