A new BOClean 4.24 version is nearing completion. We hope to have it done by the end of next week, but lessons have been learned from the premature release of 4.23 and thus I’m not making any promises at this time. My reasons for posting this however are to explain what happened with 4.23 as well as to solicit some assistance in the coming days from those who have had problems with 4.23 so we can make sure that any of those problems which arose from our code will be fixed and those that arose as a result in other vendors’ software can be identified and worked around.
Those of you who are used to BOClean from its original source, Privacy Software Corp, know the attention to detail and compatibility we offered and we’ve encouraged those who already owned BOClean to stick with the 4.22 version as 4.23 wasn’t quite right. When 4.24 is released, we will strongly urge those running the earlier BOCleans to finally upgrade as the 4.22 version will become obsolete a few weeks after 4.24 is released and “proven effective.” 
BOClean began back in the days of Windows95 and NT4 and was always compatible with the earlier versions of Windows. As each new “next version of Windows will be better than ever” was released, BOClean had compatibility with each new version of Windows added to its design as expected. The 4.22 version was compatible with Vista during the final release candidate versions as well, however the ACTUAL Vista release was not quite the same as the pre-release versions.
BOClean 4.23 was released prematurely as a result of a great deal of pressure exerted by folks demanding their “free BOClean” and in doing so, completely broke compatibility with earlier versions of Windows as a result of code which was added by COMODO to provide activation of the licence as well as some additional code required which was written in Microsoft MFC code. BOClean on the other hand has always been written in BORLAND C and the two compilers produce incompatible output. Once the Microsoft code was mixed with the BORLAND code, compatibility with earlier versions of Windows was literally trashed. Microsoft and their design of their compiler was the cause of this since Microsoft’s compiler honors the concept of “obsolete version of Windows” and generates code specifically for their later versions of Windows. That was the cause of so many problems between the “Win9x not supported” and some truly oddball unique problems caused by the mixed code fighting.
Folks will be pleased to know that I obtained COMODO’s source code for the required items and have redone that code. As a result, BOClean 4.24 will continue the tradition of true “cross platform” compatibility for users of earlier versions of Windows all the way back to Win95 as has always been expected of BOClean. In addition, new code has been written which will get around the absolute stupidity of Vista’s UAC and its inability to determine “friend or foe” effectively. Microsoft claims that the upcoming “Service pack 1” this fall will solve many of these issues but then we all know that we have to wait for “Service pack TWO” for those promises to be kept. Heh.
Soooooo … when 4.24 is released, the world should be happy again and those incompatibilities should be a thing of the past as a result of replacing COMODO’s original “W2K/XP only” code with code designed for all versions. Win95, Win98, Win98SE, WinME, NT4 (all SP’s), Win2000, XP and Vista will be working. Under Vista, the AUTOUPDATE will work without tripping UAC however any MANUAL updating will require the usual UAC and that’s because of the need to connect out to collect it. Microsoft offers absolutely no way around this even with signed code. So you’ll want to set the autoupdate if you use Vista and all should be well. Therefore, if you’ve experienced any problems with 4.23 or it wouldn’t install, hang on another week or so and 4.24 will be yours.
Now … there are a few situations I’ve seen reported that I’d also like to deal with and will need YOUR help to get there. I’ve seen a few really odd problems reported that are not part of the incompatiblities of the “mixed code” and were not normal for BOClean. This tells me that there is some other software out there which is either “broken” or doing some really dumb things and I’d like to see what we can do to prevent those from happening if it’s at all possible.
Therefore, if you’ve had ANY of these symptoms, I’ll want to know who you are so I can have you run some special diagnostics so I can identify the source of the problem. The ones I want to know about are as follows:
- Lost winsock connectivity
- Failure of update to “stick” after successful download
- Windows belonging to BOClean that don’t go away
There might be other anomolies - we expect ALL of these to actually be caused by other vendors’ software - a lot of vendors expect to be the “only program you’ll ever need” and don’t play well with others. I want to try to do what we can about those.
Thus, if you’re in a situation such as above, you’re invited to let me know in this thread about it and once I have the diagnostics stuff written (once I see what I need to go after) I will contact you and let you know where to collect it, how to use it, and get me back a report so I can figure out what the culprits are. Hopefully for the 4.23 release, I can find a workaround. I’m particularly interested in those who have had “lost connectivity” so that can be programmed around.
Finally, NO FEATURE REQUESTS PLEASE! We’re not planning on adding any new features in 4.24 … we’re looking for stability and reliability here. Once this is done, work will commence on a BOClean 5 version which will entertain “bloat” and will ONLY work on Win2000/XP/Vista. The 5 version will not support older Windows versions. As far as I know, we’re going to continue the “4” versions after 4.24 for those using older versions but might consider making that a Win9x-ONLY version. At this time, there’s been way too much work to worry about anything beyond getting 4.24 happy as people have always expected of BOClean and thus my inability at this time to worry about trivia …
Just wanted to let everyone know where things stand and offer a “definitive answer” as best as time permits right now …