
ADOBE(TM) ACROBAT(TM) READER

Release Notes for Version 1.0 for SunOS4.1.3 and Solaris 2.3


This file contains important last-minute product information,
program errors not covered in the documentation, and summaries of
known problems and limitations. It also addresses some configuration
and performance issues. The Getting Started guide and the On-line
Guide (Acrobat Reader Help) provide essential information to help
you install and configure Adobe Acrobat Reader 1.0. 

Product Information: 
	Electronic End User License Agreement
	Launching Adobe Acrobat Reader 
	Solaris 2.3 Requires Patch
	SPARCstation LX Requires Patch 
	Window Managers Tested 

Program Errors: 
	See Troubleshooting Section of Getting Started

Known Problems:
	Printing With Sun NeWSPrint
	UNIX Problems With Novell Servers
	Searching Through the Getting Started guide
	Sometimes Multiple Readers May Run At Once
	Occasional Difficulties with Certain Fonts

Product Limitations:
	Printer Memory
	Focus Problems Under OpenWindow With AutoInputFocus
	Text Selection
	Text Greeking
	No APIs with Version 1.0
	Command Line: One Bad File Can Prevent Others From Loading
	Level 1 Display PostScript Font Limitations

Installation Issues:
	Installing Icons on OpenWindows Desktop
	You Don't Have To Be Root to Install the Application
	If You Install As Root, Install Onto Local Disk Drive

Configuration and Performance Issues: 
	Performance Problems with Type 3 Fonts / TeX
	Default Page Size
	File Locking in Multiplatform Environments
	Slow Menus When Displayed from HP Workstations


==================== PRODUCT INFORMATION ========================

ELECTRONIC END USER LICENSE AGREEMENT
-------------------------------------
This version of Adobe Acrobat Reader contains an Electronic
End User License Agreement. Do not install or run the Software
unless you have read and accepted the terms of the license
agreement. You indicate that you accept the terms of the license
by entering the word "ACCEPT" in response to an installer prompt.

The license agreement is displayed when you run one of the
installers (easyinst.rdr and install.rdr). Also, a copy can be
found on the CD-ROM in:
	<cdrom-base-directory>/acroread/license.rdr
(where cdrom-base-directory is typically /cdrom under SunOS 4.x
and /cdrom/adobe under Solaris 2.x) and, once you install the
product, in <installdir>/AcroRead_1.0/LICENSE.


LAUNCHING ADOBE ACROBAT READER
------------------------------
(The following is a quick summary of information on how to launch
Adobe Acrobat Reader. For more complete information, or if you
encounter errors, consult your Getting Started guide.)

To start Acrobat Reader from the Open Windows desktop, you must
have run the olwm.deskinstall script. See your Getting Started Guide
for details. Double-click on the Acrobat Reader Program Icon
(acroread) located in the  <installdir>/AcroRead.0/bin directory
(<installdir> is /usr/adobe by default) or its link in the
launchscript directory (/usr/bin by default).

If the Acrobat Reader launch script (acroread) is on your PATH,
you can also launch Acrobat Reader by typing into a UNIX shell
window:
	% acroread

For a list of command line options:
	% acroread -help


SOLARIS 2.3 REQUIRES PATCH
--------------------------
There is an X server bug in the standard Solaris 2.3 distribution
which can cause Display PostScript (DPS) applications such as
Acrobat Reader to hang when they attempt to initialize the DPS
component of the X server. With Acrobat Reader, the hang
typically occurs when the copyright window appears at product
start-up.

The technical details around the bug: the bug occurs if DPS is
used indirectly by an application making X Window System font calls
before an application uses DPS directly. Two known problem cases:
(1) if you use the OpenWindows Properties dialog under Solaris 2.3
and choose an Adobe font for your system font, then some of your
generic utilities (xterm, cmdtool, etc.) launched at window system
startup will cause this hanging problem with Acrobat, (2) if you
use the text tool in Adobe Photoshop 2.5.

Three known workarounds: (1) install the latest Sun patch
101362-xx for Solaris 2.3, which includes the fix to the X server
(Sun says patch 101362-06 or later will fix the problem - we
verified patch 101362-08) (2) install the next version of Solaris
when it becomes available and (3) force the use of DPS/NX either
by setting environment variable DPSNXOVER to true (e.g., in
C-shell: "setenv DPSNXOVER true") or by adding
"Acroread*dpsnxOverride: True" to an appropriate X resource file
(e.g., .Xdefaults).

