Tech Support

Software Configuration Notes

-This software ships with demo licenses good for 30-60 days.
-No license files for RemoteView Professional and Desktop version 1.9.1 and below will work with RemoteView Professional, Analyst, and Desktop Version 2.XX series.

-Depending on configuration, Flex licenses issued for the 2.23.X series may have to be re-issued for 2.4.

-All customers must request a new permanent license after the demo license period expires.

-Certain systems with multiple MAC addresses or machine that have been cloned may not work properly with the default primary Hostid generated license key. If this occurs, please notify us and we will regenerate your hostid license based on one of the alternative hostid's.

-Changing a machine configuration may cause your RemoteView license to become invalid. Please call Sensor Systems' support concerning network changes or hardware changes to determine if they will affect your RemoteView license.

-RemoteView may not be compatible with all Graphics cards, especially older cards without adequate DirectX or OpenGL support or sufficient video memory.

-RemoteView requires a 24-32 bit visual setting (OpenGL requires 32-bit).
-Recommended virtual memory settings should be set to 1.5-2 times the the size of the largest image you are intending to export from RemoteView.

-Recommended 'TEMP and 'TMP' space should at least twice the size of the largest image viewed in RemoteView.

-The NITF2.0 specification states that the maximum character height is 38 pixels and the minimum character height is 10 pixels. If the operator specifies a font size outside the NITF limits then the text will automatically be scaled in the exported image to the legal NITF range.

-RemoteView 2.4is not compatible with older versions of the NTM Module. Please contact Overwatch Systems for additional information.

-Placing a 'chipsizes.cfg' file in the '<RemoteView Install Directory>\Sensor Systems\RemoteView\siteconfig' with user/site specified chip sizes will populate the 'Fixed Size' menu in the Chip dialog. See the example file located in: '<RemoteView Install Directory>\Sensor Systems\RemoteView\chipsizes.cfg'
-Certain areas of context sensitive help may point to alternate locations. Should this occur, please use the root help menu to locate the help subject of interest.
-We recommend that you reboot your machine after installing RemoteView.

-RemoteView must be restarted when making changes to the elevation or tilepool settings in the Session Defaults for these items to take effect.

-RemoteView 2.4 was not intended to operate under Windows NT. Windows XP SP1 and above and Windows 2000 SP1 or above are the supported Operating systems.

-RemoteView catlog may extend the initial start time of RemoteView on certain systems.

-As of RemoteView version 2.4, panning and/or Roaming are now controlled by the middle mouse button/wheel-button.

-As of RemoteView version 2.4, holding the Shift key and performing a left click in the RemoteView overview window now control overview location selection.
Attention!
RemoteView 2.4 Default Mouse Functionality has changed slightly from earlier versions!

-Panning and/or Roaming are now controlled by the middle mouse button/wheel-button.

-To "jump" to a new location Press and hold the Shift key while clicking the left mouse button in the overview.

-Compatibility behavior for older two button mice is still available through "Session Defaults --> Presentation --> Two Button Mode". However some new functionality will not be available in two button mode.
Installing the Demo License:

- Install RemoteView by running 'Setup.exe'

- Start the application after RemoteView installation is completely installed.
- A RemoteView dialog box will appear prompting you to request a license if there is not
a license already installed.

- Select 'Yes' to bring up the RemoteView License Manager.

- Select the 'Install License' tab.

- There are two demo license located on the RemoteView Distribution CDROM. One license is for RemoteView Professional and the other is for RemoteView Desktop.

- Select the 'Import License' button.

- Browse to the RemoteView CDROM to locate the:
ProLic.txt for RemoteView Professional demo license.
DeskLic.txt for RemoteView Desktop demo license

- Once you have selected your license file, a 'License Terms' dialog box will appear. Read the license agreement and follow the prompts to complete the license installation.

Requesting a Permanent License for RemoteView:

- When your demo license expires, and you have purchased RemoteView or have a current maintenance agreement with Overwatch Systems, you will need to request your permanent license. Start RemoteView and select 'License' from the 'HELP' pull down menu. Then select the 'Request a License' tab. Fill out the license form (ensure you click either the node-locked or FLEXlm Floating button at the bottom of the page) and select email request and/or print request. If you do not have email capability, fax your license request form to (703) 437-0039, Attention: Customer Support. Your permanent license will be emailed or faxed to you within 2 business days. When calling Customer Support about licensing issues, please have your purchase order number available.

