EarthVision 8.0 Frequently Asked Questions

Windows IPC Port Security Issue

PROBLEM: When running the new 3D Viewer on Windows the firewall may issue an error like this:

or:

″Default Block Portal of Doom Trojan horse″ blocked communication.
Local address: All local network adapters(9873).
Process name is ″C:\...\dgi\dev\ev8\bin\evviewn.exe″

This message can be different depending upon the Firewall software. The message may include references to trojans or other malware. In the case of the Windows Firewall, the user is asked whether or not to Unblock or Keep Blocking the application (evviewn or coviz). Other firewalls may prompt for a similar decision.

SOLUTION: This message occurs because the 3D Viewer uses inter-process communication tasks via TCP⁄IP. This communication is entirely internal but the Firewall software isn′t sophisticated enough to know how a port is being used.

The suggested action is to select the Keep Blocking option. This maintains security on your system but should allow the 3D Viewer to function. If the viewer does not work, please contact Dynamic Graphics Technical Support with the name of the firewall being used. If the Unblock option is selected (or similar choice), it may make the computer vulnerable to attack during the 3D Viewer session. Adding evviewn⁄coviz to the Exceptions list has the same effect. Before reconfiguring a firewall, read the Microsoft article What are the risks of allowing programs through a firewall?

MSYS Conflict

PROBLEM: If a client installs WellArchitect 2.x and THEN installs the non-MKS version of EarthVision 8, the gmake.exe will fail during horizon gridding and faces file creation. The error is:

0 [main] gmake 4032 open_stackdumpfile:
Dumping stack trace to gmake.exe.stackdump

SOLUTION: This problem occurs because the MSYS version shipped with WellArchitect 2.x is version 1.10 and the MSYS version shipped with CoViz 3+ and EarthVision 8 is version 1.11. If WellArchitect 2.x MSYS is in the path before the CoViz⁄EV version, the calculation grabs sh.exe from the 1.10 version but the gmake.exe from the 1.11 version. This causes the error. There are a couple of easy workarounds but this is the best:

Copy the folder: %EVHOME%\msys or %COVIZHOME%\msys and overwrite: %WAHOME%\msys. The 1.11 MSYS works fine with WellArchitect.
Alternatively: Re-install WellArchitect after EarthVision 8.

Running EarthVision 7.5 beside EarthVision 8.0

PROBLEM: A Windows user wants to continue using EV7.5 while they transition to EV 8.

SOLUTION: First the user should remove EV 7.5 and the old MKS Toolkit. Then the user should install EV 8.0 (along with new MKS). If the user wants to access EV 7.5, they can look on the install DVD for a folder named EV75. They should double-click on the executable in this folder and it will install EV 7.5.3. When a user accesses this version from the Start menu it opens a Windows cmd window. In this window, the user can access EarthVision 7.5. This 7.5 installation does NOT change the file associations or interfere with the EarthVision 8.0 installation.

PROBLEM: A Linux user wants to continue using EV7.5 while they transition to EV 8.

SOLUTION: Many times this will be set up by a system administrator but here are the DGI tools to do this:

To Run EV 8.0, the following should be sourced:

source $DGIHOME/ev8.login

To Remove EV 8 from the environment and run EV 75:

source $DGIHOME/remove_ev8.login
source $DGIHOME/ev7.5.login

In a typical user′s .cshrc file, one can set up an EV environment with aliases:

setenv DGIHOME /home/dgi
source $DGIHOME/ev8.login
alias ev75 'source $DGIHOME/remove_ev8.login;\
source $DGIHOME/ev7.5.login;\
setenv LD_ASSUME_KERNEL 2.4.1'
alias ev8 'source $DGIHOME/remove_ev7.5.login;\
source $DGIHOME/ev8.login;\
unsetenv LD_ASSUME_KERNEL'

The above sets up an environment that has EarthVision 8.0 as the default environment but the user can shift between an EV8 and EV75 environment using the two alias′s: ev75 and ev8

But what about the LD_ASSUME_KERNEL?—see the next question.

What happened to LD_ASSUME_KERNEL?

PROBLEM: In EarthVision 7.5, the user was required to set:

setenv LD_ASSUME_KERNEL 2.4.1

This was required to run EarthVision 7.5 on an RHEL 3 or RHEL 4 machine. (This was because EV 7.5 was built under Red Hat 7.)

SOLUTION: Setting LD_ASSUME_KERNEL is not needed to run EarthVision 8 under RHEL 3 and RHEL 4 and is prohibited when running under RHEL 5. So just to keep things proper, I put the setting and unsetting of this variable in the alias lines above.

How can I run my EV 8 files in EV 7.5?

PROBLEM: Headers have changed for 2D grids, 3D grids, cell grids, and faces files so trying to view or use these in EarthVision 7.5 is not possible. The differences in header are related to information on the ″zDatum above Mean Sea Level″ and, in State Plane models, the inclusion of ″US Feet″ as a valid unit.

SOLUTION: In order to view these in EV 7.5, they need to be converted back to EV 7.5 format. To do this use the evconvertfiles utility found on the Utilities menu (Convert EarthVision File Formats). This both removes the zDatum information and renames ″US Feet″ to ″feet″ if necessary. It does not run any calculation on the data, however, to compensate for these changes. Here are the command lines for doing these file format conversions:

2D and 3D Grids:

ev_gridedit –O –o EV75.2grd EV8.2grd (grid without US Feet)
ev_gridedit –u ft –O –o EV75.2grd EV8.2grd (grid with US Feet)

Faces Files:

ev_facesedit –O –o EV75.faces EV8.faces (grid without US Feet)
ev_facesedit –u ft –O –o EV75.faces EV8.faces (grid with US Feet)

Cell Grids:

ev_celledit –O –o EV75.c3grd EV8.c3grd (grid without US Feet)
ev_celledit –u ft –O –o EV75.c3grd EV8.c3grd (grid with US Feet)

Note: There is no conversion utility for sequence files (*.seq) or WorkFlow Manager files (*.wfp). To manually edit the sequence file, just remove any reference to a zDatum and andy and ″US Feet″ reference to ″feet.″

Why do I have problems with Hayford International 1924?

PROBLEM: The ellipsoid parameters for Hayford International 1924 were corrected in EarthVision 8. As a result, files that include the ″parameters″ (grids, faces files, cell grids) will see the OLD-INCORRECT Hayford 1924 as different than NEWCORRECTED Hayford 1924.

SOLUTION: These files must all be corrected using the following commands:

ev_gridedit -o out.2grd -e "Hayford International 1924" in.2grd
ev_facesedit -o out.faces -e "Hayford International 1924" in.faces
ev_celledit -o out.c3grd -e "Hayford International 1924" in.c3grd.

On Windows do I still need the MKS Toolkit (NuTCRACER)?

PROBLEM: The MKS Toolkit (NuTCRACKER) and an X-Server are still required to run a number of EarthVision modules:

Geostatistics
Digitizer Editor
2D Mapping (when used outside of WorkFlow Manager)
Cross Sections (when used outside of WorkFlow Manager)
Well Display Program
Geologic Structure Builder Depth Conversion (when used outside WorkFlow Manager)
Other miscellaneous programs: evtieline, evsim, evmistie, etc.

How do I get the required license ID on my machine?

SOLUTION for Windows:
Start > Run
type cmd
ipconfig /all

SOLUTION for Linux:
/sbin/ifconfig eth0
get HWaddr value).