cmhayes
12-14-2004, 11:51 PM
I rescued an old PC from work that was otherwise going to be scrapped. It had a Gigabyte GA-7ZX motherboard, an 800 MHz Athlon processor, a 30 GB Maxtor HD and a generic 52X CD-ROM drive. My plan was to cannibalize working components to build a system for my seven-year-old. I put a stick of memory in it and an ASUS MX-440 video card. It booted fine and everything appeared to be working. The case was beat up and missing a side panel, so I migrated the parts to another, nearly identical case. (I then foolishly tossed the old case because it was garbage day.) The computer would not boot in the new case. The power LED on the board would flicker and the CPU and case fans would spin for an instant, then nothing.
I checked connections, unplugged components, cleared the CMOS, etc.—nothing. I swapped out the power supply with a new one I had and got the same result. Nothing. I then swapped the motherboard with a new Gigabyte 7NF-RZ-C and an old (but working when recently pulled) 1.2 GHz Duron. I put a new 256 MB stick of PC2100 memory in it. The light in the network connection would flicker briefly, then nothing. I hooked up the old power supply to an old Matsonic MS7308E board outside the case and it powered up. I hooked up the new power supply to the Matsonic board and it powered up. When I took the 7NF-RZ-C board out of the case and hooked it up to either power supply it powered up. I put it back in the case, hooked everything back up (one component at a time, powering up after each component) and the computer booted fine.
I noticed the 30 GB hard drive was set up with a single 2 GB partition under DOS 6.0.2. Windows 98 was loaded but there was 28 GB unused. I didn't want to tackle the drive capacity problem after the traumatic start-up, so I shut the computer down. The next day it wouldn't boot. The only thing different this time was the CPU and case fans came on and the hard drive spun up. No POST, no signal to the monitor. My plan is to take the system apart and put it back together one piece at a time (again).
My question is this: Does it sound like I have a bad component somewhere? Could it be one of the drives as they are the only common components throughout this ordeal? Or could there be a grounding issue or some other problem with the case itself? I'm not sure what that would be but the problems started when I migrated the old hardware to the new(er) case (the case had housed an ASUS A7N-266VM-based system and was only taken out of service when I migrated its guts to a smaller case).
I checked connections, unplugged components, cleared the CMOS, etc.—nothing. I swapped out the power supply with a new one I had and got the same result. Nothing. I then swapped the motherboard with a new Gigabyte 7NF-RZ-C and an old (but working when recently pulled) 1.2 GHz Duron. I put a new 256 MB stick of PC2100 memory in it. The light in the network connection would flicker briefly, then nothing. I hooked up the old power supply to an old Matsonic MS7308E board outside the case and it powered up. I hooked up the new power supply to the Matsonic board and it powered up. When I took the 7NF-RZ-C board out of the case and hooked it up to either power supply it powered up. I put it back in the case, hooked everything back up (one component at a time, powering up after each component) and the computer booted fine.
I noticed the 30 GB hard drive was set up with a single 2 GB partition under DOS 6.0.2. Windows 98 was loaded but there was 28 GB unused. I didn't want to tackle the drive capacity problem after the traumatic start-up, so I shut the computer down. The next day it wouldn't boot. The only thing different this time was the CPU and case fans came on and the hard drive spun up. No POST, no signal to the monitor. My plan is to take the system apart and put it back together one piece at a time (again).
My question is this: Does it sound like I have a bad component somewhere? Could it be one of the drives as they are the only common components throughout this ordeal? Or could there be a grounding issue or some other problem with the case itself? I'm not sure what that would be but the problems started when I migrated the old hardware to the new(er) case (the case had housed an ASUS A7N-266VM-based system and was only taken out of service when I migrated its guts to a smaller case).