Jump to content
CCleaner Community Forums

rdsok

Members
  • Content Count

    7
  • Joined

  • Last visited

Community Reputation

0 Neutral

About rdsok

  • Rank
    Newbie
  1. Threatfire seems to be a good product but it is not an antivirus so its only a partial solution...
  2. The free versions of both AVG Antivirus ( Free ) and AVG Anti-Spyware get their updates from servers that do not have as much bandwidth as their Pro ( paid ) versions have... so they basically can get overloaded easier... Usually you can just wait a little while later and get updates without a problem.
  3. It's not that no one cares... its that you report/complaint leaves so much to be desired so it didn't deserve comment... like real information to base it on... For instance... a drive that is nearly full and doesn't have the room to completely defrag the fragmented files would explain the situation completely... As would the files that were left also happened to be files that were in use at the time... or that the files were other temp/log or other similar files that were started being created after the initial defrag was started.. and I'm sure of other possible reasons that aren't even covered in those few exist as well. Can you say what other defragmentation programs you have run and which ones were able to defrag the files in questions that you brought up? Without qualified comments ... the statements made so far just don't cover the possible issue at hand without additional info / comparisons. Rixtar has also brought up a very valid point... Vista, at this point in time could at worst be called a public beta release or at best a public release candidate... its far from being considered a stable OS at this time and has many issues to still be addressed. If past experiences mean anything, XP wasn't stabilized until well after a year after its release... it isn't even close to that time frame yet for Vista.
  4. rdsok

    CCleaner Portable

    HKCU\Software\Microsoft\Windows\ShellNoRoam\MUICache is a complex subject.. sort of. But none the less... having an entry in this key has nothing to do with CCleaner's ( or other program's ) settings per se or even it making the entry itself. MUICache is sort of like the MRU entires only for program files and dll's... only on steriods... lol. Its actually Windows itself that uses this area ( though a program can also make use of it in certain situations if needed ). MUI ... basically stands for multiple user interface. The MUIcache location then can keep track of language translations, selected icons that are shown for a program... or other info about a program file or dll such as just a location. Since this is done on a user by user basis... each user can have different languages, icons, values or or settings for the program. Just running a program can cause Windows itself to place an entry in this location and the program doesn't need to do anything itself.
  5. Simple, because things change faster than the documentation or announcements can be changed or updated... Sarcasm.... Why are users of a freeware product so critical about minor issues like this? Perhaps just pointing it out to the moderator ( s ) would be nicer than to critisize them.
  6. I've seen this behaviour on all systems that I've run CCleaner on... I don't believe its odd or unusual and I also believe that is simply caused when you remove invalid reference entries that other registry keys that used those then also become invalid. Basic simplified example... Registry key A has invalid entries in it pointing to now none existant registry keys, values or files etc... Registry key B has references to registry key A but since A currently exists... they are not yet invalid. You remove registry key A to resolve the issues it brings... now registry key B has references to a reg key that no longer exists... therefore it is now also invalid. I've seldom have to repeat my registry scans more than 3 times to get all issues resolved... at least not yet...
  7. rdsok

    SSDefrag service

    What Adder didn't mention and it is very important to understand is that in the scenario mentioned... UBCD4Win is based off of BartPE and PE environments do have some special requirements that must be met for any program to work properly on them. One of the general requirements is to understand that if a system is booted from a Windows based PE CD, that the system area's such as %Windir%\system32 and %Windir%\system32\drivers are not normally ( I'll get back to why I underlined "normally" later ) writable. A program such as Defraggler that uses being writable as a criteria to see if a user is an admin user, will fail ( normally ). So this is why Adder's statement about being able to be run from CD does have some merit. I still have some reservations about the statement "but obviously not with any help from this forum though" which shows a complete lack of respect for the others that do provide help on this forum. I do feel that statement was very uncalled for and I hope it won't reflect on the whole PE community because of this users lack of respect for what help is provided here. But, enough of that... The are several possible directions that could be taken to resolve this type of issue when addressing read only media like PE builds have. Some of the possible solutions that could be done from the program itself are... to not even require that a service and file be added, if they are required that they be added to a %TEMP% file location instead, to work with an existing SSDefrag.sys file if its on read only media... and I'm sure many other possible solutions that I am not able to come up with and will therefore leave to the programmers to come up with. I mentioned that normally there are issues with PE based CD's... There are also solutions available for BartPE builds that would allow Defraggler to be used now, just the way it is, but they do require additional requirements to be met. Specifically, to add another plugin to a users PE build called the FBWF plugin. This plugin requires the user to download the Microsoft's File Based Write Filter's files ( FBWF ) and add it's files to a simple plugin. This plugin allows a PE build to use read-only media as if it were read-write media by allocating some ram memory and then "faking" the writes virtually... It's not an elegant solution, but it works in many cases such as this one. Another issue with using this solution is that the FBWF files needed are not freely distributable by third parties, but still they are freely available from Microsoft... So it is already "do-able" but it takes some prerequisites be met to be able to have it work properly.
×
×
  • Create New...