I just bought a Samsung 840 SSD for my wife's computer.
Since Solid State Drives need the TRIM function of Windows 7, upgraded her XP system by installing a new 500 GB HDD and installed a new Windows 7 system on it, while booted in Sata IDE. I also installed Windows 7 on her new Samsung 840 SSD.
She has the following hardware:
Motherboard: Asus M4A88T-EVO/USB3
Chipset: AMD SB700
Bios: American Megatrend Vers. 307
Ram: 4 GB Single Channel DDR3
Everything booted up fine while in SATA IDE bios setting. As soon as I changed the bios to SATA AHCI, I get the infamous "NTLDR missing" message, which means it cannot find a boot device.
I have spent the last 3 days:
Updating the registry to set the correct values that enable AHCI, as per Microsoft,
Rebooting both of these drives, the 500 GB HHD as well as the 230 GB Samsung 840 SSD with IDE.
Downloading and updating all Asus drivers for the mother board.
Fresh installing Windows 7 again on the Samsung 840 SSD.
And doing all of this 4 times to no avail.
At that point I decided to find out if the problem was a defective drive.
I took her Samsung 840 SSD and installed in on my own computer. I installed Windows 7 on it and initiated this install from a my own Samsung 840 Pro SSD which was booted in AHCI and then accessed my CD drive.
Her 840 SSD booted just fine. This proved that the drive was fine and that the Windows 7 CD was also ok. Is it possible that a different boot.ini file is created when a Win7 installation is initiated while being booted in AHCI as opposed to IDE?
The only thing I found unusual, is that my wife's Samsung 840 SSD showed up as drive E:, while my own Samsung 840 SSD Pro showed up as drive C:
I am used to seeing drive" C:" as label for the boot drive in a multi drive environment. Is this something normal in Windows 7?
How can can I make my wife's 840 SSD boot in AHCI? Can it be a boot ini file pointing the wrong place? Please help.
Since Solid State Drives need the TRIM function of Windows 7, upgraded her XP system by installing a new 500 GB HDD and installed a new Windows 7 system on it, while booted in Sata IDE. I also installed Windows 7 on her new Samsung 840 SSD.
She has the following hardware:
Motherboard: Asus M4A88T-EVO/USB3
Chipset: AMD SB700
Bios: American Megatrend Vers. 307
Ram: 4 GB Single Channel DDR3
Everything booted up fine while in SATA IDE bios setting. As soon as I changed the bios to SATA AHCI, I get the infamous "NTLDR missing" message, which means it cannot find a boot device.
I have spent the last 3 days:
Updating the registry to set the correct values that enable AHCI, as per Microsoft,
Rebooting both of these drives, the 500 GB HHD as well as the 230 GB Samsung 840 SSD with IDE.
Downloading and updating all Asus drivers for the mother board.
Fresh installing Windows 7 again on the Samsung 840 SSD.
And doing all of this 4 times to no avail.
At that point I decided to find out if the problem was a defective drive.
I took her Samsung 840 SSD and installed in on my own computer. I installed Windows 7 on it and initiated this install from a my own Samsung 840 Pro SSD which was booted in AHCI and then accessed my CD drive.
Her 840 SSD booted just fine. This proved that the drive was fine and that the Windows 7 CD was also ok. Is it possible that a different boot.ini file is created when a Win7 installation is initiated while being booted in AHCI as opposed to IDE?
The only thing I found unusual, is that my wife's Samsung 840 SSD showed up as drive E:, while my own Samsung 840 SSD Pro showed up as drive C:
I am used to seeing drive" C:" as label for the boot drive in a multi drive environment. Is this something normal in Windows 7?
How can can I make my wife's 840 SSD boot in AHCI? Can it be a boot ini file pointing the wrong place? Please help.