Jump to content
Corsair Community

Windows 7 Tips & Tweaks


Davyc

Recommended Posts

taltamir,

You do realize this was posted almost three years ago right? And yes you are correct with any current SSD Force 2 or newer just let Windows 7 take care of everything for you.

 

Since Windows still doesn't support TRIM on RAID 0 drives, I think this article is still up-to-date and valid for RAID 0 configurations.

Link to comment
Share on other sites

  • Replies 137
  • Created
  • Last Reply

Windows would support TRIM in RAID0 if the controller will pass the instructions to the drives. its not Windows problem, its the chipset/drivers :):

In the release notes of a recent release of the Intel Rapid Storage Technology (IRST) driver (RAID, AHCI), it was said that an upcoming release of IRST would support TRIM in RAID 0 volumes. That has not yet happened, but we can only hope that it will.

 

Any SSD that supports TRIM (which should be all of them released since early 2011, and many before that) will work fine with a RAID driver that allows TRIM commands to reach SSDs, which is currently what does not happen.

Link to comment
Share on other sites

  • 1 month later...
Do you know anyone that knows how to optimize Win 7 using Chrome as a browser? Basically I need to learn how to store the Chrome Cache's, temp file's and other files that are going to constantly build up on my boot SSD. The step's for optimizing I.E. w/SSD's are clearly posted at the top of this thread. I think you prepared it. Can I optimize Chrome the same way?
Link to comment
Share on other sites

  • 3 months later...
Well its hard to say what you got from this but in a nut shell this information originally posted was from three years ago and pertained to first generation SSD's. Now that being said Current SSD Technology is third generation and O.S. and Driver/Bios support has greatly been improved so most of this is just not applicable but some of whats stated is noteworthy but with Windows 7 none of this is needed as Windows 7 supports SSD's and will disable settings it does not need. So for 99% of us just install Windows 7 and use the default format and let Windows do what it is supposed to and if you do run into an issue let us know we will do our best to help you.

 

Then there should be a disclaimer on the first post! I fully believed in this as it is a sticky on the manufacturer's website. To me, this means that the information is valid, current, supported and recommended. No where does the information appear that states "Oh, this is pretty much irrelevant but we do not have time to update it or add the limitations"

 

Not a way to be regarded as trustworthy.

Link to comment
Share on other sites

  • Corsair Employees

$teve

It would be easier for us to answer your questions, so please start a new thread and ask your questions.

I am sorry but It would be too confusing and time consuming to try and find all of your posts and organize them for you.

 

Capt Proton

Okay I would say the same for you as well.

so please start a new thread and ask your questions.
Link to comment
Share on other sites

  • 1 month later...
Disabling or greatly reducing your pagefile is likely a bad choice. Windows does not use the pagefile as an "overflow" when your RAM gets full. Instead it keeps the pagefile up to date as a mirror of what you have in RAM. Windows will offload certain memory (e.g. memory that is less often accessed) out of RAM to free up the RAM for other apps. When the offloaded data is needed again, Windows swaps it from the pagefile back into RAM.
Link to comment
Share on other sites

  • 1 year later...

Some apps *cough* MSSE *cough* ignore the TEMP environment variable, and put the temp files in C:\Windows\Temp regardless. This put a lot of wear on my first SSD, an Intel X-25 G1, which did not have TRIM.

 

The workaround for this, instead of setting the environment variables, is to use junctions to make C:\Windows\Temp really be located on a different drive. I would recommend Link Shell Extension for that.

 

Another thing to note: If you have a lot of RAM, and apps are written properly, the temp directory physical location becomes kind of irrelevant. Files that are created with the FILE_FLAG_TEMPORARY flag (which stuff in the temp directory SHOULD have...) is cached in RAM as much as possible by Windows, only flushing to disk if it can't fit in free memory, because it actually expects those files will be deleted soon.

Link to comment
Share on other sites

  • 1 year later...

Archived

This topic is now archived and is closed to further replies.

Guest
This topic is now closed to further replies.

×
×
  • Create New...