Unable to load driver, due to Windows driver-signing checking.

[GoogleCodeExporter]

What steps will reproduce the problem?

1. Attempt to run PeerBlock on a machine (Vista SP1+, Win 7) without having
first hit F8 during boot, or using "test-signing" mode (and disabling UAC)

What is the expected output? What do you see instead?

The program starts but then provides an error-window complaining about
"StartService" and error code 577.

Original issue reported on code.google.com by peerbloc...@gmail.com on 23 Jun 2009 at 2:37

[GoogleCodeExporter]

As of r34, the error-message should now explicitly state that you're having
driver-signing issues.  For new users, this should help point them in the right
direction.

Original comment by peerbloc...@gmail.com on 23 Jun 2009 at 2:39

[GoogleCodeExporter]

The REAL fix for this problem would of course be to sign our drivers.  The 
problem
is: a code-signing certificate costs a minimum of $180.  So until we're able to
generate enough revenue through donations or whatever, this ain't gonna get 
fixed.

Original comment by peerbloc...@gmail.com on 23 Jun 2009 at 2:40

[GoogleCodeExporter]

Issue 49 has been merged into this issue.

Original comment by peerbloc...@gmail.com on 10 Aug 2009 at 8:49

[GoogleCodeExporter]

Now that we've received enough donations, we just need to wait for all the 
paperwork 
to go through and we should be all set to buy a code-signing certificate and 
sign 
our driver.  Should be a week or two now.

Original comment by peerbloc...@gmail.com on 10 Aug 2009 at 8:56

• Changed title: Unable to load driver, due to Windows driver-signing checking.
• Added labels: Milestone-Release1.0, Priority-Critical
• Removed labels: Priority-Medium

[GoogleCodeExporter]

We now have our code-signing certificate, so all future releases will be 
signed.  For
at least a year, anyways, after which point we'll need to buy another one.

Original comment by peerbloc...@gmail.com on 14 Sep 2009 at 2:54

• Changed state: Fixed