Note: If you have a Language Supplement installed, please be aware that installing ArcView GIS 3.2 will revert your language version of ArcView GIS to English. ArcView GIS 3.2 will require a Language Supplement to maintain your current language version of ArcView GIS. The ArcView GIS 3.2 Language Supplements will be available later this year.
Note:To view the ESRI License Agreement in a translated language, see the PDF files in the License directory on the CD-ROM.
This document contains important, late-breaking information on the following topics:
1.0
Description of ArcView GIS 3.2
2.0
ArcView GIS 3.2 Documentation
3.0
New ArcView GIS Sample
4.0
Installed System Files
5.0
ArcView GIS 3.2 Font Changes
6.0
Known Issues
1.0 Description
of ArcView GIS 3.2
There are several new functionalities
in this release of ArcView GIS. What's New information is provided
in the ArcView GIS Help system as well as in the "What's New in ArcView
GIS Version 3.2" book.
Back to Contents
2.0 ArcView
GIS 3.2 Documentation
The ArcView GIS 3.2 CD-ROM
contains the following documentation which can be found in the AVDOCS folder.
All documentation is
available in Portable Document Format (PDF) and requires Acrobat Reader
for viewing. An installation of Adobe Acrobat Reader 4.0 is available on
the ArcView GIS 3.2 CD-ROM in the Acrobat4 folder. You can also obtain
the Acrobat Reader from Adobe's home
page at www.adobe.com.
3.0 New
ArcView GIS Sample
A new sample DLL, ScriptLog.dll,
has been added to ArcView GIS 3.2 to aid in Avenue application development
and debugging. This DLL adds the new avenue class, ScriptLog, which provides
the functionality to create a log file containing the name and run time
of scripts. The ScriptLog output contains the script name, the cumulative
run time (in seconds), and run time of the script (in seconds). Note that
the cumulative run time includes wait time and non-script invoked runtime.
Class Requests for ScriptLog
ScriptLog.StartLog(aFileName)
- Opens a new ScriptLog.
The name of each script that is run is written to the log file.
ScriptLog.EndLog
- Ends script logging.
The following five steps describe how to use ScriptLog.
1) Load the ScriptLog.dll in ArcView GIS using the following Avenue code.
_ScriptLogDll = System.LoadLibrary("$AVBIN\scriptlog.dll".AsFileName)2) Open a new log file using the StartLog class request.
if (_ScriptLogDll <> nil) then
MsgBox.Error("Unable to load ScriptLog.dll", "")
return nil
end
logFileName = FileName.Make("c:\temp\scriptlog.txt")3) Run or debug your Avenue application as normal.
ScriptLog.StartLog(logFileName)
4) Close the log file by using the EndLog request.
ScriptLog.EndLog5) Examine the log file contents. An example log file is below. This log file was generated by calling StartLog, choosing File/Save As from the Project GUI, and then calling EndLog. Note that the script name is followed by the log's duration and the script's run-time duration.
Project.CustomizeUpdate:
0 (0)
Project.RenameUpdate: 0
(0)
Project.DeleteUpdate: 0
(0)
Project.AddTableUpdate:
0 (0)
Project.ImportUpdate: 0
(0)
Project.HasSQL: 0 (0)
WindowMenuUpdate: 0 (0)
Doc.NewUpdate: 0 (0)
Doc.OpenUpdate: 0 (0)
Doc.ActionUpdate: 0 (0)
Project.UpdateButtons: 0
(0)
Project.CheckForEdits: 2
(0)
Project.SaveAs: 9 (7)
Project.CustomizeUpdate:
9 (0)
Project.RenameUpdate: 9
(0)
Project.DeleteUpdate: 9
(0)
Project.AddTableUpdate:
9 (0)
Project.ImportUpdate: 9
(0)
Project.HasSQL: 9 (0)
WindowMenuUpdate: 9 (0)
Doc.NewUpdate: 9 (0)
Doc.OpenUpdate: 9 (0)
Doc.ActionUpdate: 9 (0)
Project.UpdateButtons: 9
(0)
Additional Notes:
-During debugging, it is best to call StartLog and EndLog from buttons added to the ArcView GUI. See the ArcView GIS Help system for additional information on adding buttons to the ArcView GUI. A third button can also be added to the ArcView GUI to display the contents of the log file a text editor such as notepad.exe.
-The ScriptLog class can only have one log file open at a time. Calling StartLog with a log file already open will close the existing log file and open a new one.
- Do not try to unload the ScriptLog.dll. This library cannot be unloaded. If you need to unload ScriptLog.dll you must exit and restart ArcView GIS.
-If any unexplained behavior is experienced when using ScriptLog.dll, exit and restart ArcView GIS without ScriptLog.dll loaded.
4.0 Installed
System Files
Setup will install the following
files into your Windows 95/98 SYSTEM or
Windows NT/2000 SYSTEM32
directories:
comctl32.ocx | isunist.exe | msvcrt10.dll |
comdlg32.ocx | mfc42.dll | ctl3d32.dll |
dforrt.dll | mfc40.dll | msvcrt20.dll |
msvcrt40.dll | msvcrt.dll | oleaut32.dll |
mscomctl.ocx | tabctl32.ocx | msvbvm60.dll |
comcat.dll | msvcirt.dll | msvcp60.dll |
(AV Reports)
asycfilt.dll | vb5stkit.dll | p2bbnd.dll |
ccsdk32.dll | msjint35.dll | p2bdao.dll |
comcat.dll | msjter35.dll | p2ctdao.dll |
comct232.ocx | msrd2x35.dll | p2irdao.dll |
comdlg32.ocx | msrepl35.dll | p2sevt.dll |
crpaig32.dll | mstext35.dll | p2smon.dll |
crpe32.dll | msvbvm50.dll | p2sodbc.dll |
crwrap32.dll | msvcp50.dll | regsvr32.exe |
crystl32.ocx | msxbse35.dll | st5unst.exe |
expsrv.dll | odbcji32.dll | tabctl32.ocx |
implode.dll | odbcjt32.dll | tdbg5.ocx |
mscomct2.ocx | odbctl32.dll | threed32.ocx |
msrdo20.dll | olepro32.dll | vb5db.dll |
msjet35.dll | vbajet32.dll |
Setup will create a directory
named 'Crystal' under your Windows directory, and install the following
files:
crxlat32.dll | p2solap.dll | u2fdif.dll |
p2bact.dll | p2soledb.dll | u2fhtml.dll |
p2bact3.dll | p2sora7.dll | u2fodbc.dll |
p2bbde.dll | p2soutlk.dll | u2frdef.dll |
p2bbtrv.dll | p2srepl.dll | u2frec.dll |
p2bxbse.dll | p2ssql.dll | u2frtf.dll |
p2ctbtrv.dll | p2ssyb10.dll | u2fsepv.dll |
p2iract.dll | p2strack.dll | u2ftext.dll |
p2ixbse.dll | p2swblg.dll | u2fwks.dll |
p2lodbc.dll | u25200.dll | u2fwordw.dll |
p2molap.dll | u25dts.dll | u2fxls.dll |
p2sacl.dll | u25store.dll | u2l2000.dll |
p2sdb2.dll | u2dapp.dll | u2lbar.dll |
p2sfs.dll | u2ddisk.dll | u2lcom.dll |
p2sifmx.dll | u2dmapi.dll | u2ldts.dll |
p2sexsr.dll | u2dnotes.dll | u2lexch.dll |
p2smapi.dll | u2dpost.dll | u2lfinra.dll |
p2smcube.dll | u2dvim.dll | u2lsamp1.dll |
p2smsiis.dll | u2fcr.dll |
NOTE: If you proceed
with the full install of Crystal Reports, this
directory will contain additional
files.
The following file will be
installed into your PROGRAM FILES\Common
Files\Microsoft Shared\DAO
directory:
dao350.dll
dao2535.tlb
Setup will install the following
files into your Windows\fonts or
Windows NT\fonts directories:
ESRI Cartography (TrueType)
esri_1.ttf
ESRI Environmental &
Icons (TrueType) esri_2.ttf
ESRI Geometric & Symbols
(TrueType) esri_3.ttf
ESRI Oil, Gas, & Water
(TrueType)
esri_4.ttf
ESRI Transportation &
Municipal (TrueType) esri_5.ttf
ESRI Weather (TrueType)
esri_6.ttf
ESRI Geology (TrueType)
esri_7.ttf
ESRI Crime Analysis (TrueType)
esri_8.ttf
ESRI Transportation &
Civic (TrueType) esri_9.ttf
In addition to these system files, the ArcView GIS 3.2 Setup program launches Microsoft Data Access Components (MDAC) on all platforms, and Microsoft's Distribution COM for Windows 95 on 95 platforms. For a list of specific files installed with these executables, please see the Microsoft Web Page.
Additional system files installed for Hardware Key installations only:
Rainbow Sentinel Driver files
Windows 95/98
SENTINEL.VXD-73,728 bytes
The following files are installed
into \WINOWS\SYSTEM\RNBOSENT
SENTSTRT.EXE-12,000 bytes
SENTW9x.EXE-32,768 bytes
SENTW9x.DLL-40,960 bytes
SENTW9x.HLP-10,240 bytes
Windows NT
RNBOVTMP.DLL-18,432 bytes
SENTINEL.HLP-10,240 bytes
The following file is installed
into \WINNT\SYSTEM32\DRIVERS
SENTINEL.SYS-73,728 bytes
5.0 ArcView
GIS 3.2 Font Changes
- ArcView GIS 3.2 installs
updated ESRI fonts which are embeddable into presentations and files. For
example if you make a Windows Meta File export from ArcView and insert
it in Microsoft PowerPoint, within Microsoft PowerPoint you can choose
'Embed Fonts'. This ensures that others who do not have ArcView installed
can see your WMFcorrectly.
- Mapping Fonts in Adobe
Illustrator Export Format:
ArcView uses /etc/comftnam.dat
to map font names to standard font names. In the past there was only
support for the three standard font names already in the file. For
3.2, we've changed the logic so that any font name on the right side of
the comftnam.dat will be treated as a standard font name. Thus, users
can map any font to any other font. Note, font names should not include
spaces (remove them—see example below). Additionally, if users want
text to be stored as outline, they should map the font name to "None" (example
for font name "UserFont"):
UserFont None
TimesNewRoman Times
6.0
Known Issues
General Hardware Known
Issues
-It has been reported that
the following graphics card prevents ArcView GIS from running properly:
16MB Revolution IV / 128
bit AGP Super VGA graphics card CM812 on Revolution IV (Standard - HawkEye,
DirectX)
-After installing ArcView
onto Windows NT 4.0, NT 4.0 crashes if the default printer is set to a
fax modem.
Workaround: Change the default
printer to a printer.
Indexing a CAD Drawing
Theme Table
ArcView GIS creates spatial
indexes only on visible CAD layers. In theme properties, the user can check
on individual CAD layers to make them "Visible." Layers that are not checked
are therefore not visible and will not draw with the theme. If a spatial
index was created on several of the available layers, and all available
layers are subsequently made visible, actions such as zooming may result
in certain entities disappearing from the view.
To avoid this, make all
layers visible, build a spatial index and then select only those layers
you want to display.
Online Help
The Arcview GIS 3.2 Online
Help includes outdated contact information for Lizard Tech. The correct
information is:
LizardTech Inc.
The National Building
1008 Western Ave
2nd Floor
Seattle, WA 98104
Ph: 206-652-5211
Fax: 206-652-0880
Printing
-Layouts with several different
fonts or font variations process, but do not print to HP DeskJet 1600CM/PS
using enhanced PostScript.
Limited memory on the printer
may be the cause.
Add more memory to the printer.
Use fewer fonts or variations.
Print with the basic PostScript
option or the native driver.
Print through ArcPress.
-Printing large MrSID images to large page sizes causes the printer to hang, fills up the disk with temporary files, or is very slow.
-A MrSID image of a few megabytes really represents hundreds of megabytes if not gigabytes of data. This data cannot be printed in its compressed form, so it needs to be uncompressed. This takes time and resources. The following suggestions are recommended for printing MrSID images.
To avoid hanging your printer always export a layout or view using the PostScript New (EPS) option and then use ArcPress to send the exported PostScript files to your plotter.
To avoid filling up your
disk with temporary files obtain more disk space or use the AVMRSID_MAXSIZE
environment variable to limit the size of temporary images that are created.
Using the AVMRSID_MAXSIZE environment variable to limit the size of a temporary
image will result in the MrSID image having less resolution in your plot.
The AVMRSID_MAXSIZE environment variable should be set to the maximum size
of temporary image you have space for in bytes. The ideal value depends
on the size of images you are working with, available system resources,
and on the quality required for the printed imagery. We recommend you experiment
with multiple value settings to find one that is ideal. It is best to never
set the AVMRSID_MAXSIZE environment variable to greater than half of your
available disk space. You will need room for both the temporary image and
the plot file. The AVMRSID_MAXSIZE environment variable can also be used
to speed up printing of MrSID images. Setting the AVMRSID_MAXSIZE environment
variable to 0 is the same as not setting it at all.
ShapeDXF
To display information to
the screen about a shapefile using the ShapeDXF program, the program must
be run from a Command Prompt. To list information about a shapefile in
a text file, you can use the ShapeDXF shortcut found in the ArcView GIS
Program group. See the ArcView GIS online Help for more information
about the ShapeDXF program.
SQL
-Access number fields with
decimals are being padded with extra zeros in ArcView GIS.
-The "*" character does not provide access to all available tables in the database in ArcView GIS Version 3.1 and remains a known limit for 3.2.
Views and Themes
-Using extended image formats
(ImgDLL)
This information will help
you properly use the extended image formats:
1. When an image theme is
added using ImgDLL, ArcView will ask the external DLL for a zero size image.
This is necessary to set up the ImgDLL structure. This image is not used.
The DLL should pass back a small image.
2. When ImgDLL asks the external DLL for an image for a view extent that does not overlap the image, it still needs to pass back an image. A small image of the extent of the image should be passed back.
-Manage Data Sources does not support data sources with spaces in their names.
-Drawing a 1-bit TIFF (non-TIFF
6.0) with the TIFF 6.0 extension loaded causes drawing and memory problems.
Workaround: change the image's
legend to Grayscale.
-Spatial indexes for read-only data (such as shapefiles that are on a CD) are written to the current working directory. If the current working directory does not have write access, the files are written to the temporary (TEMP or /tmp) directory. The index file names are converted to an 8.3 naming convention if necessary, and have a .fbn/.fbx suffix. For example, the temporary spatial index files for a shapefile on a CD called Backgrnd.shp are called backgr1.fbn and backgr1.fbx. These files are deleted when you exit ArcView GIS.
-You may need to set the default printer to a valid printer to use the IMAGINE extension.
-If Image Analysis Version 1.0 is installed but the extension is not loaded, displaying a MrSID image may result in a "Error calling unlink for file C:\TEMP\ximg2.bil" type of error message. This occurs when you have both the MrSID Image Support extension and either the IMAGINE Image Support or TIFF 6.0 Image Support extension loaded at the same time and have installed the Image Analysis extension.
You can avoid this error by turning off the IMAGINE Image Support or TIFF 6.0 Image Support extensions or by displaying MrSID images as a "Image Analysis Data Source" via the Image Analysis extension.
This issue will be resolved
in the next version of the Image Analysis extension.
Crystal Reports for ESRI
-ArcView GIS 3.2 will install
Seagate Crystal Reports 7.0 for ESRI. If you have Crystal Reports
6.0 installed, the Crystal Reports setup will display a dialog asking if
you'd like to replace your previous version. You should respond Yes to
continue with the installation.
-To run Seagate Crystal Reports on both operating systems of a dual boot machine (i.e., on both Windows NT 4.0 and Windows 98), you must install the software under both operating systems. After you have installed Crystal Reports under one of the operating systems, during the installation on the other operating system, the Crystal Report's installation will inform you that an earlier version of Seagate Crystal Reports currently exists and asks you if you wish to replace it with the new version. You must respond yes and proceed with the installation to install Crystal Reports in both operating systems.
-If the full Crystal Reports
software is not installed, selecting Launch Crystal Reports from the Project
File menu (with the Report Writer extension loaded) results in an error
message.
Sample Extensions
There is a conflict between
the ADRG and the sample DIGEST raster image extension when both extensions
are loaded. The ADRG extension will attempt to load ASRP images due to
the same .img file extension of the image files. Therefore, the ADRG and
ASRP extensions should not be loaded at the same time.