Contact your Sun representative if you want to order the patch.


SPARCSTATION LX REQUIRES PATCH
------------------------------
You may encounter significant performance degradation when using
SunOS 4.1.3C on the Sun Sparcstation LX. This problem has been
fixed by Sun and is available with SunOS 4.1.3U1. Contact your Sun
representative to order the new operating system.


WINDOW MANAGERS TESTED
----------------------
Adobe Acrobat Reader for SUN has only been tested with the
OpenLook and Motif window managers. If you are using a different
window manager (like twm or olvwm), Acrobat Reader is not
guaranteed to work completely or correctly.


==================  PROGRAM ERRORS =============================

If you receive a program error while running Adobe Acrobat Reader,
consult the Troubleshooting Section of your Getting Started Guide.


=================== KNOWN PROBLEMS =============================

PRINTING USING SUN NeWSPrint
----------------------------
Adobe Acrobat Reader is not compatible with SUN NeWSPrint. We have
contacted Sun and are working to create a solution.


UNIX PROBLEMS WITH NOVELL SERVERS
---------------------------------
Novell Netware servers may exhibit generic file access problems between
Mac/Windows clients and UNIX/NFS clients where a file opened by a Mac
or Windows user cannot be opened by a UNIX user or vice-versa, even if
the file is opened read-only and permissions appear to give universal
access. The problem is intermittent and has a timeout component where
you might have to wait some number of seconds after the Mac/Windows
user closes the file before you can access the file from UNIX.


SEARCHING THROUGH THE GETTING STARTED GUIDE
-------------------------------------------
There is a known problem with the Getting Started guide PDF file
that appears on the CD-ROM as getstart.pdf and as 
<installdir>/doc/GettingStarted.pdf after the product is installed:
searches fail if begun from the beginning of the document. This is
a problem with the PDF file itself. The workaround: begin the search
starting with page 5.


SOMETIMES MULTIPLE READER MAY RUN AT ONCE
-----------------------------------------
If you issue the command "acroread <file>...", the Acrobat launch
script will invoke a small front-end program to determine if 
Acrobat is already running under your login on this machine and
displaying on the same display. If all of these conditions are
true, then the launch script will pass the given file names to
the process that is already running; otherwise, the launch script
will launch a new Acrobat process.

Two versions of Acrobat may be launched when you do a Save
Workspace with Command Tools or Shell Tools active (under
OpenWindows). If you launch Acrobat from one of the saved Command
Tools or Shell Tools, you get one Acrobat process. If you open a
new Command Tool or Shell Tool and run "acroread", then another
Acrobat process may launch.

The workaround: make sure that you have defined a value for
environment variable DISPLAY within one of your startup dot files
(.profile for Bourne shell, .cshrc or .login for C shell). For
example, for the C shell, put the following line in $HOME/.cshrc:

	setenv DISPLAY :0

If you make this change and then log out of your workstation and
then log back in, the problem should go away.


OCCASIONAL DIFFICULTIES WITH CERTAIN FONTS
------------------------------------------
There is a known problem with the software with certain classes
of fonts which may occasionally prevent the application from
viewing/printing particular pages. The problem is rather obscure
and will not be encountered by most users.

If you find that you cannot view/print a particular page, try
the following:

1) Add the following line to the appropriate start-up file in your
home directory (e.g., .cshrc if you are using C-shell):

	setenv PSRESOURCEPATH <installdir>/AcroRead_1.0/fonts::

For example, if Reader was installed in the default location
of /usr/adobe/AcroRead_1.0, then the line would read:

        setenv PSRESOURCEPATH /usr/adobe/AcroRead_1.0/fonts::

2) Log out of your workstation and then log back in to make sure
that all of your shell windows will have environment variable
PSRESOURCEPATH set correctly.

3) Try to view/print the problem page again.


================== PRODUCT LIMITATIONS =========================

PRINTER MEMORY
--------------
If you encounter problems, such as a "VMerror," printing to output
devices supporting the Adobe PostScript language, it may be because
the printer has little available memory (for example, a non-upgraded
LaserWriter, LaserWriter Plus, LaserWriter II NT or NTX). There are
two potential solutions to this problem:
    1. In the Preferences dialog (select from the Edit menu) you may
       choose to use Serif only or Sans only for font substitution.
       This frees up additional memory in the printer and chances
       are your document will print successfully.
    2. The other option is to purchase more memory for your printer.

