Jump to content

brain75

Members
  • Posts

    8
  • Joined

  • Last visited

Reputation

0 Neutral
  1. I was trolling through the forums looking for good and bad ideas and ran across this. I would 3rd this suggestion, specifically .BAK .TMP .DMP etc - some powerusers know for sure that all .TMP files are trash and are willing to risk data loss with this feature - user beware, but feature enabled.
  2. no updates to this thread from the programmers yet - thought I would bump it back up to the top and see if we can get a status from the gurus?
  3. I regularly use CCleaner as one of 2 cleaners to do all my trace removal. Found out today that the FTP user name history is not being removed. Don't know if this is just a missing feature or if it is a bug in the latest code or... Steps taken to reproduce: 1) open a ftp site in M$ I.E. that requires credentials ftp://ftp.foo.bar 2) authenticate successfully with credentails 3) close I.E. 4) clean and wash everything - all options 5) rebooot, log off, or not - any which way same results autocomplete does NOT fill in ftp://ftp.foo.bar, BUT the popup box asking for username and password does automatically fill in the last user sucessfully authenicated
  4. Been a while and no input added here from the coders - what's the future of this request oh programmers. Any word from on high?
  5. calculating percentage versus calculating time is a 10x harder code implimentation - to throw out percent you just do that, before you start you know you have 107,000 items to handle, increment the % every 107 items. To calculate "time" and have it behave realistically you have to do 1% of the file i/o (call that A), 1% of the memory i/o (call that and then ballpark the time (100 * [A+B] ) - way to much bloat code for what little it accomplishes (think about this becoming a 3 meg executable just to time estimate correctly. again I'll defend coding this feature and not coding it. Anybody do the "1 hour" windows 95 install on a modern pc - it takes like 13 minutes. or even the ~32 minute win 98se install - it ticks off a minute every 20 seconds. time is a real tough thing to do right. KISS - keep it simple s***** - text field with however many items is appropriate, update it as needed. a smart user looks at his watch, notices it took 3 minutes for the first 10%, then leaves on a soda break for 27 minutes. (and yes, I was cleaning an old dog machine and that first clean removed 501Megs, and took 30 minutes)... unfortunately with the current non-progress bar I had to just look back at it every 10 minutes and wonder if the old dog had froze. All that said - I still want to give kudos out the coders - this is really the only feature that is poorly implemented, and as far as my other posts in other areas go, you can't dog a coder for not adding a feature, just screwin one up Thanks programmers and programmets
  6. As a programmer I can help defend the code writer, and both request the feature and request it NOT be implimented. Programattically it is almost impossible to ballpark file i/o time + registry i/o time + .... and then make your progress bar behave realistically (progress bars that show nothing but file work ok, you mix file and memory and the progress bar jumps and stalls). That said, I like to have an idea if I have 5 minutes left or 5 hours - so I want a real working progress bar. Cost / benefit wise I prefer to have a tiny clean sharp exe that does the job with no bloat - progress bars almost always bloat the code to ridiculous levels. So what's my ultimate input. I say leave a true progress out, dump the existing progress bar, and add a text field with say "delete file progress 5%" "delete registry progress 30%" and update the text as appropriate. This is more usefull than the duh progress bar you have now, and less bloaty than any other graphical option. Sure it's less pretty, but we are here for something that does a job good and clean not all pretty and half working. (sorry for the blunt, but we are here cause this is the best program, not junk code).
  7. I'm gonna second this request but with a little variation. How about command line switches that allow users to launch, chooose a dozen check box options, execute, and exit silently (no results)... for those of us who want total automation. I've done this in both VB.NET 2003 and C++, be glad to give you a sample code project / applicaiton - etc advice, help, anything you need.
  8. Ditto to the above suggestion, I would like RDP session history cleaned up as well. ( So much so I am willing to provide the code, VB or C++). Here's what I did in VB.NET 2003 (only used vb cause that is what we do at work, I'm really a C++ coder) Private Function CleanRDP() Dim regkey_RDPKey As RegistryKey Dim string_RDPDefaultFile As String 'True = Write, False = Read regkey_RDPKey = Registry.CurrentUser.OpenSubKey("Software\\Microsoft\\Terminal Server Client\\Default", True) If regkey_RDPKey.GetValue("MRU0") <> "" Then : regkey_RDPKey.DeleteValue("MRU0") : End If If regkey_RDPKey.GetValue("MRU1") <> "" Then : regkey_RDPKey.DeleteValue("MRU1") : End If If regkey_RDPKey.GetValue("MRU2") <> "" Then : regkey_RDPKey.DeleteValue("MRU2") : End If If regkey_RDPKey.GetValue("MRU3") <> "" Then : regkey_RDPKey.DeleteValue("MRU3") : End If If regkey_RDPKey.GetValue("MRU4") <> "" Then : regkey_RDPKey.DeleteValue("MRU4") : End If If regkey_RDPKey.GetValue("MRU5") <> "" Then : regkey_RDPKey.DeleteValue("MRU5") : End If If regkey_RDPKey.GetValue("MRU6") <> "" Then : regkey_RDPKey.DeleteValue("MRU6") : End If If regkey_RDPKey.GetValue("MRU7") <> "" Then : regkey_RDPKey.DeleteValue("MRU7") : End If If regkey_RDPKey.GetValue("MRU8") <> "" Then : regkey_RDPKey.DeleteValue("MRU8") : End If If regkey_RDPKey.GetValue("MRU9") <> "" Then : regkey_RDPKey.DeleteValue("MRU9") : End If 'Delete C:\Documents and Settings\%user%\My Documents\Default.rdp string_RDPDefaultFile = Environment.GetEnvironmentVariable("USERPROFILE") & "\\My Documents\\Default.rdp" If System.IO.File.Exists(string_RDPDefaultFile) Then System.IO.File.Delete(string_RDPDefaultFile) End If End Function 'CleanRDP() Basically the two things you need to do... 1) delete the MRU history from the registry 2) Delete the Default.rdp file that is re-created every time you run RDP client. Add this feature and maybe a couple others and I can abandone my code entirely and have just 1 cleaner
×
×
  • Create New...

Important Information

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