- We have also provided, on the distribution CD under the 'Utilities' directory, a 'hostid.exe' program to extract licensing information on machines that do not have RemoteView currently installed.
If you have not purchased RemoteView and wish to do so, please contact RemoteView Sales at 703-437-7651 or email rvsales@overwatch.com

Configuration & Integration Notes
IF YOU DO NOT READ ANYTHING ELSE, PLEASE READ THIS!
Please take a few moments to read these Configuration & Integration notes before beginning installation. This document contains important information regarding the proper configuration of your workstation and operation of RemoteView.
RemoteView UNIX 2.36 Important Notes
· This version of RemoteView is compatible with Solaris 2.6, 7, 8, 9 and IRIX 6.5.
· Before using RemoteView 2.36 you must have the latest Solaris Operating System kernel patch clusters from Sun Microsystems. Refer to http://sunsolve.sun.com/ for additional information. The Clusters should include at least the latest versions of these patches:
a. For Solaris 2.6, Patch-ID#s – 105591 & 107733
b. Solaris 2.7, Patch-ID#s 106300 & 106327
c. Solaris 2.8, Patch-ID#s 108434-03, 108435-03, & 109147-16.
· A NEW LICENSE is ONLY required for RemoteView 2.36. If you are running RemoteView Version 2.30 or below, license keys generated for RemoteView 2.31 and above should work with RemoteView 2.36. FLEX license holders: Depending on your configuration, you may be required to update your FLEX license when updating to RemoteView version 2.36.
· Be sure Open GL is installed on your system (Solaris only).
· After installation is complete, run the Monitor Setup Wizard.
· The first time you run RemoteView on any particular display, run Monitor Setup to characterize the display system (FILE- MONITOR SETUP). Then exit and restart RemoteView. This step is required to obtain optimum display performance, to establish the presence of options such as stereo support, 8 or 24-bit display modes, to enable hardware specific performance optimizations and to calibrate your monitor for image viewing.

· Shared Memory must be enabled and set to at least 64 MB. Insufficient shared memory is characterized by a "two stage" screen update when performing a rotate or zoom on an image, severely affecting display performance. If your kernel requires tuning, change the shared memory kernel parameter and reboot your workstation for the change to take affect. The documentation provided with your operating system will provide information for kernel tuning procedures. Also, see the Sun specific Notes for additional details.
· Swap Space should be at least two times the size of the largest uncompressed image used on the system. Example: A system with an image viewed in RemoteView that is 1GB should have 2 GB of swap space.
· RemoteView is capable of handling very large images (approximately 4 TB). Optimum performance is realized when large images are tiled on disk, and use Reduced Resolution Data Sets (RRDS). RemoteView can generate RRDS for large images that lack them. Performance is severely degraded on large images lacking RRDS when the image is minified (a scale < 1.0), due to the increased I/O required to load data for display. Generation of RRDS is strongly recommended for images greater than 4K X 4K pixels.
· Some images are formatted as large un-tiled images because many software applications write out TIFF format image files without using the standard TIFF 6.0 tiling extension. Such images will be characterized by relatively slow image import times and slow vertical or diagonal roam. Although many formats are not designed to efficiently handle large images and do not support tiling, TIFF 6 (with the tiling extension) and NITF 2.0 and NITF 2.1 do support tiled images. Tiling dramatically increases performance, significantly decreases memory requirements on large images, and is strongly recommended. Images that are not tiled can be imported into RemoteView and then exported as TIFF or NITF 2.0 format files to obtain the performance benefits of tiled image storage.
· Netscape is the default Help browser. A copy of Netscape is provided for your convenience with the RemoteView distribution if you do not already have Netscape installed. Netscape is required to view the online help documents. Be sure to configure your default Netscape font size.
· Stereo support requires a StereoGraphics emitter and receiver for stereo viewing. Contact your workstation vendor or StereoGraphics directly for purchasing information
· Starting with RemoteView version 2.31, Solaris 2.5 is no longer supported.
· Running multiple simultaneous copies of RemoteView using the same user home directory may cause problems with the users RemoteView defaults and is not recommended.
· RSET/RRDS files generated by RemoteView are NOT for distribution and are for internal RemoteView use only.
· Chipping Region of Interest on a template layer is not supported.
· Mensuration using the Output Function Dialog Box is not supported.
Configuration

1. SUN Solaris Specific Notes:

