Re: PREfast (5744) fails some WDF headers, and thus my code too
- From: chris.aseltine@xxxxxxxxx
- Date: 1 Nov 2006 10:14:19 -0800
David J. Craig wrote:
The docs are what SHOULD happen and not what really happens. Clean out your
xml file of any IP and submit it. It does not have a signature or hash of
the driver. When and if they get it fixed the txt has a hash that will link
it to the driver, but for now hand massage the xml file.
Are you speaking from experience from a successful DTM submission where
you were asked to do this?
Why is this little tidbit not included in the DTM documentation?
Why do we need to hand-edit tool output?
I'd like someone from DTM to answer if possible, at least for the
latter two questions.
.
- References:
- Re: PREfast (5744) fails some WDF headers, and thus my code too
- From: chris . aseltine
- Re: PREfast (5744) fails some WDF headers, and thus my code too
- From: David J. Craig
- Re: PREfast (5744) fails some WDF headers, and thus my code too
- From: Dan
- Re: PREfast (5744) fails some WDF headers, and thus my code too
- From: David J. Craig
- Re: PREfast (5744) fails some WDF headers, and thus my code too
- Prev by Date: RtlQueryRegistryValues
- Next by Date: Re: two network adapters on a dual processor - on interrupt routin
- Previous by thread: Re: PREfast (5744) fails some WDF headers, and thus my code too
- Next by thread: Re: PREfast (5744) fails some WDF headers, and thus my code too
- Index(es):
Relevant Pages
|