Jump to content

JDPower

Experienced Members
  • Posts

    3,373
  • Joined

  • Last visited

Everything posted by JDPower

  1. No. The file starts GUT followed by 4 numbers and letters (mine is GUT37E2.tmp)
  2. These entries can probably be removed I think. Soluto is dead and, as far as I remember, required connection to their (also now dead) servers to work [Soluto Cache*] LangSecRef=3024 Detect=HKLM\Software\Soluto Default=False FileKey1=%CommonAppData%\Devices|*.* FileKey2=%CommonAppData%\Soluto\IconCaching|*.* FileKey3=%CommonAppData%\Soluto\rdcache|*.*|RECURSE FileKey4=%LocalAppData%\VirtualStore\ProgramData\Devices|*.* FileKey5=%LocalAppData%\VirtualStore\ProgramData\Soluto\IconCaching|*.* FileKey6=%LocalAppData%\VirtualStore\ProgramData\Soluto\rdcache|*.*|RECURSE [Soluto Dumps*] LangSecRef=3024 Detect=HKLM\Software\Soluto Default=False Warning=This will remove Soluto's dump files. If you use this feature to diagnose dumps, do not use this entry. FileKey1=%CommonAppData%\Soluto\Dumps|*.*|RECURSE FileKey2=%CommonAppData%\Soluto\Logs\KMCustomDumpFolder|*.*|RECURSE FileKey3=%LocalAppData%\VirtualStore\ProgramData\Soluto\Dumps|*.*|RECURSE FileKey4=%LocalAppData%\VirtualStore\ProgramData\Soluto\Logs\KMCustomDumpFolder|*.*|RECURSE [Soluto Logs*] LangSecRef=3024 Detect=HKLM\Software\Soluto Default=False FileKey1=%CommonAppData%\Soluto\logs|*.log;*.txt|RECURSE FileKey2=%LocalAppData%\VirtualStore\ProgramData\Soluto\logs|*.log;*.txt|RECURSE [Soluto Reports*] LangSecRef=3024 Detect=HKLM\Software\Soluto Default=False FileKey1=%CommonAppData%\Soluto\SysInfo|*.* FileKey2=%LocalAppData%\VirtualStore\ProgramData\Soluto\SysInfo|*.* [Soluto Temp*] LangSecRef=3024 Detect=HKLM\Software\Soluto Default=False FileKey1=%CommonAppData%\Soluto\Temp|*.*|RECURSE FileKey2=%LocalAppData%\VirtualStore\ProgramData\Soluto\Temp|*.*|RECURSE
  3. What is stored in that backups folder???
  4. I didn't think so, I don't even have any Windows Live stuff installed as far as I can tell. Only discovered them after trying out a rival program yesterday. Another rival I tried found me those missed Manycam entries. Sometimes it pays to sleep with the enemy
  5. Has anyone tried deleting the files at C:\Program Files (x86)\Common Files\Windows Live\.cache? Seems to be a load of cached installers that haven't been modified since Windows install?
  6. Added detect2 and filekey2 to this (detects and cleans the last unwatermarked free version that many use): [ManyCam Thumbnails*] LangSecRef=3023 Detect1=HKLM\Software\ManyCam Detect2=HKCU\Software\ManyCam Default=False FileKey1=%AppData%\ManyCam\Settings\MoviesThumbnails|*.*|RECURSE FileKey2=%LocalAppData%\ManyCam\cache\gallery|*.*|RECURSE
  7. I was all set to disagree, till you pointed me in the direction of the relevant post. Surely the simple solution for those entries is to just untick the "not older than 24 hours" box in CC's options, not add additional entries to winapp2 when the capability is already present within CC. So, short answer - I agree
  8. Yup. My routine is usually - try it, disable it, see it removed by Mozilla a few versions later.
  9. When will they learn. They keep adding tat/features to the browser, then removing them a few versions later to 'streamline' cos no one used it. And a screenshots tool? Might have been groundbreaking 10-15 years ago, but now? I really do wonder about the brains at Mozilla (or if there are any!)
  10. Those PCMatic guys being classy again at the merest hint of blood in a competitor - CCleaner "RIDDLED With Malware". "2 Billion devices exposed" Surely this being emailed out to millions today, when the facts proving it wrong were available a week ago ("2.27 million people used the affected software" - Piriform blog, September 18, 2017) is borderline defamation?
  11. Is there a separate collection of language file entries for winapp2?
  12. To be fair, you could say that about any dodgy entry
  13. A quick search of this thread will show you that wmdb files have been added, caused issues, been removed. Added, caused issues, been removed. Added, caused issues, been removed. You get the idea. So probably not one for the winapp2 file.
  14. Is this where I get to feel smug for holding off updating to 55
  15. I know, hence why I suggested keeping a backup of your FF54 profile
  16. Might be worth saving a backup of your FF54 profile folder before updating to FF55 so you can still go back a version if buggy. Or, more likely, still be able to switch to ESR and delay the web exts bomb of FF57 for a year or so (I might even run two profiles from 55 onwards, one ESR and one RC, just to cover all bases lol)
  17. Has the most recent FF version (54) been really laggy and locky uppy for anyone else?
  18. "We don't expect 64-bit Firefox to have any performance improvements over 32-bit"
  19. Don't use either so not a problem (though only a matter of time before developers start dropping support for Win7 - THEN I'll be pissed off)
  20. If it's going it's going, no point delaying it lol. I'll either have to live with the default layout, or finally make the move to Vivaldi that I've been threatening since forever
  21. The end of Classic Theme Restorer. Dreading it
  22. What black hole did 53.0.1 disappear down???
×
×
  • Create New...

Important Information

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