The Cellar - View Single Post

Undertoad · 03-24-2006, 09:47 AM

In order to diagnose the problems in my "A" system, I replaced its old memory with newer memory stolen out of my "B" system.

B memory into A -> A works well

A memory into B -> B doesn't boot.

So. Add $80 of new matched 1GB Kingston memory to A, and take the 1GB out of A and put it back in B.

B memory into B -> B doesn't boot.

Fuuuuuuuck

Now system B is dual-boot; the IDE drive boots into Windows, the SATA drive boots into Linux (Fedora). Set it to boot into Linux and it does that fine. The BIOS recognizes both the IDE and the SATA. So, maybe the Windows boot record got messed up somehow during all the various rebooting and such.

03-24-2006, 09:47 AM	#51
Undertoad Radical Centrist Join Date: Jan 2001 Location: Cottage of Prussia Posts: 31,423	In order to diagnose the problems in my "A" system, I replaced its old memory with newer memory stolen out of my "B" system. B memory into A -> A works well A memory into B -> B doesn't boot. So. Add $80 of new matched 1GB Kingston memory to A, and take the 1GB out of A and put it back in B. B memory into B -> B doesn't boot. Fuuuuuuuck Now system B is dual-boot; the IDE drive boots into Windows, the SATA drive boots into Linux (Fedora). Set it to boot into Linux and it does that fine. The BIOS recognizes both the IDE and the SATA. So, maybe the Windows boot record got messed up somehow during all the various rebooting and such.