a. If RemoteView exits on Solaris with a message saying that it cannot open libGL.so, you will need to install OpenGL to run RemoteView.
b. Solaris 2.6/7/8/9 with Creator/Elite Family Graphics Hardware: If you experience very fast vertical roam performance but significantly slower diagonal or horizontal roam performance, your monitor setup is incorrect. Run FILE- MONITOR SETUP and select one of the Creator/Elite series options.
c. Solaris 2.6, 7, 8, and 9 with Creator Graphics Hardware: To enable stereo you must configure the frame buffer to one of the stereo settings using the 'ffbconfig' command. As root, type: "ffbconfig -res stereo". Then logoff to restart the X-server. To restore the configuration to higher resolution non-stereo mode your can type: "ffbconfig -res 1280". See your system documentation for more details.
d. Solaris 2.6, 7, 8 with Elite Graphics Hardware: To enable stereo you must configure the frame buffer to one of the stereo settings using the 'afbconfig' command. As root, type: "afbconfig -res stereo". Then logoff to restart the X-server. To restore the configuration to higher resolution non-stereo mode your can type: "afbconfig -res 1280". See your system documentation for more details.
2. SGI Specific Notes:

a. IRIX 6.5: Full screen stereo is supported on SGI platforms.
3. Reconfigure the System Kernel

a. On Solaris machines the kernel is loaded dynamically, so there is no need to rebuild the kernel. By default, the shared memory segment is enabled on the Solaris machines, but the maximum setting for shared memory segment is 1 MB. The '/etc/system' file is the default configuration file for your system. To increase the maximum size of the shared memory segment, you will have to be login as root. As root, you must edit the '/etc/system' file and re-boot the machine.
i. Change the '/etc/system' file and add the following line at the end of the file:
ii. set shmsys:shminfo_shmmax = 104857600
NOTE: This will make the maximum-shared memory segment size equal to 100 MB. You should also ensure that the shared memory facility is not excluded within this configuration file. You should look for all excluded statements that are not commented out and verify that the line: exclude: sys/shmsys is not present. If it is, then comment that line out.
iii. Then reboot the machine to use the new kernel configuration.
4. Priority Paging

a. Prior to Solaris 8 the virtual memory system made no distinction between file data and program text, leading to potentially severe performance degradation if RemoteView was ever paged out by the operating system. This can be alleviated somewhat in Solaris 2.6 or Solaris 7 by adding the following line in the /etc/system file:
i. set priority_paging=1
b. The change will not take effect until the system is rebooted. For Solaris 2.6 you must first have installed kernel patch 105181-09 or higher. Solaris 8 automatically separates file system data from programs.
5. RemoteView Installation

a. Logging on as Root and Loading CDROM

i. Secure root permissions by typing "su" in a Terminal window then entering the root password or by logging in as root.
NOTE: Root access is required on most systems to mount a CD manually, and to ensure write permissions into appropriate directories.
ii. Insert the RemoteView CD into the CDROM drive.
NOTE: 'su' is a UNIX command to temporarily assume root privileges, even if you are not logged on as root. You must know the root password on the workstation you are installing the software. If you are unfamiliar with 'su', you should login as root, install RemoteView, and then log off. As with most user applications, running RemoteView as root is not recommended due to potential problems with file permissions for subsequent non-root users. If the auto-mounter is disabled you must mount the disk manually (Device names may be different on some systems):

1. IRIX: mount -t iso9660 /dev/scsi/sc0d7l0 /cdrom % may be /CDROM on some systems

2. Solaris: mount -F hsfs -o ro /dev/sr0 /cdrom

NOTE: If enabled, Volume/Media Manager on Solaris and IRIX machines will mount the CD automatically in the /cdrom/cdrom0 and /CDROM directories, respectively, when the CD is inserted into the drive. If the Volume/Media manager is not running, you will have to mount the CD manually.
iii. In the Terminal window change directory to the appropriate mount point, for example:
iv. cd /cdrom/cdrom0 (Solaris 2.6/7/8/9, typical)
v. cd /CDROM (for IRIX, typical)

b. Starting Installation

i. Start the installation script by typing ?sh install.sh?. Then hit the Return key.
1. Take the default of (1) if you are installing RemoteView as a stand-alone or demo copy.
2. Select (2) if you are authorized and have purchased the FLEXlm license.
3. Select (3) to quit.
ii. Choose the correct operating system. The software will automatically detect the correct operating system but you should double check to be sure it is right.
1. 1.Sgi_6 if running on IRIX 6.X
2. 2.Sparc_26 if running Solaris 2.6, 7, 8, or 9
iii. Choosing the location to install the software. The default directory that RemoteView expects is /usr/rv. However, if you chose to install it elsewhere there will be some additional setup requirements to perform. After either accepting the default location or entering a new one click on the Return key.