If you are using an Apple Personal LaserWriter NT printer that has
not been upgraded to a Personal LaserWriter NTR, Acrobat Reader
will not be able to print substitute fonts. Contact your Apple
dealer for information on upgrading your printer.


FOCUS PROBLEMS UNDER OPENWINDOWS WITH AUTOINPUTFOCUS
----------------------------------------------------
If you set your focus model to pointer focus and you set the
OpenWindows resource AutoInputFocus to true, then OpenWindows will
automatically give input focus to dialogs, even if the mouse is not
over the dialogs. If you use the options with Acrobat and you
operate and dismiss a dialog exclusively from the keyboard (i.e.,
never move the mouse into the dialog), then you may find that your
document window does not have focus, making it so that keyboard
accelerators such as Ctrl-G (Find Again) will not work.

If you encounter this problem, the workaround is to move the mouse
outside of your document window and then back in.


TEXT SELECTION
--------------
Unexpected Results may occur using the text select tool. This is an
inherent consequence of the way the text appears in the PDF file.
Make sure the text selection marquee intersects only with the
desired text.


TEXT GREEKING
-------------
Type 3 fonts do not greek.


NO APIs with VERSION 1.0
------------------------
Acrobat version 1.0 does not support any application programming
interfaces except via the command line. The command line
interface consists of:
	acroread <files>...

With the default setup, this command will determine whether Acrobat
Reader is already running on your machine and displaying on your
display. If so, a message is passed to Acrobat Reader telling it
to load/display the given files. Otherwise, a new version is
launched to load/display the given files. Consult the Getting
Started guide for more details.


COMMAND LINE: ONE BAD FILE CAN PREVENT OTHERS FROM LOADING
----------------------------------------------------------
If Acrobat Reader is already running and you specify that
multiple files should be opened by the already running program with
a command such as:
	acroread *

If any of the specified files is not a valid PDF file, then
all subsequent files may not be loaded. An error dialog may
appear indicating that the non-PDF file cannot be read. Then,
a message may print to the console indicating that files
cannot be loaded while a modal dialog is up (the error
dialog is a modal dialog). Also, messages may appear about
no process found to send a SIGUSR1 signal. The work-around:
only ask Acrobat Reader to load valid PDF files.


LEVEL 1 DISPLAY POSTSCRIPT FONT LIMITATIONS
-------------------------------------------
Versions of Display PostScript which are based on a Level 1
PostScript interpreter have an upper limit on the number of
fonts that can be used simultaneously. The DPS/NX that is
bundled with the application is a Level 1 versions of DPS,
whereas the DPS that is bundled with Solaris 2.3 is a Level
2 version of DPS. Thus, this problem can be encountered
under Solaris 1.1 but should not be encountered under
Solaris 2.3.

If a particular document uses more fonts than a Level 1 DPS
can manage, the following message will appear:

	Level 1 DPS font limit reached

Once this message is encountered, the application will not
be able to create additional fonts during this session; you
need to restart the application.

If you encounter this message with a single document, then
you should either: (1) change your document to use fewer
fonts or (2) upgrade your system to Solaris 2.3.


================== INSTALLATION ISSUES ===========================

INSTALLING ICONS ON OPENWINDOWS DESKTOP
---------------------------------------
There are two ways that you can invoke the olwm.deskinstall script
which installs Acrobat icons on the OpenWindows desktop: (1) if you
install Acrobat with the easy install script (easyinst.rdr), the
olwm.deskinstall script will be executed automatically, or (2) if
you manually run the script <installdir>/desktop/olwm.deskinstall,
typically after performing a custom installation (install.rdr). No
matter how it gets invoked, the olwm.deskinstall script is likely
to produce one of the following four sets of messages. 

The first message is a single line, which indicates that the icons  
were installed successfully:

	Integration with OpenWindows desktop completed.

The second set of messages will appear if you have other application
icons in either /etc/cetables/cetables (if you run the script as
root) or $HOME/.cetables/cetables (if you run the script as a normal
user). These messages indicate that Acrobat's icons have been 
installed successfully:

        add_name_space: new namespace Types
        add_avlist(NS_MANAGER, string, <$CEPATH/tns_mgr.so>)
        set_new_entry(is_ns 1)
        add_avlist(TYPE_NAME, type-id, <PortableDocumentFormat-file>)
        add_avlist(TYPE_OPEN, call, <acroread $FILE>)
	(etc.)
	Integration with OpenWindows desktop completed.

