Greetings all, have spent a few hours playing with my various Win95, Win98 and ME boxes at home, and there’s absolutely nothing wrong with 4.24 as long as it was downloaded from either the www.nsclean.com page or the COMODO page - the install and uninstall works perfectly whether done from the COMODO programs group or the add/remove programs in control panel and thus I’m really at a loss to explain how there would have been any difficulties there at all. 4.23 had the uninstall for control panel pointing to the wrong file and so that didn’t work, but could still be removed just fine from the COMODO group in the programs listing on the start menu.
As far as any lockups go, there have been absolutely no changes to the code in 4.24 from the 4.22 version as far as Win9x goes - no changes. So it looks like what we have here unfortunately is a “last program installed gets the blame” issue. 
Now to be fair, BOClean 4.22 has been around for a while and some “security programs” do some dumb things in blocking or hosing other “unknown” software (folks are used to their firewall complaining that a program is different from what was in there but many other security programs and AV’s don’t say a word, they just block things) … I have to guess that this is the actual problem here, so for you two, the question is going to need to be finding out what you two have in common as far as AV, firewall or any other “protection” proggies … somewhere, there’s got to be a common denominator.
As I explained in a previous, Win9x is kinda flaky and BOClean has been around since before Win98. That’s why there’s still support for those in there all along. But because large portions of memory where bad things can hide are not properly protected when some programs are running, a hang is possible in the presence of other “fat” programs if Win9x decides to put it in a bad place. But for the few programs this has happened to, excluding them once all are found, usually stops that. But even still, Win9x can lose its brains every now and then as well when Win9x decides to “relocate code” … that’s the actual cause behind it and sadly, as the number of malwares increases, BOClean requires more memory itself despite our efforts to keep it as slim and trim as possible.
I won’t be around on Sunday, going to pipe on board a Naval vessel for the day but will be back to pick up on this Monday … but once again, the install/uninstall is confirmed to be working properly, and for those rare instances where something doesn’t get along with BOClean - excluding it solves the problem. What I suspect is going on here is that some AV or other “security program” needs to exclude BOClean. We went through that years ago with NOD32 and they fixed it owing to all the complaints. It’s probably something along those lines once again because BOClean has changed.
Finally, BOClean 4.22 is going to end very soon - somewhere in the vicinity of 30,000 “uniques” in the nasty count as it will run out of memory allocation somewhere past that point. And 4.24 is the SAME as 4.22 as far as Win9x systems will see it. All of the changes which remain in 4.24 were made to keep Win2000, WinXP and Vista happy. All of the code is internally compartmentalized so those changes will never be seen by Win9x when BOClean runs …