Allen-Bradley Company, Inc.
PanelBuilder Configuration Software
Bulletin 2711-ND3
Version 2.50.00

PanelBuilder, FontTool, and PanelView are Trademarks of 
Allen-Bradley Company, Inc.  INTERCHANGE, RSLinx, and RSLinx LITE 
are Trademarks of Rockwell Software, Inc.  Windows, Windows 95, 
Windows NT, and Office 97 are Trademarks of Microsoft Corporation.

Thank you for choosing PanelBuilder Configuration Software
Package. This file contains installation notes and last minute updates
to the user manual.  This file is typically installed in your c:\ab\pbwin 
directory.  If you wish to print this file, you may do so now by 
selecting File->Print from the menu line above.

**************************************************************************
** IMPORTANT:  PanelBuilder now contains a preferences dialog allowing  ** 
** the pre-configuration of the Add/Replace Tags/Devices dialogs.  This **
** dialog is available from the Application->Preferences menu and will  **
** allow you to set the default operation of dialogs normally displayed **
** when an application is read into PanelBuilder.  PLEASE READ THE      **
** ACCOMPANYING RELEASE NOTE FOR SPECIFIC INSTRUCTIONS ON HOW TO USE    **
** THIS DIALOG.                                                         **
**************************************************************************

The following topics are covered in this release note:
-----------------------------------------------------
.  Release notes
.  Office 97 compatibility note
.  Application conversion notes
.  Installation notes
.  RSLinx Lite
.  INTERCHANGE
.  Problems during software installation
.  Notes on using PanelBuilder with Windows for Workgroups
.  Notes on using PanelBuilder with Windows 95 and Windows NT
.  Notes on using the FontTool utility and external fonts
.  Using the PanelView File Transfer DOS Utility (PFT)
.  Installed files

Release notes:
-------------
V2.50  Adds the ability to program ControlNet terminals.  Adds ASCII 
       Input and Alarm Filter support for select terminal types.  Adds
       ability to program Modbus terminals.  Corrects a problem in
       WinPFT which results in failed uploads via Pass-Through
       connections.  Adds support for Pass-Through via ControlLogix
       Gateway connections.  Adds preferences dialog for pre-configuration
       of application load Add/Replace Tag/Device dialogs.

       Note:  When loading applications using SLC type tags it may be
       necessary to reset the device type.  This is due to the addition
       of SLC types not previously supported.  To reset the device type,
       open the Terminal Setup dialog and press the Comms Setup button.
       The device type is selected from a drop down list within the grid.

V2.40  Adds the ability to program PV1000C and PV1000G terminals.  Adds
       support for PV550 Universal Language Support and increased application
       memory space.  Adds support for RSLinx communications software version 
       1.7 and later on Windows 95 and Windows NT 4.0 platforms.  
       Provides Windows NT compatibility.

V2.32  Adds the ability to program PV600 and PV1400 DeviceNet terminals
       and PV600 and PV1400 Profibus terminals.  Also increases the
       available RAM limits for PV600 and PV1400 terminals and updates
       the internal DF1 driver.

V2.31  Adds the ability to program PV900M and PV900C DeviceNet Terminals.
       Removes the Internal DH485 Driver support.  If needed, please
       contact Allen-Bradley/Rockwell Automation Technical Support.

V2.30  Adds Universal Language Support and the ability to program PV600 and 
       PV1400 terminals.

       INTERCHANGE is only needed for Pass-Through downloads or for DH485
       downloads when Windows 3.1 or 3.11 is running.  In order
       to use the internal DF1 drivers all INTERCHANGE Drivers must be
       disabled and INTERCHANGE must not be running.  INTERCHANGE can be
       stopped by exiting Windows and typing ABICSTOP at the DOS prompt.

Office 97 Compatibility Note:
----------------------------
Users of Office 97 should install the Office 97 SR-1 patch provided by
Microsoft.  Failure to do so may result in loss of either Office 97
or PanelBuilder functionality.  Please contact Microsoft for information
concerning the SR-1 patch.  The patch may be downloaded from Microsoft's
WEB site at http://www.microsoft.com.

Application Conversion Notes:
-----------------------------
When converting applications to or from Profibus or DeviceNet terminal
types it is suggested that the existing Project Database be copied
for use with the new application. This will prevent changes in current
addresses due to the special addressing needs of these protocols. 

     How to Copy and Select a Project Database:

     1) Open the existing application, select Project Management from
        the Application Menu and note the Current Project Name. Close
        Project Management.
     2) Save current application with a new name using Save As from the
        File menu. Close the application leaving PanelBuilder running.
     3) Select Project Management from the Application Menu.
     4) Select the Project noted in step 1.
     5) Use the Copy button to copy the Project to a new name.
     6) Close Project Management.
     7) Open the new application file Saved in step 2.
     8) Select Project Management from the Application Menu.
     9) In the Current Project box, select the new project copied in
        step 5.
    10) Close Project Management, Confirm Project change by selecting
        Yes.
    11) Save the application.


