temp internet files folder disk space

toxicgreentoxicgreen
edited May 2004 in Hardware
Hello and thank you for reading my post!
In the Temp Internet files settings what should my temp internet files folder disk space be set to? Right now mine is set at 951 MB. It's way to the left. Should i change it?

Also on my LOCAL DISK (C) properties, in the General tab, there are 2 choices at the bottom:
Compress drive to save disk space
Allow indexing service to index the disk for fast file search
Which should it be on?

Finally on the System properties menu, under the system restore tab, what should that be set on, mine is on MAX. is that right?
Thank you, soooooooooooo much
Regards,
Toxicgreen :zombie:

Comments

  • csimoncsimon Acadiana Icrontian
    edited May 2004
    I wouldn't change it much more or less than what it already is. I typically set mine to 1024mb's. Set it too low and your cache is so small that it has to reload each page each time ...too high and it gets bogged down with too much cache to sort through.

    I'm sure someone can offer a more technical explanation if you need it!
  • KwitkoKwitko Sheriff of Banning (Retired) By the thing near the stuff Icrontian
    edited May 2004
    Knowing your system specs and type of internet connection will help. I use cable internet on an XP2500+ with 1GB of RAM. My file cache for IE is set to 100MB. The PCs at my office are 500MHz PIIIs with 128-256MB of RAM on a 384kbps DSL connection. The file caches for those machines are set at 150MB. So far I haven't had a problem.
  • MediaManMediaMan Powered by loose parts.
    edited May 2004
    Temporary Internet Files: I set mine to 100MB. You'll only bog down your system by a) not clearing it out every so often and b) setting it to a huge size.

    Compress Drive Space: Ignore IMHO

    Indexing: It may make searches faster for finding files or folders but it does slow the drive down. Uncheck is my recommendation.

    System Restore Tab: I use GHOST to image my drives therefore I have completely disabled it. Setting system restore too large means you'll just store more history. So ask yourself...How much history do you want to store? I'd advise a more conservative setting. ...maybe 600MB to 1GB depending on partition/drive size.

    Others may have better insight into this since I usually turn it off.

    Hope this helps.
  • toxicgreentoxicgreen
    edited May 2004
    MediaMan wrote:

    Compress Drive Space: Ignore IMHO

    Indexing: It may make searches faster for finding files or folders but it does slow the drive down. Uncheck is my recommendation.

    wow thanks for the info! So leave the compress drive space unchecked too?
    When i unchecked the indexing for a faster search, it was transfering alot of files. And for a long time, i canceled cuz i was unsure. What was it doing?
    Thanks for answering all 3 questions i had. :mullet:
    Toxic
  • KwitkoKwitko Sheriff of Banning (Retired) By the thing near the stuff Icrontian
    edited May 2004
    Yes, leave compress drive unchecked.

    What happened when you unchecked indexing was Windows running through and removing the indexing from all the files. Let it run its course. No need to cancel it. If you see a popup box saying that it can't remove the index because the file is in use, just hit "Ignore All." Next time you restart your machine it will automatically un-index those files.
  • Straight_ManStraight_Man Geeky, in my own way Naples, FL Icrontian
    edited May 2004
    MediaMan wrote:
    Temporary Internet Files: I set mine to 100MB. You'll only bog down your system by a) not clearing it out every so often and b) setting it to a huge size.

    Compress Drive Space: Ignore IMHO

    Indexing: It may make searches faster for finding files or folders but it does slow the drive down. Uncheck is my recommendation.

    System Restore Tab: I use GHOST to image my drives therefore I have completely disabled it. Setting system restore too large means you'll just store more history. So ask yourself...How much history do you want to store? I'd advise a more conservative setting. ...maybe 600MB to 1GB depending on partition/drive size.

    Others may have better insight into this since I usually turn it off.

    Hope this helps.


    MM:

    Couple major idea things.

    I run System Restore defaulted to off. I will turn it on temporarily before I do any of these four general things:

    1. Install drivers.

    2. Install security packs I do not have good cross-checked feedback on.

    3. Install older programs, with my cutoff for new versus old being one year ago.

    4. Install beta software.

    System Restores are snapshots. So, if another reliable backup system is not in place, 10% of Hard Drive allowed for System Restore and a snapshot-only-when-you-need it strategy makes sense. The system state restore or backup snapshot point backup is very useful, for instance in any of these four situational cases. I treat system restore as an on-demand service, and utilize it as such. It is very good at allowing recovery from things that you are likely to see afterwards rather than immediately if used this way. A full backup as second full level of recovery will probably then also be wanted.

    System state backups include registry snapshots. Full backups also do, but it takes longer to get jsut system state recovered from a full backup, much less make one, than to recover just system state from a system state backup.

    IE Temp Internet Files:

    An alternative to setting your IE defaults fairly low is to use the Disk Cleanup function built into the XP accessories|system tools more often, then empty recycle bin, and then follow up with a 3X run of defrag on the boot partition. Most folks will not end up overrunning their HD space with stuff if this is done on a once-every-ten-days basis to a once-every-twenty-days basis. How much media-intense surfing you do will determine the exact time frame of this maint cycle more than anything else, as it is the graphics and not the pure HTMl that takes up most of space in the temp internet files subtree.

    I say to run the builtin defrag three times in a row with XP and 2000 because of the following one fact set: Microsoft has tuned the defragger for a minimum time for max overall performance benefits run rather than a one pass to fix even fine details run (they did more the opposite in 9X versions of Windows, and folks kept partly defragging their drives-- even more aborted the scandisk runs which could have saved them from a reload). Result is, to get finer details fixed, you get to run defrag more than once. Further, the need to defrag is based on performance loss analysis-- so, you can have data that is critical to you fragged badly before the "you need to defrag" notice after you choose analyze drive by using the Disk Defragmenter interface even shows up.
Sign In or Register to comment.