Jump to content
CCleaner Community Forums

SeanC

Members
  • Content Count

    8
  • Joined

  • Last visited

Community Reputation

0 Neutral

About SeanC

  • Rank
    Newbie
  1. If you have less than 256MB of RAM and you're running XP, defragging your pagefile to improve performance is next to pointless. Go out and get more RAM.
  2. For optimum disk defragging, I first delete pagefile.sys by turning off virtual memory entirely (Control Panel > System > Advanced > Performance Settings > Advanced > Virtual memory > Change, choose "No paging file" then click "Set"). I then run CCleaner as well as manually delete other unneeded files, etc. as necessary before defragging. If you've enabled hibernation, you should disable it prior to defragging as well (Control Panel > Power Options > Hibernate). When defrag is complete, you can turn virtual memory back on (and hibernation if you use it). A note on virtual memory... I set my pagefile to 2048MB (same value for both min and max). The recommended setting is 1.5x physical memory for minimum and 3x for maximum, but since I have 1GB of RAM and lots of free diskspace, I simply set both values to 2x. Should my system ever need the virtual memory, there it is, but it probably won't, and since the size is fixed, pagefile.sys won't become fragmented. Works for me.
  3. My first reaction: If someone is reckless enough to make such a puposefully intentioned mistake (as opposed to an honest, easy or simple mistake, which this most certainly isn't), they should have their important documents or, using the above example, their WINDOWS directory, destroyed. It is their destiny. The universe itself deems their impending tragedy necessary. Otherwise, how are they ever going to learn not to make mistakes of this magnitude in the future? "I'll never stick my hand in a lion's cage again," said he, offhandedly.... And: Isn't this really an issue for the Windows OS? I mean, it shouldn't let you set a TEMP variable to a decidedly permanent or otherwise non-temporary directory, e.g., My Documents, C:\WINDOWS, etc. I'm surprised it doesn't offer some form of warning or guidance in this regard. And if other programs really are changing this variable (I've never before heard of such a thing...) these programs need to be identified so their authors can be publicly flogged. Lastly, such a scenario could be easily addressed in the ReadMe, something along the lines of, "Be aware that this utility purges the contents of your TEMP directory should you instruct it to do so. If you've changed the TEMP variable to a folder containing non-temporary documents and files, CCleaner will permanently delete these files along with the temporary ones. Further, if you have changed the TEMP variable to a location containing important files and documents, perhaps you should pause and reflect upon your decision to use potentially destructive file and system utilities, be it CCleaner or others, at all."
  4. My gut tells me this is a corrupt Fonts folder (or corrupt screen font) that can be repaired with FiFoFo, but if not, can you post your findings and solutions here? I sorta keep a database of font-related problems and workarounds, and would be very interested in knowing the exact nature of this one. Thanks.
  5. I'd suggest downloading the Tweak UI PowerToy from Microsoft here: http://www.microsoft.com/windowsxp/downloa...ppowertoys.mspx After you install it, choose the "Repair" option, then choose "Repair Font Folder" from the drop-down list and click the "Repair Now" button. If that doesn't correct your problem, you might want to try High-Logic's "FiFoFo" (Fix Fonts Folder), which you can download here: http://www.high-logic.com/fifofo.zip Unzip and run the exe (there is no setup, nor does the app have to be installed anywhere special). Click the "Fix Fonts Folder" button, and FiFoFo will analyze it. Any font registry problems will be listed at the top of the results. Select them, then click "Repair Items." If FiFoFo can fix them, it will. Then click the "Rebuild Cache" button and restart your system. If neither of the above correct the problem, you may have to reinstall the fontext.dll file. For instructions on how to do this, click the "Read Me" button in FiFoFo. - Sean
  6. Here are some suggestions (in descending order) of features I'd love to have in CCleaner: - An checkbox in CCleaner's "Cookies to Delete" list to add the deleted cookies to Firefox's and IE's Block Lists (a la Spyware Blaster), with a "Select All" option at the top of the list. - A browser plug-in for IE and Mozilla that deleted any cookies not in the "Cookies to Keep" list upon exiting the browser. - Ability to add file types to the list of Custom files and folders to clean. Currently the Custom option accepts only specific files or entire folders. I.e., you can't tell it to clean only *.lst files, for example, in a specified folder. Rather, you would have to know the exact name and location of each .lst file you wanted to clean. The current implementation is still very useful, and I'm happy to have it, but it would be nice to have a bit more flexibility. - An option to purge the Windows Desktop Search index of deleted files. WDS will do this on its own, but it takes it's own sweet time. Say, for example, you cleaned out a bunch of .log files with CCleaner, and then performed a search for *.log in WDS... the files you recently cleaned would be returned in the results found by WDS, even though they no longer exist. Obviously, this is a shortcoming entirely of WDS' making, but then again, CCleaner addresses the shortcomings of a number of Windows system and application functions, so perhaps this would be useful (or am I the only person using WDS?) - a Mac OS X version I apologize in advance if any of the above have been requested earlier in the thread (I didn't make it through all 16 pages) or elsewhere on the forum. CCleaner kicks ass most mightily, so none of the above should be construed as disappointments, just idle wishes from an impressed user. - Sean
  7. I wouldn't say it's "absolutely" safe to delete -- it is a system file after all, and is listed in layout.ini -- but it is generally safe to delete. That said, I don't delete it regularly, but only after a period of installing and uninstalling a large number of fonts, specifically different versions of the same font, or whenever I notice slowdowns or strangeness in the appearance of menus, dialogs and other screen fonty things. Corruption to this file can occur whenever an installer (or manual action) overwrites any font registered with the system. If, for some reason, a reboot doesn't recreate fntcache.dat, go to Display Properties, choose the Settings tab and click Advanced. Under the General tab, change the DPI setting from Normal to Large (or vice versa depending on your setup). Apply, then change it back. (Note: I've never had an instance where a simple reboot didn't recreate fntcache.dat, but changing the DPI setting forces this file to be recreated.) - Sean
  8. My first post, so let me first say how impressed I am with CCleaner -- a truly first-rate app that became one of my all-time favorites within moments of using it. In addition to using CCleaner for basic system cleaning, I've also found it very useful for a more specific task -- clearing font cache files. Admittedly, not many of you will have a need to do this, but maybe some of you will. See, I develop commercial fonts for a living, and sometimes I find myself frequently installing and uninstalling fonts in various stages of development, a process which occasionally causes XP and the apps I use to test fonts grief. But thanks to CCleaner, I now have a quick way to clear font cache files. If you find yourself experiencing wierdness with font menus, font display or printing, you can add the following to your Custom files list in CCleaner: C:\Windows\System32\FNTCACHE.DAT If you regularly use Adobe apps (including Adobe Type Manager or ATM Deluxe), you may also want to add the AdobeFnt.lst files to your Custom files. You'll find these in various directories, depending upon which Adobe apps are installed on your system. Here are some examples: C:\Documents and Settings\username\Local Settings\Application Data\Adobe\Fonts\AdobeFnt10.lst C:\Documents and Settings\username\Local Settings\Application Data\Adobe\TypeSpt\AdobeFnt10.lst C:\Program Files\Common Files\Adobe\Fonts\AdobeFnt.lst C:\Program Files\Common Files\Adobe\Fonts\AdobeFntXX.lst (where 'XX' is a two-digit number) You may want to first search your drive for "AdobeFnt*.lst" to see where they're all located and their specific 'XX' names. You can safely delete all of them (do not delete AdobeFnt.db files, however, but only the .lst files). Note: If you add FNTCACHE.DAT to your Custom files, you will need to restart your machine after deleting it. A suggestion for future versions of CCleaner: When adding files to the Custom list, it would be very helpful to have the ability to add a folder, but instead of deleting its entire contents (as this feature presently works), to be able to specify wildcards. For example, choose the Adobe\Fonts and Adobe\TypeSpt folders in the Common Files dir, and tell CCleaner to delete any *.lst files it finds there. To the developer of CCleaner, many thanks for such a great utility. To any CCleaner users who might want more info about font caches, you can contact me via email (seanc at fontsite dot-diddly-ot com). - Sean
×
×
  • Create New...