Microsoft Knowledge Base Email Alertz

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

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 221933 - Last Review: January 24, 2007 - Revision: 1.4

How To How 1394 Diagnostic Mode Works

System TipThis article applies to a different version of Windows than the one you are using. Content in this article may not be relevant to you. Visit the Windows Vista Solution Center
This article was previously published under Q221933

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.

APPLIES TO
  • Microsoft Windows 98 Standard Edition
  • Microsoft Windows 98 Driver Development Kit (DDK)
Keywords: 
kbhowto kbkmode kbmm kbprint kbstoragedev kbvideotech KB221933
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate