To have CCleaner clean up HostsServer log file the following winapp2.ini file has to be added to CCleaner's program Folder that is typically in C:\Program Files\CCleaner

Thanks YoKenny.

Is there a reason that you did not include block1.log for cleaning as well?

I don't have a block1.log on my WinXP Home SP2 system :unsure:

When the size of block2.log is around 256kb, it's renamed to block1.log and a new block2.log is created. It seems you clear the log before the block2.log reaches 256kb of size. :)

To clean out both logs then the code should be

but as I have never seen a block1.log file on my system then this should work but let me know if it does not.

Thanks, it works. :)

I'll probably never again see a Block1.log because I run CC frequently.

BTW, CCleaner V2.00.500 has been publicly released.

Thanks.

I saw it announced on Calendar of Updates as well.

Hey guys,

Doesn't Clear log work too in HostSever Control Panel?

I see block1 in Vista at: C:\Users\Hardhead\AppData\Roaming\abelhadigital.com\HostsServer

It sure does but I thought that as CCleaner cleans a bunch of stuff then why couldn't it also clean out HostsServer logs as well.

Cool, thanks - send a request to have it added to the 'official-non-official' winapp2 file on the CCleaner forum ;)

I think I did but another request for it to be added would help and you should include the Code snipit B)

Okay, I just didn't find it added to the list on the CCleaner forum - don't know why if you already send it to them. But let's see what happens...

I thought I would resurect this topic as I needed to install it on my newly FORTMATed WinXP Home system and the topic was way down the list.

Hopefully it will be within the soon to be announced CCleaner update.

For Version 3.2.61 Beta1, winapp2.ini needs to changed to:

The latest update for winapp2.ini now includes the needed modifications:
http://forum.piriform.com/index.php?showtopic=1110

BTW, CCleaner V2.07.575 has been publicly released.

Actually, since 3.2.61, the most effective way of detecting HostsMan is by checking the presence of the following registry key:

This way, even if users install to a different location, it's still possible to detect HostsMan.