New
#1
Unsigned drivers questions on 64-bit Windows 7?
Hello everyone:
This is my first post on the Windows 7 forums.
I currently have an old P4 running 32-bit Windows 7 RC. I don’t think I can put 64-bit on that machine, but I am considering 64-bit on the retail version when it is released in October. I tested about thirty 32-bit shareware and freeware applications on 32-bit Windows 7 RC and they all work well.
My questions concern 32-bit drivers and unsigned 32-bit and 64-bit drivers on Windows 7 64-bit retail.
I have seen references to a BCedit command. I ran Bcdedit /set Bcdedit nointegritychecks ON on my Vista SP2 machine and it ran successfully. I have not tested what it will let me do as I now have no Vista driver issues.
Here are my questions:
Which of these is the correct command to disable the signature check on Windows 7 RC?
bcdedit /set loadoptions DISABLE_INTEGRITY_CHECKS
bcedit –SET TESTSIGN NO
Is there any reason to use the correct command rather than using F8 during the boot process?
Does the correct command work for both unsigned 32-bit and unsigned 64-bit drivers on a 64-bit Windows 7 system?
Is the correct command useful on both 32-bit and 64-bit Windows 7 for driver signing issues generally?
I assume the command works for only 1 boot cycle. Given that, is there any reason to run a command to re-enable the driver signing check if one reboots again after the driver installation?
Is there any other solution other than third party software, which I would prefer to avoid as I don’t expect to run into a driver issue frequently?
What is a decent estimate of how many of my 32-bit applications that work well on 32-bit Vista SP2 will install and work well on 64-bit Windows 7 retail, assuming I use the correct command to disable the signature check?
Thanks for any responses.