I have HID driver develped for custom device in Vista 32 bit operating system and I am preinstalling it with the DPInst.exe
The installation completes with successfully and when I attach the device to the system, the driver gets loaded from the driver store - file repository normally.
Now the same I want to test for Vista 64 bit operating system and my machine has AMD board.
For this I approached as below:
Builded the driver in 64 bit Vista build environment.
Taken AMD64 DPInst for pre installing.
Decorated manufacturer section of the inf file with nt.amd64
The drive package preinstalling is completing successfully. But when I attach the device, the preinstalled driver is not getting loaded.
Do I need to modify any other settings in the inf file. The following statements from the setupapi.dev.log may be useful to analyze the actual error:
this may be basic thing but here it is. Vista64 will load any driver only if
it is signed , is ur driver signed ?
rtshiva
wrote in message news:xxxxx@ntdev… > Dear Team, > > I have HID driver develped for custom device in Vista 32 bit operating > system and I am preinstalling it with the DPInst.exe > > The installation completes with successfully and when I attach the device > to the system, the driver gets loaded from the driver store - file > repository normally. > > Now the same I want to test for Vista 64 bit operating system and my > machine has AMD board. > > For this I approached as below: > > 1. Builded the driver in 64 bit Vista build environment. > 2. Taken AMD64 DPInst for pre installing. > 3. Decorated manufacturer section of the inf file with nt.amd64 > > The drive package preinstalling is completing successfully. But when I > attach the device, the preinstalled driver is not getting loaded. > > Do I need to modify any other settings in the inf file. The following > statements from the setupapi.dev.log may be useful to analyze the actual > error: > > ================= > setupapi.dev.log > ================= > > flq : File ‘C:\Windows\system32\DRIVERS\hidusbosrfx2.sys’ pruned from > copy. > cpy : DrpSetRegFileProt ‘C:\Windows\system32\DRIVERS\hidusbosrfx2.sys’ > Status=0 Class=OEM Legacy > > flq : File ‘C:\Windows\system32\DRIVERS\hidmapper.sys’ pruned from copy. > cpy: DrpSetRegFileProt ‘C:\Windows\system32\DRIVERS\hidmapper.sys’ > Status=0 Class=OEM Legacy > > flq : File ‘C:\Windows\system32\WdfCoInstaller01005.dll’ pruned from > copy. > cpy : DrpSetRegFileProt ‘C:\Windows\system32\WdfCoInstaller01005.dll’ > Status=0 Class=OEM Legacy > > Regards. >
Your driver needs to be signed for x64 Vista. There are three ways to
get around this requirement temporarily:
1.) Press F8 every time you boot to disable signing requirements. This
used to be an option; it may not be anymore, and it’s pretty much
useless anyway.
I have HID driver develped for custom device in Vista 32 bit operating system and I am preinstalling it with the DPInst.exe
The installation completes with successfully and when I attach the device to the system, the driver gets loaded from the driver store - file repository normally.
Now the same I want to test for Vista 64 bit operating system and my machine has AMD board.
For this I approached as below:
Builded the driver in 64 bit Vista build environment.
Taken AMD64 DPInst for pre installing.
Decorated manufacturer section of the inf file with nt.amd64
The drive package preinstalling is completing successfully. But when I attach the device, the preinstalled driver is not getting loaded.
Do I need to modify any other settings in the inf file. The following statements from the setupapi.dev.log may be useful to analyze the actual error:
Thanks for the pointers. I understood that Kernel Mode Driver for Vista 64
must have Digital Signature. The followed the third step of test signing
the driver.
In the case of 32 bit installation package the inf file includes the
following:
[copyfiles]
mydrv.sys
hidclass.sys
hidparser.sys
hid.dll
Since all these are system related HID drivers which are already located in
the system (except mydrv.sys), there is only one mydrv.sys included in the
installation package and everything went on correctly.
In the case of 64 bit installation, setupapi.dev.log points that the
specified files hidclass.sys, etc are not found. When I try to locate them
on the disk, they are present.
When I still include them in driver package, the installation is smooth.
Any reasons for this behaviour.
Regards.
On Jan 14, 2008 11:16 PM, Martin O’Brien wrote:
> Your driver needs to be signed for x64 Vista. There are three ways to > get around this requirement temporarily: > > 1.) Press F8 every time you boot to disable signing requirements. This > used to be an option; it may not be anymore, and it’s pretty much > useless anyway. > > 2.) Establish a KD connection during boot > > 3.) Test sign your driver - > > http://msdn2.microsoft.com/en-us/library/aa906283.aspx > > and use bcdedit to allow test signed driver support: > > bcdedit /set testsigning on > > Good luck, > > mm > > xxxxx@gmail.com wrote: > > Dear Team, > > > > I have HID driver develped for custom device in Vista 32 bit operating > system and I am preinstalling it with the DPInst.exe > > > > The installation completes with successfully and when I attach the > device to the system, the driver gets loaded from the driver store - file > repository normally. > > > > Now the same I want to test for Vista 64 bit operating system and my > machine has AMD board. > > > > For this I approached as below: > > > > 1. Builded the driver in 64 bit Vista build environment. > > 2. Taken AMD64 DPInst for pre installing. > > 3. Decorated manufacturer section of the inf file with nt.amd64 > > > > The drive package preinstalling is completing successfully. But when I > attach the device, the preinstalled driver is not getting loaded. > > > > Do I need to modify any other settings in the inf file. The following > statements from the setupapi.dev.log may be useful to analyze the actual > error: > > > > ================= > > setupapi.dev.log > > ================= > > > > flq : File ‘C:\Windows\system32\DRIVERS\hidusbosrfx2.sys’ pruned from > copy. > > cpy : DrpSetRegFileProt ‘C:\Windows\system32\DRIVERS\hidusbosrfx2.sys’ > Status=0 Class=OEM Legacy > > > > flq : File ‘C:\Windows\system32\DRIVERS\hidmapper.sys’ pruned from copy. > > cpy: DrpSetRegFileProt ‘C:\Windows\system32\DRIVERS\hidmapper.sys’ > Status=0 Class=OEM Legacy > > > > flq : File ‘C:\Windows\system32\WdfCoInstaller01005.dll’ pruned from > copy. > > cpy : DrpSetRegFileProt ‘C:\Windows\system32\WdfCoInstaller01005.dll’ > Status=0 Class=OEM Legacy > > > > Regards. > > > > — > 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 >