why cache system32?

By Cosmin | December 2nd, 2008 | 9:29 am

i was wondering whether is or is not necessary to cache the windows/system32 folder. that contains lots of drivers that are anyway loaded into system ram. in same situation i think is the fonts folder. does it make an sense to cache them?

4 Responses to “why cache system32?”

  1. chris
    Dec 02, 2008

    general discussion about useful cacheable files (or not) would be interesting.


  2. belledesirepc
    Dec 02, 2008

    Well I think you do want the system32 to be cached, because like you say they are loaded into ram at boot time/whenever a program needs them.

    Loading them from eboostr cache at boot time/application loading will speed up your windows.


  3. belledesirepc
    Dec 02, 2008

    I did exclude the following folders:
    C:\Downloads (need my downloads only once after downloading)
    C:\System Volume Information (system restore point, no need to cache)
    C:\MSOCache (ms office installation cache)
    C:\RECYCLER (files to be deleted don’t need to be cache)

    I did exclude some file extensions also, you can read them in one of the previous posts


  4. mikei
    Dec 02, 2008

    This is general mistake thinking that system files all time sit in memory after loading on startup. This will be true in case of unlimited RAM. In real world, windows balance between cache and memory. So they are often discarded from memory.