|Was the replacement mboard identical or different?|
MAKE SURE there are no metal mboard mounting posts mounted in the case where there are no holes for mounting screws in the mboard!!
You probably had a loose connection, or your ram was getting a poor connection.
My usual suggestions -
Check all the connections of the wiring to make sure they are all the way onto their pins and into their sockets, especially the main connector from the power supply. The wires close to the mboard going into the main power connector/socket should be more or less perpendicular to the mboard surface rather than at an angle. Make sure all cards in slots are all the way down in their slots.
See response 2 in this - try cleaning the contacts on the ram modules, and making sure the modules are properly seated:
It is common to un-intentionally damage IDE data cables, especially while removing them - the 80 wire ones are more likely to be damaged. What usually happens is the cable is ripped at either edge and the wires there are either damaged or severed, often right at a connector or under it's cable clamp there, where it's hard to see - if a wire is severed but it's ends are touching, the connection is intermittant, rather than being reliable.
Another common thing is for the data cable to be separated from the connector contacts a bit after you have removed a cable - there should be no gap between the data cable and the connector - if there is press the cable against the connector to eliminate the gap.
80 wire data cables are also easily damaged at either edge if the cable is sharply creased at a fold in the cable.
Try another data cable if in doubt.
Check your SATA data cables. The connector on each end should "latch" into the socket on the drive and on the mboard, or on the drive controller card - it should not move when you merely brush your hand against it near the socket - if it does, mere vibration can cause a poor connection of it - use another SATA data cable that does "latch", or tape the connector in place.
(There is a slight projection or bump on one side of the outside of the connector that "latches" it into the socket - it's easily broken off or damaged)
The same thing applies for the SATA power connection.
DO NOT try other ram in your mboard when your system isn't working properly - there is almost always nothing wrong with the ram if it worked fine previously in the same system, and the ram you try may not be compatible with your system!
Ram that works in another mboard , or any ram you buy or have lying around, may not work properly, or sometimes, not at all - even if it physically fits and is the right overall type (e.g. SDram, DDR, DDR2, etc.; PCxxxx, xxx mhz) for your mboard. In the worst cases of incompatibilty your mboard WILL NOT BOOT all the way with it installed, and the mboard may not even beep - the ram has to be compatible with the mboard's main chipset, or in the case of recent mboards, compatible with the memory controller built into the cpu.
The same applies for testing your ram in another mboard - the ram must be compatible with the other mboard - if it isn't any results of testing the ram on the other mboard cannot be relied upon to be valid.
If you still have the ram that was installed when the system worked fine, try installing just that ram.
See response 5 in this for some info about ram compatibilty, and some places where you can find out what will work in your mboard for sure:
Correction to that:
Once you know which module ID strings work in your mboard, you can get them from anywhere you like that has ram with those ID strings.
If you have brand name ram, it is usually easy to look up whether it's ID string is in a list of compatible modules found by using your mboard or brand name system model number.
If the ram is generic, that may be difficult or impossible.
emachines computers are well known to have el-cheapo power supplies that tend to fail more often than average, and when the power supply fails completely, they are a lot more likely than average to damage something else, often the mboard.
This is especially the case if the PS brand is BESTEC!!
Other than the PSs, there's nothing that's particularly substandard overall about emachines systems, especially more recent emachines models, because the mboards in them were/are almost always NOT made by the actual company that made the system - Trigem, in Korea - the mboards are made by major mboard manufacturers and supplied to Trigem. Trigem supplies the systems to emachines, and some other brand name builders also use Trigem supplied systems (and they often also have BESTEC power supplies) for their cheaper models.
T5234 Mboard is ECS MCP61PM-AM
However, he does not have the manual
PackardBell models use the same mboard:
Acer models use the same mboard:
Gateway uses the same mboard:
"It seems to be this one:
Only the LAN driver doesn't work."
MCP61PM-AM is probably an OEM only model - only supplied to brand name system builders - no support for the specific model on the ECS web site. The same mboard may be supplied to several different brand name builders, the only difference being the bios version is usually specific to the brand, although sometimes ECS mboards use a generic bios version . The model that guy found is very similar except the LAN chip is probably different. The mboard manual that guy found probably has info that also applies to the OEM only version, and the supported ram info (ram comptibility info) is probably the same.
However, the I/O chip and the bios code because of that may be different, so it's NOT a good idea to use bios updates for a similar model.
If you buy a ECS MCP61PM-AM that does not have the bios version for the brand name computer your using, then it's likely a Recovery disk or Recovery disk set for your model will refuse to load software because the bios code does not have the brand specific info it looks for, if the bios version is brand specific.