Re: Procedure for Windows Logo Testing

Sam Developer <> wrote:
>
>I want to install my NDIS Intermediate Filter driver without requiring
>any user interaction.
>For this I understand that the driver needs to be signed and windows
>logo certified.
>
>Please give me complete procedure for getting my driver Windows Logo
>tested.
>How many days will it take to complete the procedure after I have
>submitted my driver?

Only a few days, but it's going to be quite some time before you are in a
position to submit the driver.

You need to download the Windows Logo Kit and install it. That requires
two computers, one of which must be running Windows Server 2003. You then
install your filter on the second computer, and run the suite of tests that
are required for network class devices.

Then, you need to open a Winqual account. To do that, you must have a
Verisign certificate to validate that you are authorized to speak for your
company.

Then, you take the logs from your passing test run, and submit them along
with your driver package through your Winqual account. After that, and
payment of the fee ($250 per operating system family), they'll send back
your signed driver package.

You must submit both 32-bit and 64-bit drivers. Note that you submit for
Windows 7, and you get the XP signature as part of the deal.
--
Tim Roberts,
Providenza & Boekelheide, Inc.

>What do you mean by driver package?
>We have a setup file to install our software.
>Do we need to send that setup file or only NDIS driver with its 2 INF
>files?

Since you have INF files, you rely on PnP's setup engine to install your stuff.

This means that your setup program is calling the PnP setup routines at some point, asking PnP to install you INF+SYS files.

In such a case - no, the setup program is not a part of the package.

What is the part of the package is anything referenced in the INF - DLLs or such.

--
Maxim S. Shatskih
Windows DDK MVP

http://www.storagecraft.com

Sam Developer <> wrote:
>
>Thanks for your quick reply.
>I have some more queries related to windows logo testing?
>
>> "$250 per operating system family"
>
>What do you mean by family? Is that desktop family or server family
>classification?

This is described in the WHQL documents, which you will need to be familiar
with if you plan to move forward. A family is basically x86, x64, and ia64
for one OS release. XP is a family, Vista is a family, Server 2008 is a
family, Server 2008 R2 is a family, Windows 7 is a family. If you submit
for any other system XP is free.

So, if you want XP, Vista, and Windows 7, that would be $500.

http://winqual.microsoft.com. You need to set up a Winqual account to make
your submission. You will need a Verisign certificate to create that
account.

>I want signatures for all desktop and server operating system. i.e
>starting from Windows 2000 to Windows Server 2008 R2
>Is that sufficient if i submitted for Windows 7?

That's $1,250. Five families, and XP and 2000 come for free.

>What do you mean by driver package?
>We have a setup file to install our software.
>Do we need to send that setup file or only NDIS driver with its 2 INF
>files?

The package is your INF file, and all of the files that are mentioned in
it. You must create a CAT file that lists all of those files with their
checksums. It's the CAT file that gets signed.

>How much time does the procedure take after submitting the logs
>through winqual?

Only a few days.
--
Tim Roberts,
Providenza & Boekelheide, Inc.

>If i made any changes to INF file or in a SYS file, Do i need to pay
>again for whole procedure?

Yes.

--
Maxim S. Shatskih
Windows DDK MVP

http://www.storagecraft.com

Sam Developer <> wrote:
>
>I have another doubt regarding resigning procedure.
>If i make any changes to INF file or in driver, will I have to
>resubmit the driver package for Windows Logo Testing?
>How long will it take to complete the procedure? Will I have to repay?

The CAT file, which is the thing that gets signed, includes a checksum of
your INF and all of the files mentioned in your INF. If any of those files
changes, so that the checksums do not match, then the signature is
invalidated. You'll need to submit and pay again.
--
Tim Roberts,
Providenza & Boekelheide, Inc.

I think the WLK docs specify an XP SP to be used for testing. If you use
that one then you are OK on other SPs.

IOW: You don't have to test on each SP, but you do need to use the one they
specify in the kit you are using.

Thomas F. Divine
http://www.pcausa.com


"Sam Developer" <> wrote in message
news:737ea82d-b57a-4626-b46d-...
> On Aug 3, 7:50 am, Tim Roberts <t...@probo.com> wrote:
>> Sam Developer <iamdeveloper2...@gmail.com> wrote:
>>
>> >I have another doubt regarding resigning procedure.
>> >If i make any changes to INF file or in driver, will I have to
>> >resubmit the driver package for Windows Logo Testing?
>> >How long will it take to complete the procedure? Will I have to repay?
>>
>> The CAT file, which is the thing that gets signed, includes a checksum of
>> your INF and all of the files mentioned in your INF. If any of those
>> files
>> changes, so that the checksums do not match, then the signature is
>> invalidated. You'll need to submit and pay again.
>> --
>> Tim Roberts, t...@probo.com
>> Providenza & Boekelheide, Inc.
>
>
> Hi,
>
> Thanks for sharing your knowledge with me.
>
> I have completed installation of WLK 1.5. I have install server on
> Windows Server 2003 with SP1 and Client on Windows XP SP3.
> If I test my NDIS intermidiate filter driver on Windows XP SP3, Do i
> need to test it again for Windows XP SP2 and SP1 ?
>
> Regards,
> SAM
>
>