NOTE: If you installed RemoteView in a directory other than "/usr/rv" then you must set the environment variable PXHOME to the installation directory before starting RemoteView (you may wish to set this in the $PXHOME/bin/rv startup script). Alternately, you can make a symbolic link between your new directory and /usr/rv ("ln -s /yournewpath /usr/rv").
iv. The software will then report the available disk space on the selected installation location. The size of each component will also be reported, including optional components. If acceptable click on the Return key.
v. The software will now look for Netscape, which is required to view the online help files. If the installation program is unable to locate Netscape, the installation program will ask you if you want to install it. If it finds Netscape it will default to the answer ?no? for installation. It is possible that the runtime setup during the installation process will differ from a user’s normal runtime environment, which may include Netscape. Ask your system administrator for additional runtime configuration information.
vi. Select any demo data sets you wish to install. The default is no for all optional components.

NOTE: The DENVER sample folder must be installed in the $PXHOME directory for example /usr/rv to function properly.
vii. Select the version of the Graphical Situation Display (GSD) you wish to install. Some sites require use of GSD 2.2 to maintain compatibility with other sites. Installing both allows you to change GSD configuration by simply setting an environment variable before running RemoteView.
NOTE: You can change the setup later between 2.2 and 3.01. See below.
viii. Enter the desired selection and hit the Return key.
ix. You will now be asked if you wish to install a demo license to run the software. You may use the time-limited demo license provided on the CD, or if you already have a License Key from Sensor Systems, you may enter the license information at this time. You may also enter license information any time after the software in installed using the $PXHOME/bin/addlicense.sh program.
x. If you want to install a demo license of the software accept the default ?no?. If already have a License Key, you may enter the license information at this time by selecting ?yes?. See the following section for detailed licensing information.
xi. After you have completed the licensing step, the install program will copy the software the directory you specified.
xii. Click on the Return key and take a short break while the software is copied onto your system.
c. Obtaining a License Key

NOTE: The easiest way to get a permanent License Key or an extension to a demo license is to e-mail Sensor Systems, Inc. at remoteview@sensor.com. Permanent license requests require the machine names and the hostid's for the systems you will be running RemoteView. Floating licenses are also available at the email address above. On all platforms, you may use the command $PXHOME/bin/sysid -host to determine the hostname and host ID. This is the recommended method.
i. On Sun systems, you may also use hostid to determine the Host ID.
ii. On SGI systems, you may also use sysinfo -s (which is located in ‘/sbin’) to determine the Host ID.
iii. For example, the hostid is 80d4670f and host name is sunny. It is very important when sending this information to Sensor Systems for a License Key to send the information EXACTLY as displayed on the screen (CASE is important!).
iv. On both the Sun and SGI systems, you may use the hostname command to determine the Host Name.
v. You will receive via email or fax the following License information from Sensor Systems. This information is required to install permanent keys, or to extend demo licenses.
NOTE: Under the module section in a license file, License keys will not contain the 'all' phrase, but instead will contain the "Basic" phrase. See sample below.
Licensee: Organization
Product:RemoteView_Pro
Version:2.00
Expiration Date:20361230
Maximum Users:0
Users: all
Groups: all
Modules: Basic
License Key:AAAAAAAA.77777777.0.1
6. Table 1: Permanent License Key Information
a. Installing a License Key

i. Installing a License Key During Installation

1. If you have obtained a License Key prior to installation, you can install the license key during the installation.
2. After the information is entered, press Return. The software will ask you to verify the License information.
ii. Installing a License Key After Installation

1. If you have already installed a demo key and need to update the license, you can run the program addlicense.sh program.
2. Be sure you are running as root.
3. Navigate to the installation directory of RemoteView where the file ‘addlicense.sh, is, typically:
$PXHOME/bin.
4. Make sure the environment variable for $PXHOME is set.
5. Type sh addlicense.sh and complete the information.
b. Completing Installation

i. When the installation completes successfully, you will be given important configuration requirements for the various platforms. Taking the time to review this information before running RemoteView will answer many common configuration questions.
ii. If the installation fails (due to lack of space or some other problem), you will be notified and the installation will exit.
NOTE: It is very important to exit as root before running RemoteView. Running as root can change the permissions of files that which will not allow other users to run the software properly.
7. After Installation Notes

a. Site.sh File

