Prev: Writing a 1394 interface driver
Next: MmAllocateMappingAddress() and MmProbeAndLockPages()
From: Andriy on 14 Sep 2010 03:34
Hello,

I experience a problem with /O-option of the ChkInf.bat within WDK 7.1.0
installation.
/O-switch with given path generates me 2 files: "summary.htm" and something
like
"@+objCHK_WNET_X86+i386+__MyDRIVER.htm" under the given path.
In summay.htm there is a link to this second .htm-file with complex name.
But it doesn't work. I looked into HTML code of the summary.htm. There is a
tag:
<A
HREF=".\objCHK_WNET_X86\i386\CheckInfResults\@+objCHK_WNET_X86+i386+__MyDRIVER.htm">.\objCHK_WNET_X86\i386\MyDRIVER.inf:</A>
Because of the relative link in HREF it doesn't work. The tag should be:
<A
HREF="@+objCHK_WNET_X86+i386+__MyDRIVER.htm">.\objCHK_WNET_X86\i386\MyDRIVER.inf:</A>
If so - works!
Hopefully, the defect will be corrected.

Regards,
Andriy
From: Scott Noone on 14 Sep 2010 09:53
You can submit this to the WDK Community Bug Bash. Not only does it get the
bug to the right people, but it also gets you a prize :)

http://www.osronline.com/page.cfm?name=bugbash

-scott

--
Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com
http://twitter.com/analyzev


"Andriy" <Andriy(a)discussions.microsoft.com> wrote in message
news:4F9E509B-5062-4B3B-B6D4-2E33CAB6F754(a)microsoft.com...
> Hello,
>
> I experience a problem with /O-option of the ChkInf.bat within WDK 7.1.0
> installation.
> /O-switch with given path generates me 2 files: "summary.htm" and
> something
> like
> "@+objCHK_WNET_X86+i386+__MyDRIVER.htm" under the given path.
> In summay.htm there is a link to this second .htm-file with complex name.
> But it doesn't work. I looked into HTML code of the summary.htm. There is
> a
> tag:
> <A
> HREF=".\objCHK_WNET_X86\i386\CheckInfResults\@+objCHK_WNET_X86+i386+__MyDRIVER.htm">.\objCHK_WNET_X86\i386\MyDRIVER.inf:</A>
> Because of the relative link in HREF it doesn't work. The tag should be:
> <A
> HREF="@+objCHK_WNET_X86+i386+__MyDRIVER.htm">.\objCHK_WNET_X86\i386\MyDRIVER.inf:</A>
> If so - works!
> Hopefully, the defect will be corrected.
>
> Regards,
> Andriy

 | 
Pages: 1
Prev: Writing a 1394 interface driver
Next: MmAllocateMappingAddress() and MmProbeAndLockPages()