Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Software on Networks
Carrier Corporation
1.0 Introduction
This document provides information about installing and operating Carrier software on networked
computer systems.
Network capabilities depend on the type of software involved. Currently there are three types of Carrier
software in circulation: DOS-based, 16-bit Windows and 32-bit Windows. The software is steadily being
converted to the 32-bit Windows format, but in the interim some programs are still in a DOS-based or 16-
bit Windows format. Briefly:
• 32-bit Windows Software can be configured for network operation. The remainder of this manual
explains how to install, operate and maintain the 32-bit software on a network system. 32-bit
Windows software includes:
AHUBuilder v4.0 and later. Refrigerant Piping Design v4.0 and later
Air Terminal Selection v3.0 and later. RTUBuilder v1.0 and later.
Chiller System Optimizer v2.0 and later WSHP Builder v4.0 and later,
Commercial Split Systems v4.0 and later 19XR Evergreen ChillerBuilder v3.0 and later
Hourly Analysis Program v4.0 and later.
The discussion of networking 32-bit software begins with a summary:
• Quick Start (Section 1.1) - A concise summary of how to install and configure the software for
network operation.
The remaining sections of the manual provide greater detail on each subject involving 32-bit
Windows programs:
• Overview of Network Concepts (Section 1.2)
• Installing the Software on a Network (Section 1.3)
• Running the Software on a Network (Section 1.4
• Adding Users (Section 1.5)
• Removing Users (Section 1.6)
• Adding or Updating Programs (Section 1.7)
• Uninstalling Software from the Network (Section 1.8)
• 16-bit Windows Software should not be configured for network operation. The software uses
database files for data storage and these databases have not been configured for concurrent access.
Therefore, there is a danger that multiple users working with the same database file at the same time
on a network drive will corrupt or destroy information in the database file. Thus, our
recommendation against networking this software. 16-bit software includes:
Block Load v3.x Rooftop Packaged Units v6.x
Commercial Inve$t v1.x Unit Ventilator Selection v1.x
Nu-Fin Coil Selection v1.x 30 Series Chiller Selection v2.x
• DOS-Based Software can be configured for network operation. Please refer to Chapter 9 of the
E20-II Guide to Operations or Electronic Catalog Guide to Operations manuals for complete
instructions. DOS software includes:
Duct Design v3.x Water Piping Design v3.x
DuctLINK v2.x 42 Series Fan Coil Selection v2.x
Engineering Economics v2.x 23XL Chiller Selection v2.x
HAP v3.x
7. Assign Read, Write, Create and Destroy file privileges to the \E20-II folder on the server drive and all
its subfolders. It is possible to be more selective about assigning file privileges if you wish. See
1.3.3 for details
3. Network Aware: Programs which are designed to detect the presence of the network and make
active use of networking features. These programs provide added benefits to the user beyond those of
a network compatible program and reduce the maintenance work required of network administrators.
4. Network Dependent: Programs which are designed exclusively for network operation and must be
installed on a network. These programs tend to make optimal use of network resources, but are often
tied to the features of a specific vendor’s network operating system
1.2.2 Client/Server
The Carrier software is not client/server software. Software components must be installed on both the
central server and the workstation. A single installation procedure run from the workstation automatically
installs the required software on both the central server and the workstation.
For the highest level of data security, we recommend that users store data in areas of the network to
which they alone have read and write access privileges. As noted in 1.4.3 below, there is a way for
users to log into the Carrier software using another person’s network ID and gain access to this
person’s data. If data has been stored in an area of the network in which other users are not permitted
to read, write, create or destroy data, then the user’s data will be protected from unwarranted access.