i. Create a "/usr/rv/bin/site.sh" file to configure any site-specific items. You may copy the example "/usr/rv/bin/site.sample" file to "/usr/rv/bin/site.sh" ("cp site.sample site.sh") and then "edit site.sh". Example lines are in this file to configure dual headed systems, redirect the temporary image pagefile, setup Applix, etc. See the Release Notes for more detail. Be sure that your site.sh file has executable permissions set ("chmod 555 site.sh").
b. Setting up GSD Version

i. GSD 3.0.2 has been withdrawn by the program office and is no longer supported.
ii. GSD 3.0.1 is the only version of GSD supported in RemoteView 2.36.
c. Starting RemoteView

i. To start RemoteView,
1. Add $PXHOME/bin to your PATH variable in your startup script and then start by simply typing "rv".
-OR-
2. Type: "/usr/rv/bin/rv"
-OR-
3. Type: "$PXHOME/bin/rv" if you installed in a directory other than "/usr/rv" and didn't make a symbolic link su:

8. Site Specific Customization

a. Dual Head Configuration

i. If it exists, the "/usr/rv/bin/site.sh" file is read by RemoteView at start-up to configure site-specific features. You typically will want to create a site.sh file to configure a dual head configuration or to redirect the location where temporary image products are stored. Note that an example file ("/usr/rv/bin/site.sample") can be copied to site.sh ("cp site.sample site.sh") and edited as required.
ii. Dual head configuration is enabled by setting the environment variable PX_NUMSCREENS to 2 in the "/usr/rv/bin/site.sh" file:
iii. setenv PX_NUMSCREENS 2
Note that such a line is already in the site.sample file, but is commented out with a leading "#" character. You may remove the "#" from the beginning of this line and save to /usr/rv/bin/site.sh, or add PX_NUMSCREENS to your login profile to activate RemoteView with dual head configuration.
b. Temporary Image Products

i. Temporary image products and image tiles are placed in a pagefile in the "/var/tmp" directory by default. Therefore it is necessary to have sufficient space in "/var/tmp" to accommodate your image sizes (potentially a gigabyte or more). If "/var/tmp" is too small for your purposes you can redirect the pagefile by setting the environment variable VEST_PAGEFILE in the "/usr/rv/bin/site.sh" file:
ii. setenv VEST_PAGEFILE /new_tmp_location/PAGEFILE.$$
where "new_tmp_location" is a file system with sufficient space for your image sizes. Note that such a line is already in the example file, but is commented out with a leading "#" character. If you copy the example file to site.sh, then simply replace "new_tmp_location" with the file system with sufficient space for your image sizes and remove the "#" character from the beginning of this line.
c. Adding Fonts to RemoteView

i. RemoteView ships with four True Type Fonts (*.ttf) Arial, Arial Monospaced, Impact MT, and Times New Roman. It is very simple to add new fonts by just following these steps.
ii. Copy the True Type Font files (.ttf) from a font CD or from the Internet into the $PXHOME/rv/fonts directory. $PXHOME is the directory that RemoteView is installed.
iii. Restart RemoteView and the fonts will automatically be added to the font menus.
d. NITF Environment Variables

i. The following environment variables may be set in site.sh, and/or in the user's login profile to customize the population of the NITF header values:
1. VEST_DEFAULTCLASSIFICATION - "Unclassified", "Confidential", "Restricted", "Secret” or "Top Secret"
2. VEST_ORIGINATORSTATION - Your station ID
3. VEST_ORININATORNAME - Your name
4. VEST_ORIGINATORPHONE - Your telephone number
e. Security Banner Configuration

i. The following configuration settings, included in the $PXHOME/bin/site.sample file, will display the CodeWord, Control and Handling and Release keys from the security metadata in the security banner. Unfortunately, due to inconsistencies between NITF 2.0, NITF 2.1 and TFRD, there is not 100% overlap between security keywords. Security Keywords that are blank or not applicable for a particular image will be ignored.
1. Space delimited security keywords, un-escaped tabs/newlines are NOT considered delimiters
PX_SECURITY_BANNER="\
SecurityCodeWord \
SecurityControlandHandling \
SecurityRelease \
SecurityDeclassifcationType \
SecurityDeclassifcationDate \
SecurityDeclassifcationExemption \
SecurityDowngrade \
SecurityDowngrade20 \
SecurityDowngradeDate \
SecurityDowngradeEvent \
SecurityClassificationText \
SecurityClassificationAuthorityType \
SecurityClassificationAuthority \
SecurityClassificationReason \
SecuritySourceDate \
SecurityControlNumber \
"
export PX_SECURITY_BANNER

