How to read DTM *.cpk file?

Hi friends,
My WHQL DTM testing file “Xxxxx.cpk” reports that a “SCSIComplianceTest” failure, but I can’t see any more useful info from this “Xxxxx.cpk” file. i.e., I can’t see whether mode sense(6) or read(6) cause the trouble. So how can I get more useful info from “Xxxxx.cpk” file?
Thank you!

The DTM test logs are the .CPK. These can be examined using the DTM Log Viewer, which can be downloaded from this page:

http://www.microsoft.com/whdc/whql/WHQLdwn.mspx

Good luck,

Thomas F. Divine

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:bounce-315856-
xxxxx@lists.osr.com] On Behalf Of zoranzi021@163.com
Sent: Tuesday, February 26, 2008 9:22 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] How to read DTM *.cpk file?

Hi friends,
My WHQL DTM testing file “Xxxxx.cpk” reports that a
“SCSIComplianceTest” failure, but I can’t see any more useful info from
this “Xxxxx.cpk” file. i.e., I can’t see whether mode sense(6) or
read(6) cause the trouble. So how can I get more useful info from
“Xxxxx.cpk” file?
Thank you!


NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

Yes, I did use DTM Log Viewer.

Wesley

I double click the item “SCSI Compliance Test (LOGO)” in “Failed Tests”, but see nothing useful.
Then I double click and “Test Detail” dialog occurs, but I see nothing useful, either.

DTM Log Viewer can read .cpk files which consists of results.

The reasons for any test failure can be analyzed using DTM itself by right clicking failed job and viewing the result.

The following link may be helpful. Kindly go through it:

http://blogs.msdn.com/storwdk/archive/2006/10/05/Diagnosing-failures-in-DTM.aspx

Regards.

Hi Uday Bhaskar,
Thank you. I read your link. Now I am puzzled whether “*.cpk” file is the only log file of WHQL DTM testing?

> -----Original Message-----

From: xxxxx@lists.osr.com [mailto:bounce-315992-
xxxxx@lists.osr.com] On Behalf Of zoranzi021@163.com
Sent: Wednesday, February 27, 2008 11:04 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] How to read DTM *.cpk file?

Hi Uday Bhaskar,
Thank you. I read your link. Now I am puzzled whether “*.cpk” file is
the only log file of WHQL DTM testing?
[PCAUSA] As far as I know the .cpk file contains all the log files. Notice that when it runs it expands a LOT of individual files into a temp directory. You can select errors and drill down further to find more information.

Unfortunately, DTM is difficult to use and I would not doubt that sorting through the information is a chore and in the end might not provide a really clear picture of why there is an error.

In most cases you should know when you run the test that the test has failed. In this case, making a .CPK file is a waste of time. You would use the DTM studio to drill down through the logs to find the problem cause (if you can).

It is also helpful in early attempts to pass tests to have WinDbg attached to the client. Sometimes you might see information in the debug messages that would be helpful.

Good luck. (You will need it…).

Thomas F. Divine


NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

Thats the correct point. When we know that the test has been failed, no
need to create the submission package .cpk file

Instead of running the entire tests, just run the test which is failing and
use DTM to analyze the failures.

Regards.

Hi Thomas Divine and Uday Bhaskar,
Now I have done WHQL testing by myself. And as you two said, DTM studio gives more useful info than DTM log viewer.
Thank you for your help.

The DTM Log Viewer wasn’t created to provide more useful info than the DTM studio, that would be quite a leap for a project I did to replace piledriver. Piledriver did not replace HCT, nor is the log viewer positioned to replace the studio. The main function of the log viewer was and continues to be, to provide an external tool that would open a cpk file, provide info on whether the cpk would pass based on manifest info, provide a look into the submission meta data and provide a link to view the manifest set of logs. I’m the author.