The third set of messages indicates that Acrobat icons appear to be 
already installed and that no further action is necessary:

	Icons appear to be already integrated into your desktop.

	If you find that the icons do not appear or work properly,
	you might want to run binder to remove the old icons and
	then rerun ./olwm.deskinstall to install new icons.

The fourth set of messages indicate that the integration of  
Acrobat's icons onto the OpenWindows desktop failed. A common cause
of failure is the limitation in the OpenWindows utility ce_db_merge,
which  cannot handle all possible desktop integration cases.

        Command ce_db_merge failed.
        Installation onto the OpenWindows desktop failed...exiting.
        You may need to install icons manually using the OpenWindows 
        binder program.

If you observe the previous messages, then you will have to use the 
OpenWindows binder tool to manually merge the Acrobat icons into 
your desktop. Consult the man pages and OpenWindows end-user 
documentation for information on the binder utility.


YOU DON'T HAVE TO BE ROOT TO INSTALL THE APPLICATION
----------------------------------------------------
The Getting Started guide states that you have to be root to install
the application. Actually, you can install the product from any login
as long as you run the custom installation script
(/cdrom/acroread/install.rdr) instead of the easy installation script
(/cdrom/acroread/easyinst.rdr). However, be sure that you have
write permissions to all directories and files affected by the
installation.


IF YOU INSTALL AS ROOT, INSTALL ONTO LOCAL DISK DRIVE
-----------------------------------------------------
For local disks, the root login has write privileges to all files and
directories which are writable to the owner. For NFS mounted disks,
the root login does not have the same special write priveleges.
Therefore, if you install as root, make sure that the directory into
which the application is installed (<installdir>) is a disk drive
physically attached to machine from which you are running the
installation script. Otherwise, you might see many, many errors when
you attempt to install the software about permissions problems
with the tar command and the installation will fail.


============ CONFIGURATION AND PERFORMANCE ISSUES ================

PERFORMANCE PROBLEMS WITH TYPE 3 FONTS / TeX
--------------------------------------------
Some tools, such as TeX, may generate Type 3 bitmap fonts to render
text to PostScript devices.  The PDF files produced by distilling
the PostScript output of these tools with Acrobat Distiller will
display slowly under Acrobat Reader.  If you set up your version
of TeX to substitute Type 1 fonts for TeX fonts when generating
PostScript, then the PDF files produced from that PostScript will
display much faster in Acrobat.


DEFAULT PAGE SIZE
-----------------
Adobe Acrobat Reader defaults to the size of the first page of a
document. To change the default, you can edit the X resource file
Acroread located in your home directory. Add the following line
(make sure not to leave spaces):

	*pageViewShell.geometry: wxh

w is the width of the window; h is the height.


FILE LOCKING IN MULTIPLATFORM ENVIRONMENTS
------------------------------------------
If you will use Adobe Acrobat Reader in a multiplatform Netware
environment, you may experience file locking problems when a
Macintosh or Windows user opens a file which a UNIX user wants
to open also. An Alert may appear that says:

	Unable to read file.
	Permission denied.

This message may appear even if ls -l indicates -rw-rw-rw
permissions on the file. When this situation occurs, even standard
UNIX command such as more and wc cannot open this file, not just
Acrobat. The only known workarounds are to wait for the Macintosh/
Windows users to close the file or copy the file from a
Macintosh or Windows machine to another location which will only
be opened by UNIX users.


SLOW MENUS WHEN DISPLAYED FROM HP WORKSTATIONS
----------------------------------------------
When you run the product on a Sun workstation but display on an
HP workstation, the Motif menus within Reader are slower than
other similar Motif applications.




Adobe, Adobe Acrobat, PostScript and Display PostScript are
trademarks of Adobe Systems Incorporated which may be registered in
certain jurisdictions. Sun and OpenWindows are trademarks and 
Solaris is a registered trademark of Sun Microsystems, Inc.
SPARCstation is a registered trademark of SPARC  International,
Inc., licensed exclusively to Sun Microsystems, Inc. Motif is a
trademark of Open Software Foundation. UNIX is a registered 
trademark of UNIX System Laboratories, Inc., a wholly owned
subsidiary of Novell, Inc.  

Copyright  1987-94 Adobe Systems Incorporated. All rights reserved.
