HOWTO: How 1394 Diagnostic Mode Works

ID: Q221933

The information in this article applies to:

SUMMARY

A 1394 host controller can be put into Diagnostic Mode so that every detected 1394 device gets assigned the same specific hardware/device ID. Based on this hardware/device ID, a diagnostic driver such as 1394Diag.sys can load and offer test/debug options for the 1394 device.


MORE INFORMATION

Check whether the Diagnotic Mode check box is selected. To do this, from the Device Manager menu, click 1394 Bus Controller, (some 1394 controller), Properties, Settings. If the Diagnostic Mode check box is selected, then this causes the 1394Bus.sys to return a specific hardware/device ID such that another driver could be loaded, usually for test or debug purposes. When set, 1394Bus.sys (the 1394 bus enumerator) returns the hardware\device ID of 1394\031887&040892.

In the Windows 98 DDK, a sample called 1394Diag.sys in the \98Ddk\Src\1394\1394Diag path loads itself (as long as the .inf file is in the \Windows\inf or you point to it) when this specific hardware/device is used. The 1394Diag.sys sample provides a set of APIs that communicate with the 1394Bus.sys driver.

Associated with 1394Diag.sys is an application called WIN1394, which is in the \98Ddk\Src\1394\Win1394 path. This application works together with 1394Diag.sys and offers such various test scenarios as isochronous/asynchronous loopback tests.

There are no requirements to use either 1394Diag.sys or Win1394.exe. A developer could develop his or her own driver/INF that uses the 1394\031887&040892 hardware/device ID.

For more information on 1394Diag.sys and Win1394.exe, please refer to the Window 98 DDK documentation.

Additional query words: 


Keywords          : kbmm kbDDK kbKMode kbPrinting kbStorageDev kbVideo kbWinOS98 
Version           : WINDOWS:; Win98:
Platform          : WINDOWS Win98 
Issue type        : kbhowto

Last Reviewed: May 7, 1999