Ok, this bounced the first time apparently because I replied to the
digest email… So I apologize in advance if this is a duplicate…
Here’s some Microsoft-inspired confusion.
In their KB article here:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;837643
Microsoft tells how to determine if the system is booting in safe mode
from your driver.
Hector from OSR also mentions the same thing in a memo here:
http://www.osronline.com/article.cfm?id=300
BUT in their latest hardware newsletter, Microsoft posted a link to a
page listing illegal kernel driver imports:
http://www.microsoft.com/whdc/driver/kernel/km-fns.mspx
Lo and behold… InitSafeBootMode is declared as being illegal, and
supposedly WHQL won’t sign the driver if it imports it.
In the doc that lists the illegal imports, the alternative to importing
this symbol is stated as “For information about the correct interfaces
to use, see the DDK documentation.”
Maybe I’m missing something, but this doesn’t appear to be in the DDK?
Can someone (from Microsoft or anywhere else) share some info on the
correct and WHQL-able way to determine if your driver is loaded in safe
mode?
Thanks,
sean
Thanks for the feedback Sean. It looks like last newsletter, specifically
the km-fns.doc, did not include details on which illegal imports were
considered as PIT errors or warnings.
“InitSafeBootMode” in particular is considered a warning and using this
function will not results in a PIT tool failure.
If warnings are encountered it is recommended that the developer review the
implementation of the function to ensure there are not better alternatives
documented, however the driver will still pass the PIT test and can move
forward with logo testing. If the PIT tool encounters imports that are
considered as Error’s the test will fail and logo can not be achieved until
these imports are resolved.
An update is currently in the works and will be posted by Monday.
http://www.microsoft.com/whdc/driver/kernel/km-fns.mspx
The updated document will contain a “Test result” column that displays if a
given function or import is considered an Error or a Warning.
~Brian
“Sean Bullington” wrote in message news:xxxxx@ntdev…
> Ok, this bounced the first time apparently because I replied to the digest
> email… So I apologize in advance if this is a duplicate…
>
> Here’s some Microsoft-inspired confusion.
>
> In their KB article here:
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;837643
>
> Microsoft tells how to determine if the system is booting in safe mode
> from your driver.
>
> Hector from OSR also mentions the same thing in a memo here:
> http://www.osronline.com/article.cfm?id=300
>
> BUT in their latest hardware newsletter, Microsoft posted a link to a
> page listing illegal kernel driver imports:
> http://www.microsoft.com/whdc/driver/kernel/km-fns.mspx
>
> Lo and behold… InitSafeBootMode is declared as being illegal, and
> supposedly WHQL won’t sign the driver if it imports it.
>
> In the doc that lists the illegal imports, the alternative to importing
> this symbol is stated as “For information about the correct interfaces
> to use, see the DDK documentation.”
>
> Maybe I’m missing something, but this doesn’t appear to be in the DDK?
>
> Can someone (from Microsoft or anywhere else) share some info on the
> correct and WHQL-able way to determine if your driver is loaded in safe
> mode?
>
> Thanks,
> sean
>
>
>
Updated document has been posted.
http://www.microsoft.com/whdc/driver/kernel/km-fns.mspx
~Brian
“Brian Lysak [MSFT]” wrote in message
news:xxxxx@ntdev…
> Thanks for the feedback Sean. It looks like last newsletter, specifically
> the km-fns.doc, did not include details on which illegal imports were
> considered as PIT errors or warnings.
>
> “InitSafeBootMode” in particular is considered a warning and using this
> function will not results in a PIT tool failure.
>
> If warnings are encountered it is recommended that the developer review
> the
> implementation of the function to ensure there are not better alternatives
> documented, however the driver will still pass the PIT test and can move
> forward with logo testing. If the PIT tool encounters imports that are
> considered as Error’s the test will fail and logo can not be achieved
> until
> these imports are resolved.
>
> An update is currently in the works and will be posted by Monday.
>
> http://www.microsoft.com/whdc/driver/kernel/km-fns.mspx
>
> The updated document will contain a “Test result” column that displays if
> a
> given function or import is considered an Error or a Warning.
>
> ~Brian
>
>
> “Sean Bullington” wrote in message news:xxxxx@ntdev…
>> Ok, this bounced the first time apparently because I replied to the
>> digest email… So I apologize in advance if this is a duplicate…
>>
>> Here’s some Microsoft-inspired confusion.
>>
>> In their KB article here:
>> http://support.microsoft.com/default.aspx?scid=kb;EN-US;837643
>>
>> Microsoft tells how to determine if the system is booting in safe mode
>> from your driver.
>>
>> Hector from OSR also mentions the same thing in a memo here:
>> http://www.osronline.com/article.cfm?id=300
>>
>> BUT in their latest hardware newsletter, Microsoft posted a link to a
>> page listing illegal kernel driver imports:
>> http://www.microsoft.com/whdc/driver/kernel/km-fns.mspx
>>
>> Lo and behold… InitSafeBootMode is declared as being illegal, and
>> supposedly WHQL won’t sign the driver if it imports it.
>>
>> In the doc that lists the illegal imports, the alternative to importing
>> this symbol is stated as “For information about the correct interfaces
>> to use, see the DDK documentation.”
>>
>> Maybe I’m missing something, but this doesn’t appear to be in the DDK?
>>
>> Can someone (from Microsoft or anywhere else) share some info on the
>> correct and WHQL-able way to determine if your driver is loaded in safe
>> mode?
>>
>> Thanks,
>> sean
>>
>>
>>
>
>
>