11-16-2009 09:47 PM
To 34nm (G2) Intel® X25-M Solid-State Drive consumers,
• Intel has confirmed an issue with the firmware update process for 34nm (G2) Intel® X25-M SSDs (80GB and 160GB). This predominantly affected Windows* 7 (64bit) users during or immediately after the upgrade process to 02HA firmware using the firmware update tool (version 1.3). Intel plans to release a fix for this issue by the end of November 2009.
• Please see below to decide what you should do:
• If you have not upgraded to 02HA but using 02G2 or 02G9 – then use new tool when available to upgrade to new firmware to get Trim support and better sequential write performance (160GB)
• If you have successfully upgraded to 02HA - then continue using the SSD, there are no known issues.
• If you have received a SSD with 02HA pre installed – then continue using the SSD, there are no known issues.
• If you have unsuccessfully upgraded to 02HA - then contact Intel Customer Support for instructions on how to recover the SSD via secure erase or return SSD to Intel for replacement or refund.
*Other names and brands may be claimed as the property of others.
Alan
NAND Solutions Group
Intel Corporation
11-17-2009 12:56 PM
[Quote]
If you have not upgraded to 02HA but using 02G2 or 02G9 – then use new tool when available to upgrade to new firmware to get Trim support and better sequential write performance (160GB)
[/Quote]
Why do you specify 160GB? I've got a new (still in sealed package) 80GB. Is there an additional problem with the 80GB?
Kenneth Tan
11-17-2009 01:24 PM
The firmware is for 80GB and 160GB drives, but only the 160 GB drive will have better sequencial speed after the upgrade.
Because the 160 GB drive has 2 times the number of chips of the 80GB, they could increase its sequencial speed a bit in the new firmware.
11-17-2009 04:20 PM
afrosty, thanks for keeping us informed and providing an ETA. Very much appreciated!
11-17-2009 04:30 PM
11-17-2009 04:34 PM
So your point exactly is ?
That I should not thank afrosty because the information is also accessible in another way and not only at the top of the thread that he created?