DMI Component Test System for DMI 2.0 Release Notes for DCTS2 version 2.0.0.15, DTE version 2.0.0.21 DCTS2.EXE is a native 32-bit Windows application and runs on either Windows 95 or Windows NT version 3.51 or later. This release of the application has been extensively tested and contains no known fatal flaws. DCTS2 is specifically a DMI v2.0 compatible application. It does not support DMI v1.x in any way. For testing DMI v1.x Service Layers or instrumentation, you need to use DCTS.EXE (16-bit) or DCTS32 (32-bit). The latest versions of these applications are available on Intel's web site at "http://developer.intel.com/ial/dmi/dcts". [Differences from 1.x versions of DCTS] The user interface of DCTS2 is very similar to that of the previous, DMI v1.x compatible versions, so users of earlier versions will find it quite familiar. The biggest differences are: - Remote Service Provider connections. DCTS2 can connect via RPC to any number of remote systems. Currently, only DCE RPC is sup- ported but support for other RPC variations will be forthcoming. This means that you can run DCTS2 on a Windows 95 or NT system, and test DMI v2.0 SP's on other, non-Windows platforms (that support DCE RPC). - DCTS2's test result output is simplified from the 1.x method. Test results are formatted into readable text and written to a window (the Test Monitor), or directly to a log file, or both. The Report Generator used by DCTS 1.x is no longer required. - Multiple browser windows can be opened at once. Each browser window can be assigned to a different system. The menu structure is basically the same, with a few additions that are mainly related to system connections. Construction of Test Execution Lists (TELs) is also very similar, although the process has been cleaned up a bit. Any sessions and TELs (.SSN and .TEL) files that were created by DCTS 1.x will not be usable by DCTS2, and vice versa. The internal database, used by DCTS2 during TEL construction, is now managed on a per-system basis. The data (a list of MIF files) used to build the internal database used to be part of the session data; it is now part of the system connection parameters. One of the last steps in creating a TEL command is to choose whether or not to create an error condition test. This is controlled through a checkbox in the TEL dialog that is always cleared upon reaching this step. If this Error checkbox is checked, the Prev Step button is disabled, and backing up through the current command is no longer supported for the current command. Further details of DCTS2 can be found in the Introduction document. [Known Bugs] - The internal database does not handle OS identifiers for WIN95 or WINNT in MIF file Path statements. If a Path statement includes either of these identifiers, a syntax error is reported and the MIF is not installed. This applies only to the DCTS internal database; behaviour of the DMI database is dependent on the Service Provider. WORKAROUND: The WIN32 OS identifier is correctly handled, so you can use that in your MIF files instead of WIN95 or WINNT. This should only be a drawback if your instrumentation is written specifically for one of these OS's and does not work on the other. - The attribute value field in the browser window does not always show Octet string characters properly. - Automatic browser updates on receipt of indications for Component Added or Component Deleted is not always correct. WORKAROUND: If you suspect that a browser window is not showing accurate information about a system, close the browser and re-open it for the system in question, or open a second browser window. - There is no automatic browser update on receipt of indications for Languages or Groups Added or Deleted. WORKAROUND: As with Components Added/Deleted indications, if you suspect that the browser window is not up to date, close it and re- open it. - When either of the Test Monitor or Event Monitor windows are closed, there is no warning given if the monitor's text has not been saved. WORKAROUND: The Test Monitor contents are duplicated in a log file, if you enable results logging (via the Preferences dialog) before executing your TEL. - If the contents of the Test Monitor or Event Monitor window exceeds about 2000 lines (not hard to do, especially the Test Monitor!), the text will wrap around vertically in the window and trash the display. This behaviour occurs only under Windows95, not under Windows NT. WORKAROUND: If the window contents are saved to disk via the Save Report or Save Report As commands in the File menu, the resulting text file will contain the complete report, without error. - When installing components from the DCTS Install menu, if the Both Databases option is selected, the component may not be flagged as available for test even though both installations succeed. This is due to the latency time of AddComponent Indications being propagated through the system. This is more likely to occur on slower systems. WORKAROUND1: Install the component via a TEL. The indication latency is accounted for correctly for this installation path. WORKAROUND2: Install the component in two steps: First into the Service Provider database, then into the DCTS internal database. It is important that the installation into the SP database happen first. - When the Max Simultaneous count is > 1 during a test run, commands may not be submitted to the Service Provider in the exact order they are defined in the TEL. This is due to thread timing issues and is beyond the control of DCTS. Commands are logged in the same order they are defined in the TEL. Note that this logging order may indicate errors when none actually exist. For example, a DmiSetAttribute followed immediately by a DmiGetAttribute to the same attribute. The DmiGetAttribute may return the value of the attribute before the DmiSetAttribute, when in fact the DmiSetAttribute succeeded. WORKAROUND: None. This is an Operating System thread timing issue, beyond control of DCTS.Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.