- This topic has 16 replies, 7 voices, and was last updated 11 years ago by
.
-
Posts
-
The Trim.bat file you’re referring to is not developed or maintained by SingularLabs. You should direct your queries to the author, alan_b.
For some reason the TRIM functionality is removing my custom entries.
[User Local Files*]
LangSecRef=3025
Default=False
FileKey1=%LocalAppData%\temp|*.*|RECURSE
DetectOS=6.0|6.1|6.2|6.3That’s my custom entry. I don’t see why the TRIM functionality would remove it.
Nope, I checked for that rule and it’s not in there. Hence the reason for a custom rule.
‘DetectOS’ without a standard ‘Detect’ line following will cause it to be trimmed.
I’ll get this fixed in the next version. In the meantime, something like ‘Detect=C:\Windows’ will do the trick.
Hi Shane, i’ve compared CCEnhancer trim vs trim.bat by alan_b and ccenhancer have fewer entries than trim.bat
a few question regarding the trim
does it support “Detect1″/”Detect2” etc?
does it remove entries with valid “Detect” but nothing to delete?
test with installed chrome, all chrome winapp2 entries removed
test with firefox portable, profile location inserted into ccleaner.ini and edit winapp2.ini entries to follow the profile location, all entries detectedhere some of what i found from the comparison that i think need more explanation
the entries here are some of the missing entries after the trim
at the end of the list, there are 3 entries that should not be detected/included after the trim
I would strongly recommend using trim.bat until I have a chance to update all of my winapp2.ini related code.
does it support “Detect1″/”Detect2″ etc?
It will only check the first Detect.
does it remove entries with valid “Detect” but nothing to delete?
No, it doesn’t parse the FileKey lines at all.
test with installed chrome, all chrome winapp2 entries removed
SPECIAL_DETECT_CHROME is not supported, however Opera (pre-chromium), Firefox and Thunderbird are.
- You must be logged in to reply to this topic.