Installation Notes:
-------------------
It is necessary to include the \AB\BIN and \RSI\IC\BIN (if using
INTERCHANGE) directories in your path, and to include SHARE.EXE
in your autoexec.bat file. PanelBuilder will not run without
these modifications.  Note, the installation process will do this
automatically unless the user specifically requests not to update
the AUTOEXEC.BAT file.  Also, specific AUTOEXEC.BAT configurations
may require customization following the installation.

If you are using Windows for Workgroups, Windows 95, or Windows NT, 
please refer to additional information in this file below.

Changes made to the AUTOEXEC.BAT file will not take effect until the
computer has been rebooted.

RSLinx LITE:
-----------
PanelBuilder Version 2.40 and later, makes use of RSLinx LITE to
provide communications capabilities on Windows 95 and Windows NT
platforms.  Please refer to the release notes and user documentation
specific to RSLinx LITE provided with your PanelBuilder package.
If you are updating your installation from INTERCHANGE to RSLinx
LITE, please refer to the INTERCHANGE to RSLinx User Information
provided with your PanelBuilder package.

Users of Rockwell Software products using WinLinx may need to
update their installations to prevent incompatibilities between
RSLinx LITE and WinLinx.  Please contact Rockwell Software Technical
Support for additional information.

Note:  Users are encouraged to use RSLinx LITE on Windows 95 and
Windows NT platforms.  However, INTERCHANGE may still be installed
and used on Windows 95 platforms.  To use INTERCHANGE instead of
RSLinx, select the custom install option and select INTERCHANGE
to be installed.  Refer to your PanelBuilder User Manual for
additional information.

RSLinx Lite installation on Windows NT Workstations requires the
user to administrator privilege.  RSLinx Lite will inform you if
you do not have this privilege and will abort the installation
program.  If you encounter this problem, you will need to reinstall
PanelBuilder and RSLinx Lite.

INTERCHANGE:
-----------
PanelBuilder Version 2.00 and later, makes use of INTERCHANGE to
provide communications capabilities on Windows 3.1x and Windows 95.
If you are using the PCMK PCMCIA communication card with Windows 95,
a Plug and Play driver is available from Rockwell Software.  
Contact your Allen-Bradley distributor for details.

During the installation and configuration of INTERCHANGE you may
experience error messages while your computer is rebooting or while
Windows is loading.  These indicate an incomplete or improper
configuration of the INTERCHANGE drivers.  Run the INTERCHANGE
Configuration Utility in the PanelBuilder program group, or choose 
Workstation Setup from PanelBuilder to reconfigure the INTERCHANGE
drivers.

The INTERCHANGE drivers may cause conflicts with other drivers sharing
common interrupts or memory areas in the system.  Typical problems 
involve serial mouse initialization for DOS applications, PCMCIA
drivers, and special Windows video drivers.  If you are experiencing
any of these difficulties, the following workarounds are suggested:

.  If you are using a special Windows video driver, try using the 
   standard Windows VGA driver.  It may also be necessary to edit
   the EMM386 line in the CONFIG.SYS file to remove specific memory
   exclusions added by the special video driver.

.  Disable the communication drivers using the INTERCHANGE Configuration
   Utility and reboot the computer.  If the problems persist, check
   other drivers that are loaded; there may be a conflict with other
   drivers.

.  If you are experiencing lock ups using a serial mouse in a DOS
   application, try waiting for several seconds for the mouse to
   initialize. After initialization, mouse usage should return to
   normal.  If mouse operation is still a problem, try disabling the
   INTERCHANGE drivers as suggested above.

.  Under certain circumstances, it may be necessary to create a dual
   boot environment to manage conflicting drivers.  Refer to your DOS
   user manual for information regarding multiple boot environments.

If you need to relocate INTERCHANGE to a different directory, you
must follow these steps:

1.  Remove the ABIC_CONFIG line from your AUTOEXEC.BAT file.
2.  Remove all files and directories in the current INTERCHANGE
    directory (e.g. RSI\IC).
3.  Reboot the computer.
4.  Reinstall PanelBuilder and select the option to install INTERCHANGE.
5.  Select a new destination directory for INTERCHANGE.

If you fail to perform these steps, PanelBuilder will not update
your AUTOEXEC.BAT file with the correct ABIC_CONFIG and PATH settings
for the new location.  If you need to refresh your current INTERCHANGE
installation, perform step 2 above, then reinstall PanelBuilder,
making sure to enter the same path as the original installation for
INTERCHANGE.

Additional INTERCHANGE release information may be found in the
PanelBuilder User Manual, PanelBuilder release notes, and in the
INTERCHANGE User Manual available from Rockwell Software or your
local Allen-Bradley distributor.

