.kdfiles.

When I try to use .kdfiles to update a driver on Windows XP x64, the driver gets overwritten correctly, but when I look for the device under device manager, the device shows up with a yellow bang (“The software for this device has been blocked from starting because it is known to have problems with Windows. Contact the hardware vendor for a new driver. (Code 48)”). This does not happen under XP x32. Is there something that I am doing wrong?

map.ini:

map
\Systemroot\system32\drivers\UtSrDtuBus.sys
C:\WinDDK\7600.16385.0\src\general\UtSr\Drivers\UtSrDtuBus\lib\i386\UtSrDtuBus.sys

This path:

C:\WinDDK\7600.16385.0\src\general\UtSr\Drivers\UtSrDtuBus\lib\i386\UtSrDtuBus.sys

Id for 32-bit driver. You must select the WDK 64-bit build environments,
build the 64-bit driver and then modify the path to point to the 64-bit
binary.

Good luck!

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


From:
Sent: Tuesday, November 23, 2010 5:38 PM
To: “Windows System Software Devs Interest List”
Subject: [ntdev] .kdfiles.

> When I try to use .kdfiles to update a driver on Windows XP x64, the
> driver gets overwritten correctly, but when I look for the device under
> device manager, the device shows up with a yellow bang (“The software for
> this device has been blocked from starting because it is known to have
> problems with Windows. Contact the hardware vendor for a new driver. (Code
> 48)”). This does not happen under XP x32. Is there something that I am
> doing wrong?
>
> map.ini:
>
> map
> \Systemroot\system32\drivers\UtSrDtuBus.sys
> C:\WinDDK\7600.16385.0\src\general\UtSr\Drivers\UtSrDtuBus\lib\i386\UtSrDtuBus.sys
>
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer

xxxxx@gmail.com wrote:

When I try to use .kdfiles to update a driver on Windows XP x64, the driver gets overwritten correctly, but when I look for the device under device manager, the device shows up with a yellow bang (“The software for this device has been blocked from starting because it is known to have problems with Windows. Contact the hardware vendor for a new driver. (Code 48)”). This does not happen under XP x32. Is there something that I am doing wrong?

map.ini:

map
\Systemroot\system32\drivers\UtSrDtuBus.sys
C:\WinDDK\7600.16385.0\src\general\UtSr\Drivers\UtSrDtuBus\lib\i386\UtSrDtuBus.sys

If I may add to what Thomas said, it is bad practice to do your
development within the DDK source tree. When you go to upgrade your
DDKs, this will just make things confusing. Create your directories in
your own development tree.


Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

Thanks.

Uh … is it the same driver you are using on XP 32? If so it will never
work on XP 64 since it MUST be a 64 bit driver. You must also have set test
signing correctly for a 64 bit driver to load and initialize.

Gary G. Little
H (952) 223-1349
C (952) 454-4629
xxxxx@comcast.net

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@gmail.com
Sent: Tuesday, November 23, 2010 4:38 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] .kdfiles.

When I try to use .kdfiles to update a driver on Windows XP x64, the driver
gets overwritten correctly, but when I look for the device under device
manager, the device shows up with a yellow bang (“The software for this
device has been blocked from starting because it is known to have problems
with Windows. Contact the hardware vendor for a new driver. (Code 48)”).
This does not happen under XP x32. Is there something that I am doing wrong?

map.ini:

map
\Systemroot\system32\drivers\UtSrDtuBus.sys
C:\WinDDK\7600.16385.0\src\general\UtSr\Drivers\UtSrDtuBus\lib\i386\UtSrDtuB
us.sys


NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

__________ Information from ESET Smart Security, version of virus signature
database 5643 (20101123) __________

The message was checked by ESET Smart Security.

http://www.eset.com