Planning Information

Note: Most of the following information is for RealPort and the Digi One RealPort and PortServer. For requirements and considerations for EtherLIte, see Requirements and Considerations: EtherLite.

Requirements

• The RealPort driver for Microsoft Windows NT requires between one and two MB of memory on the Windows NT system.
• The Windows NT RealPort driver requires a 10-pin RJ-45 cable to connect devices to Digi One RealPort or PortServer ports. 

Limitations

• Version 1.0.2 of the RealPort driver is the only version that supports Windows NT systems. You can access this driver at the Digi Web site: http://www.digi.com.
• Only TAPI-compliant applications or those written to COM 32 API (application programming interface) standards can use intelligent ports, which means only these applications can use RealPort ports.

Configuration Information

Before you begin the RealPort installation and configuration, gather the following information. Use the set config command to determine this information. 

• IP address and/or domain name of each Digi One RealPort or PortServer involved in the RealPort configuration
• The ports on each Digi One RealPort or PortServer that you intend to use for RealPort
• More information on setting up RealPort can be found at the following URL:

http://supportold.digi.com/techsupport/hardware/portserver/psrpsetup.html

Peripheral Information

Before you can correctly cable a peripheral to a RealPort port, determine the peripheral's cabling and flow control requirements. See the peripheral's documentation for information and the Digi One RealPort and PortServer Cable Guide.

Key Concept: About Port Mapping Offsets

The number of local ports on the Windows NT host offsets the port number on the Digi One RealPort or PortServer. For example, if you have two local COM ports, Port 1 of the PortServer is seen by the RealPort service as COM 3.