Problems During Software Installation:
-------------------------------------
The installation script will install the PanelBuilder files
in their proper order and setup the Windows and DOS environment
correctly to ensure proper operation.  However, user or computer
manufacturer modifications to the environment may result in
problems when operating the PanelBuilder product.  If you have
difficulties running the product, please check the following
items:

.  Make sure you reboot your computer following installation.
   Many runtime errors a rectified by performing a cold (power
   shutdown) reboot of the system following installation.

.  When installing on a Windows 95 or Windows NT system, 
   standard DOS 8x3 directory and file names must be used.  
   PanelBuilder will not run properly from directories using 
   long naming conventions.

.  You must have greater than 500KBytes of *free* base RAM to run
   the PanelBuilder.  If you do not have sufficient RAM, the
   AB Utilities database will not initialize.

.  If the AB Utilities fails to initialize, or if files cannot be
   found, please check to make sure SHARE.EXE is running and the
   path statement contains C:\AB\BIN (or appropriate path to the
   BIN directory).  The computer must be rebooted in order for
   these items to take effect.  Also, if you are running on a
   network and your environment is loaded from network files, it
   is possible that the network files are overwriting the path
   statements.  Check with your system/network administrator to
   modify the proper files.

.  You must have the drive letter on your path statement for the
   Windows directory (e.g. C:\WINDOWS, not \WINDOWS).  The
   installation program makes use of this path statement to create
   temporary files.  If the drive letter is not present, you will
   receive an "Unable to initialize setup" error message.

.  If you are installing AB Utilities into a different directory
   than a previous installation, you may need to edit your PATH
   statement to remove references to the previous installation.

Notes on using PanelBuilder with Windows for Workgroups:
-----------------------------------------------------------
Windows for Workgroups (WFW) includes a Share VxD called VSHARE.386.
This VxD (virtual device driver) replaces the SHARE.EXE installed in
the autoexec.bat file.  If your installation of WFW makes use of this
share driver, please remove the SHARE.EXE file from your autoexec.bat
file. Please refer to your WFW User Manual for details on using 
VSHARE.386.

Notes on using PanelBuilder with Windows 95 and Windows NT:
----------------------------------------------------------
Windows 95 and Windows NT include support for SHARE.EXE.  If you are 
using Windows 95 you may comment out this line in the AUTOEXEC.BAT file.
For Windows NT, this statement is ignored.

In Windows NT, the PATH statement is accessed from the Control Panel ->
System -> Environment dialog.  PanelBuilder will automatically update
this path during Install.  If you need to alter the PATH statement,
refer to the System Guide for Windows NT.

PanelBuilder does not support long file names.  File names must adhere
to the standard DOS 8x3 naming convention.  Failure to do so may result
in file not found or inability to load file error messages.

On slower computers running Windows NT it may be necessary to install
the latest NT service release to prevent problems that may occur during
long downloads.  At the time of the release of version 2.40 PanelBuilder 
the latest service release version was SR3.

Notes on using the FontTool utility and external fonts:
------------------------------------------------------
The FontTool utility is designed to create external font sets for use
with PanelView applications.  When an external font is loaded into
PanelBuilder for editing, the screen images will be displayed with
the current font.  However, the editing controls require the use
of a Windows font.  If the appropriate Windows font is not available
to the system for editing, then the editing controls will use the
current system font.

When loading a font into an Application, the operating system must
have RAM available to load the font.  Since some of the 16-bit
character set fonts are very large, RAM above the stated required
minimum may be necessary for the application to load.

Using the PanelView File Transfer DOS Utility (PFT):
---------------------------------------------------
PanelBuilder comes with a copy of the PanelView File Transfer
Utility for DOS (PFT).  This utility can be used to transfer PanelView
application files (*.PVA) between a DH485 PanelView terminal and a
computer that does not have Windows installed.

Note:  This version of PFT only works with DH485 terminals.  To 
download to an RIO terminal you must use the Windows Application File
Transfer program (WINPFT.EXE).  Refer to the PanelBuilder User 
Manual for information on WINPFT.

To use PFT, you will need to copy the following files from the 
C:\AB\PBWIN directory onto a floppy disk for transport to the DOS 
computer:

    PFT.EXE        PanelView File Transfer DOS utility
    DEFAULT.STP    PanelView File Transfer configuration file
    PIC485.EXE     PanelView File Transfer PIC module driver
    KR.EXE         PanelView File Transfer KR Card driver
    <APP>.PVA      Your PanelView Application File
    
Refer to the PanelView File Transfer Utility User Manual for details
on the operation of the PFT utility.

Installed files:
---------------
See FILELIST.TXT on PanelBuilder Install Disk 1.  This file lists all
possible installed files with version / date information.
