140 replies to this topic

[Nergal]

pirat, on 28 October 2010 - 06:43 PM, said:

Please also offer embedded INIs in the latest CCleaner v3.00.1303
which i just downloaded as a .zip file!

Thanx in advance
pirat

Patience is a virtue, they will come.  Why do I have to tell you this every version ????    

[Aethec]

If you really want them, use Resource Hacker, Visual Studio, etc. to extract them

[MrT]

Hi there,

Please find attached copy of embedded INIs in CCleaner v3.00.1303.

Thanks

Attached Files

•  embedded_INIs_v3.00.zip   13.24K   145 downloads

[pirat]

Thank you very much for these latest INI files!

pirat

[MrT]

Hi there,

Please find attached copy of embedded INIs in CCleaner v3.01.1327.

Thanks

Attached Files

•  embedded_INIs_v3.01.zip   13.39K   115 downloads

[MrT]

Hi there,

Please find attached copy of embedded INIs in CCleaner v3.02.1343.

Thanks

Attached Files

•  embedded_INIs_v3.02.zip   13.8K   93 downloads

[pepe2]

MrT, I hate to rob you of the joy of posting this file every release, but seriously, if it is requested so often, why not add a command line switch like /dumpconfig or something so people who need it can do it themselves?

[MrT]

Thanks for the suggestion. I'll look into this!

[MrT]

Hi there,

Please find attached copy of embedded INIs in CCleaner v3.03.1366.

Thanks

Attached Files

•  embedded_INIs_v3.03.zip   14.4K   241 downloads

[MrT]

Hi there,

Please use command line to export embedded INI files.

ccleaner.exe /export [folder path]

Thanks

MrT

[Nergal]

Thanks MrT I've created a batch file to do just that

[bege]

MrT, on 24 February 2011 - 08:32 AM, said:

Hi there,

Please use command line to export embedded INI files.

ccleaner.exe /export [folder path]

Thanks

MrT

Hi,
that's a great idea. But in v305 there is no winapp.ini, only winsys.ini and winreg.ini! Please fix, thank you very much.

Regards

[Nergal]

bege, on 05 April 2011 - 04:29 AM, said:

Hi,
that's a great idea. But in v305 there is no winapp.ini, only winsys.ini and winreg.ini! Please fix, thank you very much.

Regards

I don't have this issue, Winapp.ini was created via export on both versions of 3.05 for me. Please try the export again (delete all non "2" win*.ini files first)

[Willy2]

Perhaps the Piriform folks can add the info for the Winapp2.ini file from this thread
http://forum.pirifor...?showtopic=1110

to the CC installation program as well. Not as an embedded file/info but in a seperate file that shows up in the installation folder after installation of CC. Then the user can choose which info he/she wants to add to his own Winapp2.ini file.

Edit: Has the thread mentioned above removed from the forum or don't  I have enough rights to access that page ? I thought it still would exist, I added that thread to my internet Favourites list.

[Winapp2.ini]

I don't have permission to view it neither, perhaps it's too good for us lowly peons

[Nergal]

Willy2, on 25 April 2011 - 12:05 PM, said:

Perhaps the Piriform folks can add the info for the Winapp2.ini file from this thread
http://forum.pirifor...?showtopic=1110

to the CC installation program as well. Not as an embedded file/info but in a seperate file that shows up in the installation folder after installation of CC. Then the user can choose which info he/she wants to add to his own Winapp2.ini file.

Edit: Has the thread mentioned above removed from the forum or don't  I have enough rights to access that page ? I thought it still would exist, I added that thread to my internet Favourites list.

That thread was hidden by it's author, we weren't able to discern why but it was, I think it happened about the time Winapp2.ini started maintaining his own version of the file. Which Information from it were you talking about adding? Most of what is there (entrywise) is already in the program or Winapp2

[Willy2]

Simply the entire content. According to my memory somewhere in that thread it was stated that a lot of info was removed from the embedded file/info because it negatively impacted the speed of CC. With that info the user can make his/her own customized Winapp2.ini and/or Winapp1.ini file. I certainly did.

Edited: I found where Winapp2.ini has stored the link to the updated Winapp2.ini file:
http://forum.piriform.com/index.php?showtopic=32310
I have added that link to my Piriform internet favourite links.

[Winapp2.ini]

I think when the name of the topic gets changed, it generates a new forum link or something, I've fixed it

[Nergal]

Yup, two seperate threads, the one you mentioned is the old Winapp2 thread, which is just (at the point that TwistedMetal Took it down) the tezt of the winapp2 and an empty winapp2 template

Quote

To learn about winapp2.ini or how to make program entries for CCleaner. Please read the Piriform Docs (Advanced Usage>CCleaner .INI files>How to add your own program for CCleaner to clean). Simply copy and paste the new entry in to winapp2.ini. Note: You will have problems cutting and pasting with Internet Explorer.

To report additions for current programs in winapp.ini send MrG a Personal Message.

DISCLAIMER

These entries are not supported by Piriform. These entries have not been tested by the maker of CCleaner. Use these at your own risk, these entries were created and tested by users of the CCleaner Forum. Piriform can not be held responsible for any action that these entries do. If you find a bad entry, please report it to me by Personal Message and I will look into the matter.

-----------------------
Updated 1/6/2010

Added blank winapp2.ini download
Added AOL AIM Messenger
Added Real Player SP
Updated Adobe Acrobat 7.0
Updated AVG AntiVirus 8.0

-----------------------

Listed in Alphabetical Order

After that it's just code (most of which as I said is already in the latest version of either .ini or the program)

[Keatah]

Perhaps we can simply have multiple levels of "WINAPP2.INI". What I mean by this is keep the current embedding as-is. Then we have the WINAPP2.INI "generated" by us forum users. Then why not have a WINAPP3.INI and a WINAPP4.INI file.. CC would first go to its internal definitions, then simple work through all the external WINAPP(X) files it finds.

This way we get the best of what the user community generates, and we can keep out custom entries totally separate and safe throughout upgrades to both CC's main program and the forum's WINAPP2.INI ..

Makes sense!