|18 Sep 2009||#1|
| || |
PeerBlock now has Signed Drivers!
PeerBlock r162 Interim Release - now with a signed driver!
Here it is: a signed-driver-containing PeerBlock 1.0 Release Candidate!
At this point we have pretty much all of the "showstopper" type bugs fixed, so think we're pretty much ready for an official 1.0 stable PeerBlock Public Release. However, we need your help! We'd obviously prefer for our 1.0 release to be truly stable, so if you encounter any problems with it please let us know. I've seen comments on various forums/review-sites in the format "I keep starting it but it won't start. FAIL!" - no additional info, no attempt to contact us about it, no nuthin'. This doesn't help anyone! If you're experiencing problems, PLEASE let us know about them . . . and if we have any followup questions please get us the extra information we're looking for. We actually try to be pretty good about addressing user issues, but we can't fix bugs we don't know about! And PeerBlock is running just fine on my machine...
So please, help us make PeerBlock better!
Okay, off my soapbox now. Don't forget that this release is an Interim Release, which means that it will check for new Interim Releases whenever it checks for updates. Depending on how this release goes, we may need to release another Release Candidate "Interim Release" before officially releasing a version 1.0 Public Release to the main Home (Peer Block) site. So you may get another update notice in a few days. Once we release 1.0 you can switch over from the Interim Release train to the Public Release one if you want to get updated versions less frequently; all you'll need to do is install a Public Release into the same directory in which you currently have PeerBlock installed and everything will work just fine.
I know, I know, there's a LOT of changes going on here, and there's probably no way you're going to read about 'em all. If you're going to just skim through them, you really should at least read the first four, and then you can skip down to the Known Issues section. I'll cry a little on the inside since I spent all this time writing up this big ol' changelist, but that's fine, I understand...
Here's what's different between the last Interim Release (r131) and this one:
The issue we're currently most concerned with is Issue 101, a problem with PeerBlock sometimes not exiting if you are running MS Outlook or the MS Live Mail desktop client. If you are running one of those two programs, I strongly recommend that you read the aforementioned bug, and check your current version of PeerBlock to see if the problem exists there. Not sure whether this bug was introduced recently or if it's a long-standing one, but the discovery of this issue yesterday is the reason we waited another day before releasing this Interim Release. Since it doesn't appear to show up on everyone's machines, even if they're running one of the aforementioned tools - including mine, which makes it more difficult to debug - we decided we're okay for now though we do want to resolve this prior to releasing 1.0.
Other than that, since the Installer for this version will not detect whether a pre-r162 PeerBlock is running or not, it is important that you make sure that PeerBlock is not running before installing this one. We needed to make this break at some point, and decided it's better to do it sooner rather than later.
Also please note that we're now displaying the first 9 or 10 allowed packets even if you have the "Show allowed connections" setting disabled. Especially since we're now defaulting this setting to disabled on new installs, we felt it was important to log something so that people (especially new users) don't end up with the mistaken impression that PeerBlock isn't working.
There is still an extremely rare bug that can cause PeerBlock to crash while it's downloading list updates, Issue 24. We'd patched around this a long time ago, but a very few people have seen it show up very rarely. There is an additional workaround possible, but it's going to require a nontrivial rework of our list-downloading code . . . and since this bug has only been seen very rarely, we don't want the cure to be worse than the disease. If you've seen this crash, please let us know - if it's more common than we currently believe we may change our opinion as to whether we should implement the new workaround before or after 1.0!
Get it Here
PeerBlock r162 Installer - This is the recommended download for most users.
PeerBlock "Portable" Packages:
|My System Specs|
|Similar help and support threads for2: PeerBlock now has Signed Drivers!|
|No signed device drivers were found||Installation & Setup|
|No signed device drivers were found||Drivers|
|No signed device drivers were found.||Installation & Setup|
|No signed drivers message||Installation & Setup|
|Can't find signed drivers?||Drivers|
|PeerBlock Now Has a Signed Driver||Software|
|Guide to Installing Un-Signed Drivers in Win 7 x64||Drivers|
|Our Sites ||Site Links ||About Us ||Find Us |
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.
© Designer Media Ltd
All times are GMT -5. The time now is 08:12 AM.