2. Security Banner is configured by adding security keywords, in order, to the ‘$PXHOME/bin/site.sh’ file
e.g.
PX_SECURITY_BANNER="SecurityCodeWord \
SecurityControlandHandling \
SecurityRelease"

export PX_SECURITY_BANNER
f. Configuring Adobe's PDF Reader

i. To configure Adobe Acrobat Reader as the Netscape PDF viewer use the following Netscape preferences under Netscape: Edit->Preferences->Navigator->Applications
1. Description: Portable Document Format
Mime Type: application/pdf
Suffixes: pdf
Application: /opt/Acrobat4/bin/acroread %s

ii. NOTE: Location of acroread application will depend on the location specified by the user during installation.
g. Deleting SDE’s

i. The following configuration settings, included in the $PXHOME/bin/site.sample file will allow users to delete SDE’s from their current image using the Browse Metadata viewer.:
setenv DELETESDE_ENABLE 1

ii. Warning: this should only be used by an experienced user.
h. Customizing RemoteView Point Feature Classes

i. Point Feature Menus

1. RemoteView can be customized to provide point feature menus. The menus are automatically reconfigured at run-time based on files present in the RemoteView distribution directory. RemoteView is shipped with the following icon directories in $PXHOME/icons:
-IDEX
-AIR
-GROUND
-NAVAL

2. Two files are required for each point feature icon, a bitmap file for the User Interface, and the graphic to be displayed on the imagery itself.
ii. User Interface Art

1. The feature bitmap (for the User Interface) must be an X11 bitmap file. For consistency within the interface, all bitmaps in a directory should be the same size, the standard is 20 x 20 pixels. Bitmaps can be created using any software package that create X11 bitmaps, the standard X tool bitmap, can be executed as /usr/openwin/bin/bitmap.
iii. Feature Art

1. The feature art may be an Encapsulated Postscript File (EPSF), Tagged Image File Format (TIFF), or JPEG File Image Format (JFIF, or JPEG) file. The size of the image art is not particularly important, it will be scaled such that the smaller dimension is 128 pixels. Image dimensions should be between 128 and 512 pixels. EPSF art is not re-scaled, and will use the scaling as defined in the EPS file.
iv. Example

1. For example, if we want to create a new menu called SiteFeatures, we create a directory $PXHOME/icons/SiteFeatures. To create features called Sample-one and Sample-two, files Sample-One.xbm and Sample-Two.xbm must be created of the User Interface. File Sample-One.eps should contain EPSF, and Sample-Two.tif contains a color or grayscale image. File names must not contain spaces, slashes ‘/’, single or double quotes, or asterisks ‘*’. There is no enforced limit on the number of directories in $PXHOME/icons, and no enforced limit on the number of file pairs in each directory; however, care should be exercised so that menu lists and icon palettes are practical and aesthetically pleasing. Therefore, directory $PXHOME/icons/SiteFeatures contains:

Sample-One.xbm
Sample-One.eps
Sample-Two.xbm
Sample-Two.tif
I. Converting Unix Folders & Templates to Windows

i. Convert Menu Selection from the FILE Pull-down Menu Within RemoteView

1. Folders and templates created in RemoteView Unix can be converted to RemoteView Windows format. By loading a folder or template and selecting “Convert Folder to Windows” or “Convert Template To Windows” from the FILE pull-down menu you can save a folder or template out to RemoteView’s ‘*.tpl’ or ‘*.rvf’ formats.
2. When converting folders and templates you must edit this file: ‘$PXHOME/filters/path_remap.ps’ to let RemoteView remap the Unix paths to a Windows path. Remember, RemoteView does not store images within the folder. A RemoteView folder is more like an web page that contains links to where the images are stored.
a. Script example for running the Unix to Windows convert:
#!/bin/.sh
if [ "$1" == "" ]
then
echo "Usage: cvt_dir directory"
exit 1
fi

