Tim said:
This appears to be a common problem reported on the microsoft.public
groups from time to time over the years ...
How does one tell Microsoft that the device has a new Class and
ClassGUID, so please don't reject it just because CHKINF says
E22.1.1310 ClassGUID is unrecognized?
The answer is to nicely ask Microsoft for the Incident ID to the
following:
10/18/2005 2:15 PM
The ChkINF test fails on INF files that use a custom class and a custom
GUID. The use of a custom class and custom GUID should only be used
for devcies submitted through the unclassified category. This issue
will cause the following test failure in the log file:
ERROR: (E22.1.1310) Class XXXXX (ClassGUID
{XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}) is unrecognized.
Where X can be any value.
This issue described is an acceptable failure. When making a submission
with a failed log for this test, refer to this issue with the Incident
ID number in the Readme.doc file included with your test submission
package.
I now have my driver signed. Thank you very much! Also, don't forget to
mention and correct for Errata 1418 where HCT doesn't always run ChkINF
for you.
Share and enjoy,
Tim Green.
