Jump to content
CCleaner Community Forums


Experienced Members
  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Moonbase

  • Rank
  • Birthday 19/07/1959

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
    Kaufbeuren, Germany
  1. Well, he actually has a point: Many are out there actually having the extension ?.divx?. I seem to remember they recommended that a few years ago, and I actually also used it, for a while. (Before switching to .mkv containers.) Adding it might be no harm. Still it seems the zombies have gotten his Shift key, hee hee.
  2. Cheers for taking the time and effort to always keep us up-to-date, Winapp2.ini! Happy holidays everyone!
  3. Hee, hee. Indeed! Thanks for sharing your solution here for others to find!
  4. Maybe you could lend a spare drive from a friend (or another computer) to verify if the drive is defective? Sounds a bit like it. I also lately had an LG drive that suddenly wouldn?t burn CDs anymore (behaved normally, seemed to ?write? to the blank CD, gave error upon the following verify, using ImgBurn). It was actually the drive and I had to replace it. Another idea: Do you have DaemonTools or the like installed? I experienced problems with (older versions of the) the SPTD driver (SCSI-Pass-Thru-Driver) they install on some machines.
  5. Moonbase


    Good question, no good answer. Because one cannot know what might have messed it up. Maybe the devs can help. In the meantime, if you are a little computer-savvy, you might want to try checking the HKLM\Software\Microsoft\Wbem\Scripting key in your registry, using a tool like RegEdit. It usually (on WinXP) contains something like: (Standard) REG_SZ (no value) Default Impersonation Level REG_DWORD 0x00000003 (3) Default Namespace REG_SZ root\cimv2 These are the name, type, and value of the registry entries given. If your registry contains something else, let us know. If the key is completely empty and you feel sure about what you?re doing plus have made a backup, you might try adding the above three (or just correct a potentially wrong Default Namespace value), reboot your system and check if the error goes away. If above registry contents are as shown, there might be a problem with Speccy trying to access some piece of information that ?isn?t there?, for some reason. This can happen when installing/overwriting/updating/deinstalling drivers, for instance. Or using registry cleaning software ?just a bit too much? (i.e., having it ?clean? things you?re not 1000% sure about). In that case, try waiting for answer from the Speccy devs here: There might be some means to have Speccy output better diagnostic information (i.e., a log file). Again, if you don?t want to wait, you might try rebuilding the WMI database only if the above registry stuff is as mentioned. Doing this, I?d suggest the ?Method B? mentioned.
  6. Moonbase


    Looks like the namespace for a Windows Management Instrumentation call isn?t found (or corrupt). Accidentally modified/deleted HKLM\Software\Microsoft\Wbem\Scripting? (The default namespace is usually ?root\cimv2?.) Was something about ?SWbemLocator? mentioned in the error message you got? (Apparently Speccy tried to read out some information from the system using WMI, Microsoft?s implementation of the WBEM/CMI standard, which failed. WMI is used to as a more compatible means for (hardware) drivers to supply the OS (and applications like Speccy) with information about the hardware, and notifications.)
  7. Odd. Maybe Vista? FYI: Windows? Recycle Bin is physically kept on a ?per drive?-basis, while the desktop icon shows them ?all together?. On older FAT file systems, the folders were called RECYCLED (or Recycled), on NTFS file systems (NT, 2k, XP) RECYCLER. With the advent of Vista, MS decided to rename it yet again, to $RECYCLE.BIN (the internal format has also changed then). Same is still valid for Windows 7.
  8. Just a side remark (maybe off-topic ? if so, sorry!): You did try cleaning the SD cards connectors and/or did try another reader? I?ve had a similar problem once; fortunately, everything worked again after blowing out the camera?s card slot and cleaning the card?s contacts (carefully!). Phew. Just sometimes it?s only the contacts, or a defective card reader. If you?re lucky. To easily determine if your camera or card reader is broken, you can test with another (empty) card: Format it in the camera, take some dummy shots, and try reading those into your PC. If this fails, try swapping the card reader against another that you know works (lent from a friend maybe). If you?re a very knowledgeable Linux user (or know such a person), it might also be possible to copy the raw data off the card (using tools like dd and dd_rescue), and try restoring your files from the copy.
  9. ? or maybe you used Windows 7 just once on the drive(s) in question. I noticed the additional (hidden) $RECYCLE.BIN appearing on my portable USB drive after using it with Windows 7 for the first time. Now I have two Recycle Bins on it: RECYCLER (used by Windows XP) and $RECYCLE.BIN (used by Windows 7). I decided to just leave them as they are, because they?re empty anyway. I?m a notorious ?Empty Recycle Bin? fanboy, and always empty the Recycle Bin before removing the portable drive. The stored information would be of no use on another system anyway.
  10. Seems to work okay here (WinXP+SP3 German, avast! 5, Speccy 1.07.205 Portable): Operating System MS Windows XP Professional 32-bit SP3 Installation Date: 18 October 2010, 17:20 Serial Number: XXXXX-XXXXX-XXXXX-XXXXX-XXXXX Windows Security Center Firewall Enabled Antivirus Antivirus Enabled Company Name AVAST Software Display Name avast! Antivirus Product Version 5.0.83886757
  11. Just because I cannot readily find the info under "Recuva Features": Will Recuva work reliably when trying to recover accidentally deleted digital camera image files on an exFAT-formatted CompactFlash card? I.e., does it fully support exFAT? I would be using Recuva v1.38.0.504 under Windows XP+SP3, KB955704 installed. I?m asking this for a friend who is photographer and deleted some important images. Fortunately, he switched the camera off after recognizing his error, and immediately removed the card. We?re assuming exFAT, because the card is 64 GB and his card reader could read it only after installing the exFAT drivers on his system. (He lives about 500 miles away from me, so I can?t readily check myself. That?s why I?m asking before I recommend Recuva to him.) Has anyone tried that successfully (under XP, preferably with a CF card or other medium > 32 GB)? Thanks in advance!
  12. Hazelnut: No, I understand your point of view. I?d probably also be a little suspicious when a forum newbie came up with downloadable stuff in one of his first posts. Then again, I always somehow assume that everyone knows that I?m working with EDP (what nowadays is IT) since 1976 ? I was just assuming that someone (a mod) would have a quick peek over it, see it?s okay, and leave it. The main reasons for the ZIP were not to have a "clickable" (and thus executable) VBScript on the page, be sure that everyone could copy it over unmodified (copying from forum posts can be quite erroneous) not to clutter the thread ? in most forums it is not wanted to have extra-long posts, and actually often a "max. characters" counter in effect. I wasn?t aware that it is allowed here. Glad it seems sorted out now. Cheers to Winapp2.ini for taking the effort to put it all up here as a post. Phew! (Btw, the indentation has apparently been corrupted when copying it into the forum.) Now everybody can see how clumsy my code is, written kinda tounge-in-cheek. Aaargh! I apologize for the horrible typo in winsys2.ini. It should have been "This file and its contents", not "This file and it's contents". Aaargh again ? Oh well, the copyright. Also kinda "everyday" automatism, sorry. "I herewith grant free use of my posted code for everyone, especially CCleaner users and developers. This is valid for both private and commercial use. Do what you want with it, study it, encorporate it into your own software, throw it away, use it, whatever. Only don?t try to sell my work as your own. If incorporating the code into your own product, please at least mention my name somewhere in a "contributors" list ? thanks! And I can?t take any liability that the code and/or documentation are fit for use for any given purpose." Hope that?s good enough.
  13. Andavari: Good point. About in the Eighties, I swore never to touch BASIC again and, frankly, don?t like Microsoft?s BASIC variants at all, so I tend to forget about these things. So if CCleaner somehow executes wscript.exe (or whatever equivalent function) when encountering "ScriptKeyX" (instead of just hoping some kind of shell will do the job), Howard could still reach his goal this way. A little clumsy, perhaps, but possibly working. One might have to try this out.
  14. Cheers for the answer, Winapp2.ini! Up to (and including) Vista, the above should be sufficient and give usable results. The same holds for Win7 (as far as CSIDL goes), but from a programming point of view, I?d use an OS version check, and if we?re on Vista (or above), use KNOWNFOLDERIDs in addition, to get all the extra ones not (yet) addressed by my stuff, like, for instance LocalAppDataLow PhotoAlbums Ringtones PublicRingtones Games GameTasks RecordedTV RecordedTVLibrary SavedGames SavedSearches Just to mention a few right from the memory ? The only remaining (and increasingly important) point to address would be how to prevent CCleaner from actually using paths with EMPTY substitution, i.e., using a variable in winapp2.ini that returns an empty result (say, %LocalLowAppData% on Windows XP). If those got used, like in FileKey1=%LocalLowAppData%\MyApp\SomeStuff|*.*|RECURSE CCleaner might otherwise inappropriately return a path of \MyApp\SomeStuff\*.* which could lead to all sorts of odd errors, of course. Just imagine FileKey1=%LocalLowAppData%|*.*|RECURSE being "expanded" to \*.* Aaaaargh! Then again, I assume the programmers do variable substitution in some part of CCleaner and would be able to detect an empty value. And probably just not allow this to happen (say, by ignoring the path in this case, not doing anything on it, and continue with the next FileKey, if any). Oh well. 'Nuff said.
  • Create New...