for i in $1/*
do
cvt2win $i $i.rvf
Integration Notes

1. Potential performance issue caused by Running RemoteView as a background process under specific site scenarios.

a. Who may be affected:
i. Integrators or site installers that launch RemoteView by calling a custom Korn shell script as a background process, or calling the RemoteView startup script directly as a background process may inadvertently cause RemoteView to execute with a lower than normal priority level. This reduced priority level can significantly degrade RemoteView performance.
ii. Sites using a Korn shell script to start RemoteView as a background process should be aware of a 'feature' of the Korn shell that automatically lowers the priority level of ALL background processes. This feature may be disabled using the Korn shell command 'set +o bgnice'. Please note that ALL Korn shell scripts used between the user action of pressing and button and starting RV must set this shell property. Although Csh (csh) and Bourne (sh) shell scripts are not affected by this behavior, sites not using Korn shell scripts are strongly urged to carefully verify that RemoteView is running with appropriate process priority at their site.
b. Symptoms:
i. This lower priority will cause RemoteView to 'stutter' or 'jitter' when roaming across an image. This behavior is typically seen when the image window is maximized and sharpening is a non-zero value.
c. Verification:
i. To verify that RemoteView is started with appropriate priority, use the 'ps' command to examine the priority and nice index of a RemoteView process started using the site standard startup method. Compare priority and nice index of RemoteView started directly from the command line, in the foreground, using the Sensor Systems documented startup instructions.
ii. You may also use the Solaris 'priocntl -d <PID>' command to examine the process priority of the RemoteView process (substituting the process of the RemoteView process <PID>). The priocntl output should not contain negative numbers. Negative numbers in the priocntl output indicate reduced process priority.
NOTE: Using a roam resampling setting of bilinear, bicubic or Lagrange may introduce jitter during roam, regardless of the process priority, due to computational and I/O limitations of the CPU and Dome display system. Diagonal roam directions are more likely to induce jitter than simple horizontal/vertical directions
2. Invalid CADRG/VQ Image Files

a. We have encountered some CARDRG NITF files that have an invalid NITF format. The Image Compression (IC) field states that the compression type is C4 (VQ compressed without a mask) however, the actual image data contains a mask, therefore the compression type should be M4 (VQ compressed with a mask). We have provided a workaround in the RV code to handle this problem and is available in the ‘$PXHOME/bin/site.sample’ file. The environment variable to utilize this workaround is:

NITF_FIX_BAD_VQ_MASK=1 RV
3. Modifying RemoteView Environment

a. To modify your user start-up environment so you may type "rv" at the command line to start RemoteView:

b. For sh or ksh users, edit .profile and add the following lines:
PATH=$PATH:$PXHOME/bin
PXHOME=/usr/rv
export PATH PXHOME

c. For csh users, edit .cshrc and add:
setenv PXHOME /usr/rv
set path = ($path $PXHOME/bin)

NOTE: If you installed RemoteView in a directory other than "/usr/rv", substitute that installation directory for "/usr/rv". You may also need to include Netscape path to view the help files. See your system administrator for additional information regarding the PATH environment variables.

REMOTEVIEW UNIX RELEASE NOTES

» Problem
Description

-Impact
Implication to general user community or a specific user community.

2.36.X New Features, Bug Fixes and Notices
------------
CHANGES
Problem
Modified install to allow Solaris10 users to install and use RemoteView 2.36.12.

-Impact:Minimal

• Problem
Generation of RRDS’s were not recognized by RemoteView until the image was reloaded.

-Impact:Minimal

• Problem
History of files last opened in RemoteView’s GUI’s not remembered.

-Impact:Minimal

• Problem
Report graphics were not drawn correctly when image was rotated other than North

-Impact:Minimal

• Problem
Apply button required for certain functions

-Impact:Minimal – Geo Jump functions were tedious to complete when dialog was constantly dismissed.

• Problem
Default Security Classification field order inconsistent with site.sample default order

-Impact:No impact to users, Admin had to reorder security field precedence

• Problem
Default config is to disallow invalid CADRG/CIB images. Environment variable enabling this
the workaround is off by default, as these are truly invalid NITF images.
Due to number of support calls about this issue, recommend changing site.sample to
detect and auto correct this problem by default. This invalid CIB and CADRG data is NIMA
production data.

-Impact:Minimal - users unable to load invalid (but common) CADRG/CIB image products unless variable
enabled.

• Problem
RAINDROP setup/configuration was overly complicated. Changed to require only ONE environment
variable to enable Raindrop support in RemoteView requires compatible Raindrop installation
supporting Raindrop API. Raindrop support is still Beta until next Raindrop release is
available for testing.

-Impact:Minor - Difficult to diagnose incorrect Raindrop configuration setup

• Problem
RADIANT MERCURY export hook interface was not documented in site.sample file
This is actually a general purpose hook to notify external clients that RV has exported an image file.

- Impact:Documentation only

• Problem
External viewer hook interface was not documented in site.sample file
This is actually a general purpose hook to notify external clients when the RV viewer changes the viewing rotation, scaling and location.

-Impact:Documentation only

o Problem
NITF SDE files did not include CHECKLENGTH information

-Impact:Documentation only

• Problem
Various NITF certification test cases failed.

-Impact:Various - test cases not normally seen in production data did not read/write properly

• Problem
Log file truncated prematurely, rather than maintaining fix size.

-Impact:Minor

• Problem
Optimal Tile pool size was host dependent. Sites sharing RV default files among hosts with different hardware resources (memory) could not configure Tile Pool individually.

-Impact:Moderate - required integrator workaround to modify defaults on a per host basis

• Problem
RV did not support display of transparent pixels in NITF files.

-Impact:CADRG and CIB images with transparent pixels obscured data 'under' these pixels.

• Problem
MSB image data did not mensurate properly

-Impact:Various, depending on user tasking (None to Critical)

• Problem
NITF Text export/import was not WYSIWYG.

-Impact:NITF CGM Text would change appearance during export/import process

• Problem
Changing GET requirements required change and addtionally functionality

-Impact:GET only

• Problem
Bounding box of some Shapefiles computed incorrectly

-Impact:Minimal - rare shapefile configuration

• Problem
DIEPS file import did not handle quoted strings properly

-Impact:Minimal - Unable to load some DIEPS annotation files

• Problem
NITF DES data was not propagated when exporting window or printing to file

-Impact:Moderate - Loss of DES data in printing operations (including print to file)

• Problem
North Arrow Appearance was not configurable. Some sites desire OLD North
Arrow appearance. Added support for site configurable North Arrows using
CGM definitions.

-Impact:Enhancement, old north arrow appearance still available

• Problem
Templates did not work well when chipping.

-Impact:Reworked chipping to be more in line with what is available in
Windows RemoteView.

• Problem
Multispectral image levels inconsistent

-Impact:RemoteView previously used one single DRA level for all bands in an MS
image. Version 236 now maintains DRA separately for each band.

• Problem
Saved Folders do not inherit original DRA settings

-Impact:Minimal

• Problem
Dashed line graphics did not print

-Impact:The dashed lines would print out as solid lines.

• Enhancement
Added GeoEllipse support. User may specify major/minor axis and azimuth of
geo ellipse in ground coordinates. User may place center using mouse, or
specify ellipse center coordinates.

-Impact:New feature

• Enhancement
Added command line documentation to standalone convert script

-Impact:Documentation

• Enhancement
Custom North Arrow
See RemoteView User Manual, 6.3.1.4 North Arrow Default
for information and loaction of addtional custom North Arrow
selections. User Manual can be found on RemoteView installation
CD.

-Impact:New feature

• Enhancement
User defaults for "Edit SPIA"

-Impact:New feature

• Enhancement
Stamping GSD graphics (but not for convert)

-Impact:New feature

• Enhancement
Optional: Delete NITF SDE tags.

-Impact
New feature

• Enhancement
NITF saving/chipping Options:
Use the source image originators information or
Copy over target information

-Impact:New feature

• Enhancement
JITC NITF Compliance Certification

-Impact
Certification

• Enhancement
Chipped products with Applied Screen Processing do not require ICA enhancement

-Impact:Minimal. Added HISTOA tag.

• Enhancement
Added ability to convert RemoteView Unix Folder to a format that RemoteView windows accepted.

-Impact:New Feature.

• Enhancement
Added ability to convert RemoteView Unix Templates to a format that RemoteView windows accepted.

-Impact:New Feature.

• Enhancement
Added Production Coefficient algorithms to the Image Calculator.

-Impact
New Feature.

• Enhancement
Graphic selection tool (Lasso) added to the Graphics Toolbox.

-Impact
New Feature.

• Enhancement
Placed the a “Clear Count Tag” button in the Point Features/Count Tag dialog.

-Impact
New Feature.

• Enhancement
Added an ellipse tool that contains a center dot to the Graphics Toolbox.

-Impact:New Feature.

• Enhancement
Allowed Unix Template & Folder conversions to output additional details to the ‘cvt2win.log file for diagnostic purposes.

-Impact:New Feature.

• Enhancement
OpenGL diagnostic messages are redirected to the console window for troubleshooting purposes.

-Impact:New Feature.
If you have not purchased RemoteView and wish to do so, please contact RemoteView Sales at 703-437-7651 or email rvsales@overwatch.com