V6.0 PCI Software Bug List
Updated: Tuesday, 12-Mar-96 10:57:32 EST
The following is a list of known bugs with V6.0 PCI Software.
Follow this link for
known bugs in V5.3 and V5.3.1 PCI Software.
If a problem indicates a fix is available from PCI, and your site is under
maintenance (has a paid up support contract) then you can contact PCI Support
at the email address
support@pci.on.ca
to arrange a fix to be made available on the PCI ftp site. Users not under
support may check the
FTP Fixes area
of the ftp site; however, if the bug fix has not been built for the users
system type they are out of luck.
V6.0 / V5.3 Tape I/O Package on OS/2 Warp
PCI's Tape I/O package does not work with OS/2 Warp. There is no work around
short of reverting to a pre-Warp version of OS/2, or reading tapes on another
platform. It is unclear if this will be corrected in the future.
CSR 95071415
V6.0 ADAPT/ERRDIFF/RGB2PCT on IBM AIX and AXP OSF/1
The ADAPT, ERRDIFF and RGB2PCT PACE programs produce incorrect results
on IBM AIX, and AXP OSF/1. This problem is fixed in V6.0.1.
CSR 95101313
V6.0 FLY!
FLY! will not correctly produce movie loop files. This is due to an problem
in the JPEG software being used, and should be fixed for the V6.0.1 maintenance
release.
CSR 95120414
V6.0 ImageWorks Transform (HP/UX Only)
On HP Workstations, the ImageWorks Transforms (Rotate, Scale and Flip)
produce corrupted images. There is no work around, but it is fixed in
the V6.0.1 maintenance release.
CSR 95121218
V6.0 STDIJPL
On some platforms, with some datasets the following error may occur. The
problem has been fixed in V6.0.1.
forrtl: error: floating invalid
E610:Execution terminated/aborted
CSR 95122703
V6.0 ImageWorks on Windows 3.1
On the PC when you go into the Tools/filter panel with an image loaded into
imageworks, the image previews window comes up but there is no image. Even
if you select a filter type the image data is not updated in the preview
window.
This appears to be a Mach64 video driver problem. There is no known
workaround, or fix.
CSR 96011506
V6.0 ORBITWR/ORBITRD on Windows NT/96/3.1
When you run ORBITWR/ORBITRD on a windows 31 platform with an orbit segment
in a PCIDSK file, you get the following error:
floating point not supported.
A fix is available on our FTP site, and the fix will be part of the V6.0.1
release.
CSR 96011507
V6.0 ImageWorks Transform
The Transform Panel in ImageWorks doesn't work properly for 16 bit signed
image planes. This is corrected in V6.0.1, and can be worked around by
converting image planes to 32 bit real in the Image Info panel before
applying a transform.
CSR 96011809
V6.0 MOSAIC
Cutlines specified for MOSAIC.EXE do not work when the bounds for FILI and
FILO differ. The program uses the FILI georeferencing in conjunction
with a cutline, when it should use the FILO georeferencing.
This has been fixed and will be available in the V6.0.1 maintenance update.
CSR 96011904
V6.0 GCPWorks Map Tiedown
When collecting GCPs from a "LONG/LAT" map, in tieing down the map
GCPWorks will coredump when the Geocoded/Geographic menu option is
"Geocoded". (For a LONG/LAT map, it's not supposed to matter as
"Geocoded" and "Geographic" are the same thing.)
This may be avoided by selecting "Geographic" instead of "Geocoded"
before entering the LONG/LAT values in the tiedown text fields.
This has been fixed and will be available in the software point
release V6.0.1.
CSR 96012403
V6.0 ImageWorks Transform
Entering text in the rotate, or scale text fields can cause a crash.
The work around is to set these values using the sliders. This bug
is fixed in V6.0.1.
CSR 96012508
V6.0 ImageWorks - Image Edit
When clearing 16 bit signed image planes in the image editing panel of
ImageWorks only the top half of the image is cleared. This problem has
been corrected in V6.0.1. The cut function can be used as an alternative
method of clearing out the remaining portion of the image plane.
CSR 96020216
V6.0 Imageworks - Vector Editing
Drawing a new line with a large number (>1000) of consecutive
vertices causes Imageworks to fail. This occurs because the
undo-redo buffer grows very large in order to store the
intermediate steps of the operation, so Imageworks runs out of
memory and terminates.
The code has been modified to limit the number of intermediate
undos for an unfinished new line to ten (10).
CSR 96020617
V6.0 ImageWorks
File coordinates are not reported properly on the control panel if only
graphic planes are loaded, and not imageplanes. This problem is fixed in
V6.0.1.
CSR 96020619
V6.0 Imageworks Class Editing
On some platforms the "Select at cursor" button may cause ImageWorks to
crash. This problem is fixed in V6.0.1.
CSR 96020622
V6.0 ImageWorks MultiSpectral Aggregation
Changing the aggregate class name can cause the Aggregation panel to
core dump. To avoid this leave aggregates with default names. This bug
is fixed in V6.0.1.
CSR 96020708
V6.0 ImageWorks Subset Panel
A user may notice, while in the subset panel, that values they
type into the coordinate textfields are not recognized and accepted.
This problem does not occur when the mouse is used in the thumbnail
region to set the textfields. The problem is fixed in V6.0.1, and a
fix for some platforms is available on the ftp site.
CSR 96021209
V6.0 Imageworks Supervised Classification
The panel for performing classification to disk in ImageWorks Multispectral
will show at most 21 channels off the database. This limit has been removed
in V6.0.1.
CSR 96021327
V6.0 ImageWorks on Windows 95
On Windows 95, IPC communication between ImageWorks and Pace programs
will not work unless TCP/IP protocol is installed. If a person is on a
network, then this is normally installed. If not, then the following
steps are required.
Step 1: From the Control Panel, select the network applet.
Step 2: Select the Add button, this displays a panel.
From the panel select Adapter and select the Add button.
Step 3: Find Microsoft in the Manufacture list and select it.
This should display the Dial up driver Adapter selection.
Step 4: Select the Dial up driver from the Adapter selection.
Select Ok.
Step 5: Now select Protocal then select Add button.
Step 6: Find Microsoft in the Manufacture list and select it.
This should display the Protocols list.
Step 7: Select TCP/IP and select Ok.
Finally and OK. This restarts the machine. Things should be configured.
This problem will persist in V6.0.1.
CSR 96021510
V6.0 NUMREAD for Windows 3.1/95/NT
Program fails for input files with long lines with the following
error message:
ERR-IO-27 formatted record or format edit desriptor is too large for record size
E610 Execution terminated
As a workaround the V5.3 NUMREAD program can be used. The problem is
fixed in the V6.0.1 release.
CSR 96021601
V6.0 Xpace in Sun Cmdtool
When Xpace is run in a sun cmdtool it doesn't always put the command tool
in vt100 mode. This can result in PACE program status reports that don't
clear the screen, as well as other problems. The work around is to run
Xpace from an xterm instead of a cmdtool.
CSR 96022007
V6.0 GDB - NTF Format
There are problems when reading some NTF files with programs that use
the GDB library (such as FIMPORT, and ImageWorks). The bug appears as
an error 34 (File header read error) when attempting to read the files.
The problem is fixed in V6.0.1. There is no workaround.
CSR 96022104
V6.0 Works Programs
There is a font selection problem on some IBM AIX systems causing a
symbol/special font to be used instead of the proper latin fonts.
This causes works applications to display symbols instead of the proper
text.
As a temporary workaround, enter the following line in the
existing or new .Xdefaults file in the local directory:``*fontList: fixed''.
This problem has been fixed in V6.0.1.
CSR 96022206
V6.0 ImageWorks Filter (Sun/Sparc Solaris 2.4 - Open Window 3.4)
On Sun/Sparc running Solaris 2.4 (Open Window 3.4), when bringing up
the Filter window from the Tools menu, ImageWorks causes
the Open Window manager to terminate which in turns automatically
logout the user.
This problem has been fixed in V6.0.1. You can get a fix off our
FTP site under the pcisun/pcisol directory.
CSR 96022301
V6.0 ImageWorks for Windows 3.1
Only one copy of ImageWorks can run on a MS Windows 3.1 system. There is
no work around, though the problem does not exist on Windows 95 or Windows NT.
This should be corrected in V6.0.1.
CSR 96022308
V6.0 ImageWorks
If ImageWorks is terminated with a full resolution window open the
application may core dump. This corrected in V6.0.1. To avoid this
problem close any full resolution windows before terminating the
application.
CSR 96022312
V6.0 SMODEL, SORTHO and SRORTHO
V6.0 version does not support the METRE unit. This problem has been fixed
in V6.0.1.
CSR 96022603
V6.0 GDB Intergraph Raster
Type 28 Intergraph raster files (uncompressed RGB) are not supported. This
problem is fixed for V6.0.1. Tiled Intergraph raster files are also
unsupported, but this limitation will not be resolved in V6.0.1.
CSR 96022804
V6.0 ImageWorks
When vector layers (segments) are loaded into ImageWorks they consume
a large amount of memory, often significantly more than they require on
disk, and noticably more than the same vector layer required before V6.0.
In V6.0.1 a CompactVectors preference has been introduced to allow the user
to make a tradeoff between display speed and memory use.
CSR 96022901
V6.0 V6V5VEC Documentation
The documentation for the FLDNME parameter is missing from the
V6V5VEC documentation. The FLDNME parameter specifies the
database field name to be used to assign a value to the attribute
field of the V5 vector format. Fixed in V6.0.1.
CSR 96022903
V6.0 IVI
When IVI is used to load a 16 bit or 32 bit image channel to the display
that is of a constant value (for example all zeros) there is a floating
point error while scaling. On some systems this is fatal. Fixed for V6.0.1.
This doesn't happen for eight bit channels, or channels with more than one
pixel value.
CSR 96030104
V6.0 ImageWorks Windows 3.1/Windows 95
For a small image file, the load graphics dialog sometimes does not
display a newly created graphics segment in the load graphics dialog.
The solution is to restart ImageWorks.
CSR 96030427
V6.0 GDB - 16 bit LGSOWG CDROMs
When reading 16bit LGSOWG CDROM data with FIMPORT or ImageWorks all values
greater than 255 are truncated to 255. This problem may be avoided by
using the LINK program, and FIMPORT on the resulting PCIDSK header file when
importing 16 bit data. This problem is solved in V6.0.1.
CSR 96030619
V6.0 FLY! (Windows NT)
Rendered image does not increase in size if rendering window is enlarged.
Add the option -nobitblt to the end of the command line in the FLY!
properties.
CSR 96030713
V6.0 GDB - CCOGIF Import
The import of CCOGIF vector files can cause applications to crash, or
produce incorrect results. There is no work around, but this is fixed
in V6.0.1.
CSR 96030723
V6.0 GDB (RadarSat CDROM Data)
When reading some CDROMs in LGSOWG (CEOS) format the image has a vertical
strip of improper data. This is due to an improper computation of the
offset to the first pixel of data. The CDSAR program can be used as a
work around. Fixed in V6.0.1.
CSR 96031001