User`s guide

Dialogic
®
System Release 6.0 PCI for Windows
®
Release Update, Rev 62 — January 30, 2008 362
Dialogic Corporation
The rtftool utility is a stand-alone program, and it is not necessary to have the
Dialogic
®
System Release installed on the system in order to convert RTF log files
from binary to text format.
Note: When generating large binary files with RTF, do not split the single large
binary file and then use the individual split files with the rtftool utility. Rtftool
will not work with chopped binary files.
Update to Chapter 29, RTFManager Reference (IPY00037518)
Section 29.5, General Tab, says that binary log format is not supported by the
current release. This is not correct; binary log format is supported. For information
about binary log files, see the update to Chapter 28, Runtime Trace Facility (RTF)
Reference above.
Update to Chapter 30, Status Monitor Reference
An enhanced version of the Status Monitor tool (statusmon) is provided in the Service
Update. The previous version of the tool is still supported. For information about the
new version, see Section 1.21.2, “Status Monitor (statusmon)”, on page 82 of this
Release Update.
3.3.4 Dialogic
®
System Software for PCI Products on Windows
®
Administration Guide
Single board start/stop for selected Dialogic
®
JCT Boards
Because of a new feature in the Service Update, the ability to stop and start a single
Dialogic
®
JCT Board (after the system has initially started) is now supported.
Guidelines for performing a single board stop/start should be added to the
Administration Guide. For information about this feature, see Section 1.50, “Single
Board Start/Stop for Selected Dialogic
®
JCT Boards”, on page 178 of this Release
Update
Update to Section 2.1.1.2, Start Server Only Mode
Change Section 2.1.1.2, Start Server Only Mode, to read:
Selecting the Start Server Only mode from the System/Device autostart submenu causes the
Dialogic
®
Service to start automatically when the system reboots. The boards will be automatically
detected, but not started. In this mode, you will need to start the boards manually through the DCM
GUI or the NCM API.
This mode allows Windows
®
NT Service applications to start and stop the boards without any
dependency on the Dialogic
®
Service.
Updates to Section 3.3, Replacing a Board in the System
The paragraph preceding Step 1 of the procedure is replaced by the following:
The following procedure describes the basic steps for removing a PCI board and replacing it with a
board identical in model and type in the same slot in the system.
Step 7 of the procedure is replaced by the following:
7. Depending on the DCM System/Device autostart option selected, the replacement board will
be detected when the system is rebooted and either be started, or remain in the stopped state,
allowing you to manually configure and start the board. See Figure 4 for a display of the
Device menu.