Re: installijng ssd hard drive as boot drive for windows 7



Ian D wrote:

"Paul" <nospam@xxxxxxxxxx> wrote in message news:invi09$pac$1@xxxxxxxxxxxxxxxx
aaronep@xxxxxxxxxxx wrote:
I am interested in purchasing a 64 gb Kingston Solid State hard drive
and installing it on my Windows 7 PC as the
C drive which I believe would allow the system to boot up considerably
faster.

Has anyone done this? If so, what steps were used to make the
installation?

best, Aaron

Windows 7 is "SSD aware". If the SSD is detected, the partitioning
should be set up to align with sector 2048, rather than the traditional 63.
If you used WinXP, it would choose sector 63 for alignment of the first
sector (presumably based on CHS alignment and the fake values used for
such).

Windows 7 should also refuse to defragment the SSD, because defragmenting
them is not required. And that is because the seek time for an SSD is
0.1 milliseconds on the SATA bus (the flash chips may need around 0.025
milliseconds, to set up the operation and handle first data). Such a small
time means there is virtually no penalty for head movement.

Another optimization, is not updating the "last accessed" time stamp on
files. I don't know whether Windows 7 disables that by default or not.

I would expect Windows 7 could be installed and used, without special treatment.
If you could install the OS on a regular rotating hard drive, there shouldn't
be much difference with the SSD. If you set the BIOS to AHCI, Windows 7 has
the "msahci" driver which supports TRIM to a single drive. Getting TRIM
to work with RAID arrays, is a separate issue.

Paul

Paul,

Do you really need to enable AHCI to get TRIM support?

I got an Intel X25-M 120 GB SSD at a really good price. I installed
64 bit Win 7 Pro, along with various apps on it with my other
drives disconnected, but haven't yet put it into normal service. My
BIOS SATA setting is now at IDE. Right now I'm dual booting
XP Pro and 64 bit Vista Ultimate. The SSD would be introduced
in a tri boot setup using VistaBootPro.

If I change the BIOS to AHCI, will there be any loss of data
integrity on the other two drives?


I can't find a good reference, but along the way, I've seen "msahci"
and "TRIM" mentioned together a lot. I don't think the regular IDE
style driver supports it.

There are options besides TRIM. Some SSDs have built-in garbage
collection. And things like the Intel Toolkit, support manual
TRIM. So in some cases, you can get an equivalent to TRIM, using
a standalone application (left running overnight).

The procedure for flipping your system to AHCI, is here. You have to
"rearm" Windows 7 for the driver change, and that takes a registry
change. Once Windows 7 has identified the right driver, it prevents
the other ones from automatically detecting a hardware change later.
So the "rearm" step is necessary, before shutting down and entering the
BIOS to make the change. I notice in here as well, that some people
are having trouble with the "msahci" driver. The Intel driver package,
generally has AHCI and RAID in the same package, and you could get
AHCI that way. But I don't know whether the Intel AHCI also supports
TRIM - the reason for wanting "msahci" to pick up all the drives,
is it is built in. If you use a separate Intel driver, I don't
know whether you can later "go backwards" or not.

http://www.sevenforums.com/tutorials/61869-ahci-enable-windows-7-vista.html

OK, the bottom of this table, says the Intel RST driver supports
trim, for drives not in a RAID array. If you own two SSDs and they're
running RAID 0, then there is no TRIM used there.

http://www.intel.com/support/chipsets/imsm/sb/CS-022304.htm

"What features are supported on each I/O controller hub (ICH)?
...
TRIM support in Windows 7* (in AHCI mode and in RAID mode for drives
that are not part of a RAID volume"

I presume any AHCI driver is smart enough to query all hard drives, and
see whether they indicate they support AHCI. The same would apply to
using any command queuing protocol (NCQ or TCQ). There is no point in
tagging commands, if the disk isn't paying attention. The driver needs
a fallback, in case a user mixes ancient and modern drivers on the
same computer. If a person wanted, they could use an IDE to SATA adapter
dongle, and then that means the driver would be exposed to some crufty
old drives. Any driver, has to be tolerant of all the various revisions
of ATA/ATAPI specs.

Paul
.



Relevant Pages

  • Re: installijng ssd hard drive as boot drive for windows 7
    ... Windows 7 should also refuse to defragment the SSD, ... the "msahci" driver which supports TRIM to a single drive. ... Getting TRIM ... drives disconnected, but haven't yet put it into normal service. ...
    (alt.comp.hardware.pc-homebuilt)
  • Re: CHKDSK NTFS file system corruption boot screen message flooding (SOLVED)
    ... Your Installation Specialist ... Windows XP SP3 detects a disk problem at boot time and runs chkdsk. ... or registry fix for large LBA drives, ... older Microsoft-certified ultra.sys driver. ...
    (microsoft.public.windowsxp.general)
  • Re: STOP on shut-down, optical drives or drivers?
    ... Windows update loose. ... thought that this could be a different type of driver issue dealing with the ... the PCI Bridge that is used to connect to the CD-ROM drives. ... Some malware can restore themselves, and to prevent it, System ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Hot Swapping a SATA drive in Windows 2000 and XP.
    ... Using the ICHR5 chipset on Windows XP MCE (just an addon to ... > enclosures for the drives. ... and driver you have used because it is driving me crazy. ...
    (microsoft.public.windowsxp.hardware)
  • Re: Unable to Access CD/DVD drives
    ... All is well with that machine -- I'm now wondering if the windows drivers are ... device manager and let windows redetect them. ... Here are the Driver Details: ... For both the Sony & TSSC Drives: ...
    (microsoft.public.windowsxp.help_and_support)