10-26-2009 12:10 PM
Just did the firmware update and it hosed my Windows 7 installation. The updater showed a successful firware update. Initially the computer booted just fine, but once I was within Windows it installed some drivers and asked for a reboot. That's when the trouble started. Now the drive won't boot Windows 7 anymore. I don't know if it's a Dell problem or Intel problem. The Dell BIOS claims a SMART error. I have a Dell XPS 8000.
10-28-2009 06:04 PM
dbm:
Thanks for the reply as to what was said in the Intel readme. I was certain it said it would work with AHCI enabled. Since my bios had no legacy/compatability mode(only IDE, AHCI, RAID) I decided to try for the AHCI setting. Had read that this was trouble and hard to do and it was. When it didn't recognize the SSD and said to contact Intel, that is what I did. The guy there was insistent that I use IDE mode to do the update as they had nothing but problems with users trying it in any other mode. Guess they've been doing lots of upgrades with the problems this hardware has had. He said it would go very simply in IDE mode and it did. There was no discussion of setting things back to AHCI after the upgrade. My thinking is that those folks whose motherboards (or whatever part does it) let them do the upgrade in AHCI mode
might have gotten in to trouble. Glad my board or whatever didn't see the SSD in AHCI mode so got the good advice from Intel to use IDE. Maybe any user error was started by the information on the readme? Maybe it would do the upgrade in AHCI then fail later when something was loaded or changed. As to the ports and what was plugged where, no clue. Guess I was just lucky the SSD was plugged into a proper port. Will be interesting to see where this all leads.
10-28-2009 06:17 PM
The way I read the Readme was there could be issues...and I set BIOS to IDE and then after firmware ran I rebooted back to BIOS and set it to AHCI before going back to desktop. Now that is what I am pretty sure I did.
10-28-2009 06:42 PM
Yeah, the Intel guy was sure there would be issues using anything but IDE. I couldn't rightly determine from the readme that IDE was an option (unless legacy/compatability mode is the same)--others probably understand this. Will leave things in IDE for now as can see only small advantages in using it and am afraid to blow something up from the trying of it. Have myriad questions on settings, drivers, etc. but those can go to other forums in other places. Later--
10-28-2009 07:17 PM
FWIW, my experience with two 80GB G2 drives updated to firmware 2CV102HA:
<!--[if gte mso 9]> <![endif]--><!--[if gte mso 9]> 0 false 18 pt 18 pt 0 0 false false false <![endif]--><!--[if gte mso 9]> <![endif]--><!-- /* Font Definitions */ @font-face {font-family:Arial; panose-1:2 11 6 4 2 2 2 2 2 4; mso-font-charset:0; mso-generic-font-family:auto; mso-font-pitch:variable; mso-font-signature:3 0 0 0 1 0;} @font-face {font-family:"MS Mincho"; mso-font-alt:"MS 明朝"; mso-font-charset:128; mso-generic-font-family:modern; mso-font-pitch:fixed; mso-font-signature:-536870145 1791491579 18 0 131231 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"MS Mincho"; mso-bidi-font-family:"Times New Roman"; mso-fareast-language:JA;} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.25in 1.0in 1.25in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} --><!--[if gte mso 10]> /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-ascii-font-family:Cambria; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:"Times New Roman"; mso-fareast-theme-font:minor-fareast; mso-hansi-font-family:Cambria; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} <![endif]--> <!--StartFragment-->
<!--[if gte mso 9]> <![endif]--><!--[if gte mso 9]> 0 false 18 pt 18 pt 0 0 false false false <![endif]--><!--[if gte mso 9]> <![endif]--><!-- /* Font Definitions */ @font-face {font-family:"MS Mincho"; mso-font-alt:"MS 明朝"; mso-font-charset:128; mso-generic-font-family:modern; mso-font-pitch:fixed; mso-font-signature:-536870145 1791491579 18 0 131231 0;} @font-face {font-family:"Neo Sans Intel"; mso-font-alt:Arial; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:3 0 0 0 1 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"MS Mincho"; mso-bidi-font-family:"Times New Roman"; mso-fareast-language:JA;} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.25in 1.0in 1.25in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} --><!--[if gte mso 10]> /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-ascii-font-family:Cambria; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:"Times New Roman"; mso-fareast-theme-font:minor-fareast; mso-hansi-font-family:Cambria; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} <![endif]--> <!--StartFragment-->
<!--[if gte mso 9]> ...
10-28-2009 07:41 PM
I wrote: The newer Mac [MacBook Pro mid-2009 13"], after firmware update, runs the drive at 3.0 Gigabit/s.
That would be Apple's update for the MacBook Pro itself, which enabled 3.0 Gigabit/s SATA. As initially shipped, it was restricted to 1.5 Gigabit/s.