Scott said:
Was there no setup software that 'optimised' these settings
automatically?
Windows 7 has some level of awareness of SSD requirements.
Including power_of_two alignment for partitions, not running
defrag on the SSD, and so on. So some level of optimization
for wear life is already present. And the emission of TRIM
commands, helps make the spare space effectively larger,
for background garbage collection.
If you just connected your SSD to WinXP, then there is some
amount of tuning you can do if you feel like it. The SSD will *work*
without any help at all, but tuning can improve the benchmarks
on it slightly. Since an SSD is fast, compared to the original
hard drive, many people are quite content with just leaving it
in the out-of-the-box state.
As for an AV program, I would hope all it is doing, is redundant
reads, when you load executable programs. It's supposed to scan
stuff as you execute it. Reading an SSD doesn't hurt it. Whereas
writing requires block erasure of previous blocks, to be able to
write new data, and that eventually damages the flash cell (so-called
write life).
Windows file systems keep track of the last time a file was accessed,
and the info is written back to the disk. At least on WinXP, this
is something a new SSD owner would likely turn off. I don't know
if Windows 7 has any special provision for this (like batch updating
the necessary info, rather than one file at a time) or not.
http://www.ocztechnologyforum.com/forum/showthread.php?43460-Making-XP-pro-SSD-friendly
"fsutil behavior set disablelastaccess 1"
A person should at least be curious enough, to read the background
material on the topic, even if they never intend to do all the
actual grunt-work. (I.e. You should understand what the tradeoffs
are, by not doing anything special for your new SSD.)
Paul