Comodo Boclean will be available for Free very soon.

[Guest]

[foxman]

sound great! seems like I can finally dispose of Spyware Terminator (good stuff though!)... or can I? but then CPF + CASV already using >90MB RAM, how much more will BOClean use?     Guess my 320MB T60 notebook won't be able to use them all.. 

[Soyabeaner]

how much more will BOClean use?

Currently, it occupies about 8,000K memory + 1,000K for the core service = 9,000K total.  Definitely lighter than the other listed apps.

[dadkins]

10,856K(total) is being used by BOClean here currently.

[twl845]

10 mb isn't bad. I doubt if it uses any real amount of RAM right?
Here's a thought. How about posting the operating instructions in advance of the big announcement, so everyone can be ready to just dive in when they install it? 

[Soyabeaner]

Ok.

Step 1: Install BOClean.

End of tutorial .  It does its job on startup..

Edit: There's an optional Step 1a: drag and drop a suspicious file into the GUI to let it scan it.

[twl845]

Way cool!   

[Hamo Sopien]

will this new version of BoClean be fully compatible with Vista,
there are a couple of niggling things with the current version that I think were being worked on prior to the sale to comodo

[JolietJake]

will this new version of BoClean be fully compatible with Vista,
there are a couple of niggling things with the current version that I think were being worked on prior to the sale to comodo

They're working on a BOclean that is Vista compatible.

[JWill]

I'm using BOClean with Vista Home Premium.
The only thing is with the UAC turned on BC keeps popping up telling you it is trying to update.
Other than that I have no problems with BC and I keep the UAC turned off

[Rednose]

Very interesting news 

Greetz, Red.

[Kevin McAleavey]

Long story short, when BOClean 4.22 was released PRIOR to Vista's actual release, certain things in the RTM and betas worked just fine. Somehow when the actual "doesn't expire on April 1" Vista came out, things changed. Because of where BOClean has to assert itself in the system, certificates were required as well as a special "CROSS certification" and that didn't exist in BOClean 4.22 nor could we actually AFFORD the "blood money" ... COMODO has gotten the paperwork together with Redmond and this was the ONLY cause for the Vista incompatiblities. We even had the proper 64 bit driver stuff already built in but Vista went and hosed it all.

 The ACTUAL problem people had complained about with "File missing" errors was the result of UAC in Vista deciding to put up an incorrect error message. The file was THERE, but Vista didn't want to run it as a "child process" and instead of an "access denied" or other useful message, decided that it just couldn't find the file when everyone else had no problem finding it.   

 But HAVING "ze papers" allows us to now get past the border guards and onto the plane. Heh.

[CajunTek]

Just curious here.. When is soon... My teeth are aching from the clinching... Here I was attempting to buy BOClean on the very day the sale went through.. and I couldn't... Now I'm stuck waiting.... Especially with this bad boy being out there:
C:\WINDOWS\system32\ntos.exe

Hurry up guys!!!!!!  (J)

[Kevin McAleavey]

As I've said too many times in my own engineering life ... "do you want it NOW, or do you want it *RIGHT?* Choose." As I've said elsewhere, maintaining the quality of keeping up with malware for our already-existing customers has been the HIGHEST priority and even there, it's been incredibly difficult with Microsoft's ... umm ... umm ... (ahem!) "security." Coding up the 4.23 has had to take a back burner to this necessary stuff. Been working on it, have a number of things migrated but there's a lot of other things still to be done as far as BUILDING the code and getting it done.

Once that's done, then begins our own internal testing with machines built to replicate some really off the wall conflicts we've seen before. After that, then some serious beating up of the code and then handing off to others I already know who will do a GENUINE "beating up" of the code - "beta testing" is something we never did as PSC - most folks just want a toy and don't give it a truly serious beating the way my own folks do. And I don't like to release "hoseware" and have to go and put everyone through a "oh well, that one's no good, come and get a replacement replacement." Anyone who's been with us for a while knows that's happened with pretty much every release we've ever done - some stupid little thing that gets one or two people twitchy and everyone needs to uninstall and reinstall. Reliabilty and "it's REALLY done" has to be a priority and thus the delay.

 There's a LOT of pressure to "get it out" ... I'm RESISTING that ... "get it out" sure ... but get it out RIGHT. Hang in there, won't be much longer - I'll ring the soup bell when it's ready and has actually boiled. 

[CajunTek]

Oh, I understand (Of course I could care less it it's Vista compatible  )... but of course I want it right!!

Keep doin what ya do....

[panic]

As I've said too many times in my own engineering life ... "do you want it NOW, or do you want it *RIGHT?* Choose."

Way to got Kevin!

The Nike approach (Just do it) usually turns to the Nookie approach (Just did it - and look at the mess it left behind). I'd rather have software that is two weeks behind a published schedule than software that is released but two weeks ahead of development. 

Quality doesn't cost - it pays!

Cheers,
Ewen :-)

[Tags:]