Jump to content

TheOdds

Experienced Members
  • Posts

    72
  • Joined

  • Last visited

Posts posted by TheOdds

  1. The same installer you state I think is Nullsoft Scriptable Install System ("NSIS") which recently allot of virus scanners started giving false positives against. Then again it's like the old problem when some virus scanners detect all UPX compressed files as viruses even though they're clean.

     

    Yes apparently some virus writes wrote viruses what used NSIS component's or source code. As result pretty much every AV in the market started to detect literally tens of thousands NSIS installers as viruses. The biggest AV companys are aware of the problem and doesn't cause much NSIS false positeves anymore, but the smaller AV companys (mainly free AVs) are still producing "tons" of NSIS false positives.

     

    As personal opinion I would ditch any AV what still is producing these false positives.

  2. Portable app only uses one ini. CCPortable.ini should be portable.ini and if the readme "talks" about CCPortable.ini it means portable.ini. Rename the CCPortable.ini to portable.ini or delete it. :)

     

    When NoAppSettings=1 the so called "(app)" settings are not used and CCleaner will use the default "(app)" settings each time it starts.

     

    The value of Language setting is the language identifier (the number in the lang-????.dll file) Though the portable distribution only comes with English.

     

    Those 4 additional ini files are all for CCleaner. ;)

     

    Edit:

    When LocalSettings=1 the portable app will create a own sections in the portable.ini file for each computer.

  3. Actually... Partly yes, you could simply edit CCleaner ini files (winapp.ini, winapp2.ini and winsys.ini) and change all %something% paths to corresponding paths in hdd and change the Detect keys so that CCleaner could find the things on hdd.

    Example: replace all %ProgramFiles% with "C:\Program Files" assuming that "C:\Program Files" is your program files directory. :)

     

    But I don't recommend that you actually do this, the "WARNING - DO NOT EDIT THIS FILE" in the beginning of each CCleaner ini file is there for good reason. And it would only work with small amount of things CCleaner can clean so I don't think it would be worth to do anyway.

  4. If you boot your windows from hard drive of the computer and then run the portable CCleaner from usb or CD/DVD it can clean the booted windows and the applications installed in it.

     

    If you boot your windows from DVD/CD and then run the portable CCleaner from that DVD/CD it can clean the booted windows and the applications installed in it.

     

    And if I have understood you right, you are trying to do this.

    You boot your windows from DVD/CD of the computer and then run portable CCleaner from that DVD/CD and try to clean windows and applications installed on the hard drive.

     

    So actually when you run portable CCleaner in ubcd4win it is working just the way it should work when it trys to clean the windows and the applications on that DVD.

  5. The result of those commands are:

     

    %tmp% =B:

    %windir% =X:\i386

    %appdata% =B:\UBCD4Win User Settings\Administrator\Application Data

    %ProgramFiles% =X:\Programs

     

    which is correct for the DVD, but not for CCleaner I suspect!!?

     

    Yes and I quess that B: drive is a ram drive or a virtual drive what ubcd4win created. The problem is that CCleaner doesn't support this kind of cleaning because CCleaner is a "system" cleaner which means that it can only clean the system it is running from and the applications installed on that system. So if the system is runing from DVD...

  6. :rolleyes: Try this open command prompt and run these commands:

    echo %tmp%

    echo %windir%

    echo %appdata%

    echo %ProgramFiles%

     

    Does all or some of the paths it prints point to the DVD?

  7. I am looking very old CCleaner versions. The older the better... No I am not feeling nostalgic. I need them to test new function for CCleaner Portable. :)

     

    ps. I already have every version from oldversion.com so older than v1.16.082 please.

  8. Sorry I can't help you. I can't reproduce the problem. Everything works just like it should when I run it from CD so I really can't tell how you end up with this "but it only scans the content of the cd" conclusion, unless you can explain it to me... And you don't need to be programmer to do that.

     

    The only thing I can think of is that you are missing some of the CCleaner files (the ini files particularly). Make sure that at least these files are in the same directory with the portable exe.

     

    winapp.ini

    winreg.ini

    winsys.ini

    CCHelper.ocx

    ccleaner.dll

    ccleaner.exe

    CCListBar.ocx

    CCListView.ocx

    CCSubTimer.dll

    CCSystem.dll

    CCTab.ocx

    CCTreeView.ocx

    lang-1033.dll

  9. Hi, I like this tool and it runs "just fine" on cd but...

    but it only scans the content of the cd, could you make it able to scan a remote drive?

    I would like to add this to my ubcd4win cd.

    Thanks. :D

     

    Really. :huh: What exactly is the problem? In my tests everything works just fine regardless of the drive it's running from (usb drive, CD, network drive).

     

    Though I am aware of one problem relating to the CD autorun, but in that case CCleaner doesn't even start because the portable app is stuck in loop.

     

     

    Hi,

     

    thanks for this great portable!

    I have one question though, is it possible to let it run even when CCleaner is installed on the system?

    I think this would be possible by bypassing the registry keys be?ng added and just starting the .exe

     

    can anybody please comment on this and possibly what changes need to be made to the .nsi

    thanks in advance!

     

    Well you could just run the portable app with /NOIC command line parameter to skip the installation check, but after that the installed CCleaner won't work.

     

    Better idea would be to just run the ccleaner.exe like you said, but this could lead to problems if the installed CCleaner isn't the same version as the CCleaner with the portable app. Perhaps better idea would be to run the installed ccleaner.exe when it's detected, but this method isn't perfect either.

     

     

    Here's the changes you need to do in the code to just run the ccleaner.exe when CCleaner is installed.

     

    To run the ccleaner.exe with the portable app. Replace the piece code in CCPortable.nsi about line 115 with this code...

      CCInstalled:;!ifdef SUPPORT_CMDLINE;	StrCmp ${frce} "1" instwarn;!endifMessageBox MB_ICONQUESTION|MB_YESNO "CCleaner is installed. Run anyway?" IDNO +2  Exec '"$INSTDIR\${CCLEANER_EXE}"${cccmd}'Abort notinstalled:

     

    And if you want to run the installed ccleaner.exe replace the piece code in CCPortable.nsi about line 99 with this code...

      ReadRegStr $R1 HKCR "CCSubTimer.CTimer" "" StrCmp $R1 "CCSubTimer.CTimer" CCInstalled 0

    And piece code in CCPortable.nsi about line 115 with this code...

      CCInstalled:;!ifdef SUPPORT_CMDLINE;	StrCmp ${frce} "1" instwarn;!endifMessageBox MB_ICONQUESTION|MB_YESNO "CCleaner is installed. Run installed CCleaner?" IDNO +2  Exec '"$R0\${CCLEANER_EXE}"${cccmd}'Abort notinstalled:

    Edit: No need to ExecWait :)

  10. Just trying to figure out what happened.

     

    Ok let's try this. I asume you haven't installed CCleaner after the incident. If so CCleaner setting probably still are in windows registry untouched, could post those settings here.

     

    If you don't know how to do it...

    1. Click Start, click Run, type regedit in the Open box, and then click OK.
    2. Locate the following registry key: HKEY_CURRENT_USER\Software\VB and VBA Program Settings\CCleaner\Options
    3. Click the Options key, and then click Export Registry File on the Registry menu.
    4. Enter a name and location for the saved registry file, and then click Save. (After that you can delete the CCleaner key if you want.)
    5. Attach the the registry file you saved to your reply.
  11. say or believe what you want.

    Same goes to you pal.

     

    I am a super fan of CCleaner. The files were SHOWN as being deleted by CCleaner on Norton GoBack (each file shows what deleted it, each file said CCleaner).

    I have never heard of Norton GoBack before, but if it can show the files what CCleaner deleted, could you post a screenshot what show some of those files or even better if Norton GoBack keeps logs post a full log what show all the files. It could help to explain what vent wrong.

  12. 2) It's somewhat normal and many other reg cleaners works the same way. I'll try to explain why.

     

    Example: removing broken file associations often needs 2-3 scans before it's really entirely removed this is because file associations haves several keys/vales in the registry so when CCleaner removes one invalid reg key/value relating to file association the other keys/values what points to the key/value what CCleaner removed comes invalid.

     

    CCleaner could use better of dependency check between the reg keys/values so it could remove all the keys/values at once, but I don't think it's very good idea because many reg keys/values are "common" so such check could easily also remove unintentional keys/values.

     

    I much rather scan my system couple times than let the program try to remove all at once. :)

  13. I'm testing CCleaner Portable (the version from Twisted Metal, but I've tested the other one too and the result is similar) and can't launch it.
    Well that is expected since the only difference between them is the name. :P

     

    When I try, I get this error message :

     

    Registring: CCHelper.ocx Failed!

    My guess would be that you don't have "install" privileges. Install privileges are needed for component registering. In XP home this means that you have to be an loggen on as administrator.

     

    But if this is not the case, could you run the CCleaner portable in debug mode (Run the portable executable with /PDEBUG parameter or add DebugMode=1 under [PORTABLE] section in the INI file). This gives you more detailed errors in the debug log. :)

     

    If you just get...

    ...

    Registering CCleaner components...

    Registering: CCHelper.ocx

    The problem is the install privileges. :(
  14. As you may know CCleaner Portable is now build out of CCPortable source code and me and TwistedMetal are working on the portable version together. So now on I will only only distribute the source code along precompiled bins. If you want ready to run version with latest CCleaner you should download the "official" CCleaner Portable distribution.

     

    If you have any questions ideas or you found a bug, you can post them here or just PM me or TwistedMetal. :)

     

    As a side news...

    CCleaner v2.0 is now being planned and worked on. We're going for a semi-complete rewrite in C++, to allow unicode, 64bit and thumbdrive support.

    It looks like CCleaner v2.0 is going to be portable. :)

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.