Prev: Characters allowed in short filenames
Next: NdisTest60 and unrecognized OIDs
From: SenseShankar on 15 Apr 2008 08:54

Hi,

I am upto go with making Test signing for my driver set (UsbSer.sys +
MyConvert.INF). i followed the KMCS_walkthrough.doc which explains how to
proceed to obtain a test sign the data in summary says so -
1. Prepare a computer for test-signing.
2. Create a test certificate by using MakeCert.
3. Create a catalog file by using MakeCat or Inf2Cat.
4. Test-sign the catalog file by using SignTool.
5. Install the test certificate in the Trusted Root Certification
Authorities certificate store.

Now coming to my issue, i am through step 2. but for step 3 (using the
Toaster examples .CMD script file in WDK(6000)) i am not able to generate a
..cat file to proceed further in which "Signability" tool is used in the .cmd
file

did anyone encounter the same before, i came to know that "INF2Cat" is the
one much effective, but in vain, neither i could get it as standalone nor
with "winqual submission tool .msi setup".

Thankful if any one could suggest how to proceed either "how to generate a
..CAT file using signability" else a place to get inf2cat.exe (and its
components).




--
Thanks in advance,
Shankar G.
From: duff_man on 17 Apr 2008 08:02
`"SenseShankar" <SenseShankar(a)discussions.microsoft.com> wrote in message
news:9F3FF31D-25B6-43DB-94BB-E78FD3724918(a)microsoft.com...
>
> Hi,
>
> I am upto go with making Test signing for my driver set (UsbSer.sys +
> MyConvert.INF). i followed the KMCS_walkthrough.doc which explains how to
> proceed to obtain a test sign the data in summary says so -
> 1. Prepare a computer for test-signing.
> 2. Create a test certificate by using MakeCert.
> 3. Create a catalog file by using MakeCat or Inf2Cat.
> 4. Test-sign the catalog file by using SignTool.
> 5. Install the test certificate in the Trusted Root Certification
> Authorities certificate store.
>
> Now coming to my issue, i am through step 2. but for step 3 (using the
> Toaster examples .CMD script file in WDK(6000)) i am not able to generate
> a
> .cat file to proceed further in which "Signability" tool is used in the
> .cmd
> file
>
> did anyone encounter the same before, i came to know that "INF2Cat" is the
> one much effective, but in vain, neither i could get it as standalone nor
> with "winqual submission tool .msi setup".
>
> Thankful if any one could suggest how to proceed either "how to generate a
> .CAT file using signability" else a place to get inf2cat.exe (and its
> components).
>

I tried to sign the driver itself, but it doesn't work on Vista 64-bit. It
seems like self-signing is not working.
If you do it, please share the secret with me :-)


From: Ray Trent on 17 Apr 2008 12:52
duff_man wrote:
> I tried to sign the driver itself, but it doesn't work on Vista 64-bit. It
> seems like self-signing is not working.
> If you do it, please share the secret with me :-)

Did you follow the instructions in the "How to Install and Load a
Test-Signed Driver Package" section of KMCS_walkthrough.doc? E.g. did
you enabled test signing on the target machine using bcdedit?

If so, did you follow the instructions in the "How to Troubleshoot
Test-Signed Drivers" section? What did the event log show you?
--
Ray
From: Jennifer Stepler [MSFT] on 17 Apr 2008 17:12
INF2CAT is now shipped in the WDK. Install 6001 from Connect.
If inf2cat doesn't generate your cat file, please include specific failure
information when you post.
Thanks,
Jennifer

"SenseShankar" wrote:

>
> Hi,
>
> I am upto go with making Test signing for my driver set (UsbSer.sys +
> MyConvert.INF). i followed the KMCS_walkthrough.doc which explains how to
> proceed to obtain a test sign the data in summary says so -
> 1. Prepare a computer for test-signing.
> 2. Create a test certificate by using MakeCert.
> 3. Create a catalog file by using MakeCat or Inf2Cat.
> 4. Test-sign the catalog file by using SignTool.
> 5. Install the test certificate in the Trusted Root Certification
> Authorities certificate store.
>
> Now coming to my issue, i am through step 2. but for step 3 (using the
> Toaster examples .CMD script file in WDK(6000)) i am not able to generate a
> .cat file to proceed further in which "Signability" tool is used in the .cmd
> file
>
> did anyone encounter the same before, i came to know that "INF2Cat" is the
> one much effective, but in vain, neither i could get it as standalone nor
> with "winqual submission tool .msi setup".
>
> Thankful if any one could suggest how to proceed either "how to generate a
> .CAT file using signability" else a place to get inf2cat.exe (and its
> components).
>
>
>
>
> --
> Thanks in advance,
> Shankar G.
From: Jennifer Stepler [MSFT] on 17 Apr 2008 17:15
When you say "it doesn't work on Vista 64-bit" what isn't working? Please
provide more details.
Thanks,
Jennifer


"duff_man" wrote:

> `"SenseShankar" <SenseShankar(a)discussions.microsoft.com> wrote in message
> news:9F3FF31D-25B6-43DB-94BB-E78FD3724918(a)microsoft.com...
> >
> > Hi,
> >
> > I am upto go with making Test signing for my driver set (UsbSer.sys +
> > MyConvert.INF). i followed the KMCS_walkthrough.doc which explains how to
> > proceed to obtain a test sign the data in summary says so -
> > 1. Prepare a computer for test-signing.
> > 2. Create a test certificate by using MakeCert.
> > 3. Create a catalog file by using MakeCat or Inf2Cat.
> > 4. Test-sign the catalog file by using SignTool.
> > 5. Install the test certificate in the Trusted Root Certification
> > Authorities certificate store.
> >
> > Now coming to my issue, i am through step 2. but for step 3 (using the
> > Toaster examples .CMD script file in WDK(6000)) i am not able to generate
> > a
> > .cat file to proceed further in which "Signability" tool is used in the
> > .cmd
> > file
> >
> > did anyone encounter the same before, i came to know that "INF2Cat" is the
> > one much effective, but in vain, neither i could get it as standalone nor
> > with "winqual submission tool .msi setup".
> >
> > Thankful if any one could suggest how to proceed either "how to generate a
> > .CAT file using signability" else a place to get inf2cat.exe (and its
> > components).
> >
>
> I tried to sign the driver itself, but it doesn't work on Vista 64-bit. It
> seems like self-signing is not working.
> If you do it, please share the secret with me :-)
>
>
>
 | 
Pages: 1
Prev: Characters allowed in short filenames
Next: NdisTest60 and unrecognized OIDs