Windows 7 Trim commands work in IDE and AHCI mode (even if some guys say on this forum that it only works in AHCI mode, that is totally false....).
But you have to install Windows 7 Sata IDE/AHCI drivers (they are installed by default duing Windows installation), and not Intel or Nvidia ones (until they officially support trim in the near future)
Windows 7 will not install AHCI driver unless BIOS is set to AHCI, and he should not try to install AHCI driver if his board does not support AHCI.
To the OP, you can use non-AHCI mode but probably will not have NCQ, nor will it be as fast as in AHCI mode. How old is your MB?
If sticking with your present MB, you could use the Optimizer in Toolbox that runs the TRIM automatically by scheduling or you can run it manually to keep your drive to specs, or at least close to specs and no need to worry about longetivity. After installing Windows 7, just make sure Defrag is turned off.
The 680i board came out in late 2006 and I built the sytem in January 2007.
If the Toolbox can take care of TRIM for me with the SSD hooked up in IDE mode and I can schedule it to run, I'm more inclined to stick with the existing board since it serves my needs already and I don't plan to upgrade the rest of the system anytime soon; the new MB would just be to get AHCI for automatic TRIM.
Windows 7 disabled Defrag when it installed, so it was still able to detect that the drive is an SSD. I downloaded the firmware update, which trashed my original install, but I was able to reinstall Win7 anyway and it has been running well for the last 3+ weeks. I'll have to keep an eye out for the Toolbox since it isn't available right now.
HD Tune does detect some damaged blocks after the failure after the firmware update, should I be worried about them and RMA the drive?
Thanks for the replies.
The choice is yours. Here is the blog from Microsoft that gives information:
Will disk defragmentation be disabled by default on SSDs?
Yes. The automatic scheduling of defragmentation will exclude partitions on devices that declare themselves as SSDs. Additionally, if the system disk has random read performance characteristics above the threshold of 8 MB/sec, then it too will be excluded. The threshold was determined by internal analysis.
The random read threshold test was added to the final product to address the fact that few SSDs on the market today properly identify themselves as SSDs. 8 MB/sec is a relatively conservative rate. While none of our tested HDDs could approach 8 MB/sec, all of our tested SSDs exceeded that threshold. SSD performance ranged between 11 MB/sec and 130 MB/sec. Of the 182 HDDs tested, only 6 configurations managed to exceed 2 MB/sec on our random read test. The other 176 ranged between 0.8 MB/sec and 1.6 MB/sec.
Will Superfetch be disabled on SSDs?
Yes, for most systems with SSDs.
If the system disk is an SSD, and the SSD performs adequately on random reads and doesn’t have glaring performance issues with random writes or flushes, then Superfetch, boot prefetching, application launch prefetching, ReadyBoost and ReadDrive will all be disabled.
Initially, we had configured all of these features to be off on all SSDs, but we encountered sizable performance regressions on some systems. In root causing those regressions, we found that some first generation SSDs had severe enough random write and flush problems that ultimately lead to disk reads being blocked for long periods of time. With Superfetch and other prefetching re-enabled, performance on key scenarios was markedly improved.
What did you do with Superfetch, boot prefetching, application launch prefetching, ReadyBoost and ReadDrive?
HD Tune won't complete a benchmark of my drive because of a read error (presumably from one of those damaged blocks), but it shows transfer rates ranging from 201.6 to 204.9 MB/sec for the parts that it does manage to test.