Path:   
   eternal-september.org!mx02.eternal-september.org!feeder.eternal-september.org!n   
   ewsfeed.kamp.net!newsfeed.kamp.net!fu-berlin.de!uni-berlin.de!individual.net!no   
   t-for-mail   
   From: VanguardLH    
   Newsgroups: microsoft.public.windowsxp.help_and_support   
   Subject: Re: Excessive AVG Temporary Files ?   
   Date: Fri, 11 Mar 2016 16:02:16 -0600   
   Organization: Usenet Elder   
   Lines: 113   
   Sender: VanguardLH <>   
   Message-ID:    
   References:    
   Mime-Version: 1.0   
   Content-Type: text/plain; charset="us-ascii"   
   Content-Transfer-Encoding: 7bit   
   X-Trace: individual.net 3vUoz+pFnLlQxkBcCkP6pQdT+4WhU9k2faHNiP667oJ4g099FA   
   Keywords: VanguardLH VLH811   
   Cancel-Lock: sha1:382eX5gVTRvWbWG3Vip9dPdv0Ng=   
   User-Agent: 40tude_Dialog/2.0.15.41   
   Xref: mx02.eternal-september.org   
   microsoft.public.windowsxp.help_and_support:31819   
      
   We Shall Over Comb wrote on 2016/03/11:   
      
   > I notice when I remove files with CCleaner 2.35 that most of the clutter   
   files are labeled AVG.  I run it about every day and this is typical.  In the   
   past, I don't remember that much being removed.  Computer is mostly email with   
   Outlook Express 6 and limited website search & browsing.  No gaming or other   
   data intensive applications.  Does this seem like a lot of space to be   
   accumulating  every day?   
      
   Unless your client wraps overly long physical lines, you can see what   
   happens when using quoted-printable format: you get one very long   
   physical line that goes outside the viewing window.  That is NOT   
   recommended for posting in Usenet.  Usenet is not an e-mail venue.   
   Configure your NNTP client for maximum physical line lengths of 76, or   
   less, characters in length.     
      
   Content-Transfer-Encoding: quoted-printable   
      
   Don't use in Usenet.  Quoted-printable format structures the content in   
   paragraphs (1 long logical line per paragraph) rather than as physical   
   lines.  There are many NNTP clients that will not line wrap resulting in   
   the reader having to scroll horizontally back and forth to see your   
   post.  Also, there are many NNTP-to-HTTP gateways operated by web-based   
   forums (for those incapable of figuring out how to use an NNTP client   
   and were weaned on web browsers) and they may not line wrap so those   
   readers have to scroll horizontally back and forth.   
      
   In Outlook Express, configure the News format to use Text and configure   
   its options configure to:   
      
   Dialog: Plain Text Settings   
   MIME = selected   
   Encode text using = None   
   Automatically wrap text at 76 characters.   
      
   Because adding the ">" prefix character for quoted content in each level   
   of reply pushes out the original line, and because OE doesn't know how   
   to line wrap the quoted content within the ">" delimiters, you might   
   want to set physical line length to 72 or 70 to allow several levels of   
   replies without having to deal with OE's jerky line wrap.   
      
   If you are going to continue posting in Usenet using Outlook Express,   
   you might want to consider using OE-QuoteFix.  See:   
      
   http://home.in.tum.de/~jain/software/oe-quotefix/   
      
   > I am using Win2000 on this computer and 99%+ Firefox.  Thanks.   
   >    
   > Details of files just removed, 24 hours since last cleaning.....   
   >    
   > Total files removed 245MB   
   >    
   > Large files removed   
   >    
   > Utilities - AVG Antivirus 9.0 - 210MB   
   > Internet Explorer - Temporary internet files -- 32MB   
   > System - temporary files - 9MB   
   >    
   > Small files removed   
   >    
   > Mozilla - less than 200KB total all files   
   > Windows Explorer - 29KB   
      
   Questions about what temp files that AVG are creating are best submitted   
   to their forums.  You might want to tell that user community just WHERE   
   (the path) all these AVG files are getting created, and any filenaming   
   scheme if it is evident along with datestamps to show how many are   
   getting created within what period of time (they may come in bunches).   
   Old versions of AVG had that problem.  You should mention which version   
   of AVG you use and, if not the latest, update to the latest version   
   available for your OS (which means you may be stuck using an old version   
   of AVG for that old version of Windows).  Documentation for the latest   
   version of AVG at:   
      
   http://download.avg.com/filedir/doc/AVG_Free/avg_free_uma_en_ltst_14.pdf   
      
   Does not list Windows 2000 as supported.  They list the following   
   supported OSes: Windows XP, Vista, 7, 8, 10.  Those later OSes probably   
   have the required functions for AVG to function with features introduced   
   after their Windows 2000 version of AVG.  So you may be stuck with old   
   bad behavior in an old AVG version running on an old OS.  You cannot   
   take advantage of bug fixes and enhancements in later versions.   
      
   The latest version of AVG Free is 2016.0.7294.  According to oldapps.com   
   (www.oldapps.com/avg_antivirus.php, click the "Legacy OS support" link)   
   and https://en.wikipedia.org/wiki/AVG_%28software%29), AVG 9.0.851 was   
   the last version that supported Windows 2000.  That's pretty old.   
   http://filehippo.com/download_avg_antivirus_64/history/11/ only goes   
   back to version 10 dated back in 2010.  Even if an old version of AVG is   
   updating its signatures database, that is only part of the security   
   protection.  Heuristics and fingerprinting are also important.  You get   
   those improvements (program updates versus just sig updates) with later   
   versions of the software.  However, you're rather stuck on using the old   
   version with that old OS.  Doing the cleanup that are you doing now may   
   be the only solution to unwanted behavior in the old version of AVG.   
      
   As for CCleaner, rather than run it manually, you can schedule it.   
   Create a scheduled task that runs:   
      
   \ccleaner.exe /auto   
      
    is to wherever you installed CCleaner.  /auto has CCleaner do the   
   cleanup without prompting the user.  Obviously your computer must be   
   powered up and running Windows at the time a scheduled task is to run.   
   Occasionally I still want to manually run CCleaner but without the   
   intervening user prompts.  So I create a shortcut in a Windows taskbar   
   toolbar to run the above command.  Just click and it does its cleaning.   
      
   Note that cleaning out the %temp% folder can result in yanking away   
   files that are immediately needed but not currently locked.  For   
   example, some installers will deposit some files there that are used on   
   a subsequent reboot to finish the installation.  Make sure to configure   
   advanced options in CCleaner to NOT delete files less than 24 hours old.   
   If you leave the Recycle Bin enabled then you supposedly want the   
   ability to recover "deleted" files (i.e., those that are not actually   
   deletect by have been moved into the recyler folder).  In that case, you   
   should probably also configure CCleaner to NOT delete files in the   
   Recycle Bin that are less than 24 hours old.   
   --- Platinum Xpress/Win/WINServer v3.1   
    * Origin: Prison Board BBS Mesquite Tx  //telnet.RDFIG.NET www. (1:124/5013)