You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey now,
I really appreciate you making this driver. I am running 64 bit Vista home
and using the PC mainly to watch movies on my tv - so the surround sound
over optical was very important to me.
The only issue I've had is that even though I run the "bcdedit.exe -set
loadoptions DDISABLE_INTEGRITY_CHECKS" command, the only way to get the
sound working is to hold F8 and disable the driver protection on every
bootup. Is there something I'm doing wrong or another method to fix this?
Thanks for any help. You can email me back at jstraw@gmail.com
Also - I didn't see my sound card on the supported list. I can confirm the
Diablotek 7.1 Tremor sound card works with these drivers. i bought it from
compusa for $15 after rebate.
http://www.compusa.com/applications/searchtools/item-details.asp?EdpNo=3180419&C
MP=EMC-COMPUSA-TEMAIL&SRCCODE=WEDBBLET
Original issue reported on code.google.com by jst...@gmail.com on 10 Feb 2008 at 8:10
The text was updated successfully, but these errors were encountered:
Hi,
this annoyance is caused by changes in ntoskrnl.exe which have found their way
into
your system through windows update. The switch described in the FAQ doesn't
work
anymore to the effect that there's no way to permanently disable the enforced
driver
signing.
There are sadly only two ways out of the misery:
1. Either enough customers complain about this at Microsoft's service and they
decide to re-enable the switch,
2. or someone buckles up a larger sum of money for a certificate and signs this
driver.
The strict enforcement of driver signing doesn't inherently create better
drivers or
a more secure system, so I fail to see the necessity of it.
Thanks for the link to the Diablotek card, I'll add it to the list of supported
devices.
Original comment by dogb...@gmail.com on 11 Feb 2008 at 6:28
Original issue reported on code.google.com by
jst...@gmail.com
on 10 Feb 2008 at 8:10The text was updated successfully, but these errors were encountered: