assuming nothing at all changed - the PC was running fine, you turned it
off, you turned it on, and BIOS sdtarted giving you odd messages &
things didn't work right, then you certainly have a component failure
inside the box. Check all cables and connections everywhere and make
sure they are firmly seated. Check drive jumpers; they may have fallen
off. Make sure every card (RAM and device cards) is firmly seated; best
you remove/reinsert them, or at least press them down firmly. Drives do
fail, sometimes suddenly, sometimes partially, sometimes slowly and
progressively. If you can boot W2k at some point, go through Device
Manager and Event Viewer carefully looking for clues. Most likely you
will find and cure the problem by doing the above. If none of the above
gives satisfaction, your recourse is to find an experienced friend or a
repair shop. With luck, the above will cost you only time. You'll need a
screwdriver, lots of patience, and running shoes so you can hop around
every few minutes and see if it boots yet.
amat wrote:
>>Does it have a SCSI or an IDE hard drive?
>
> - IDE drive
>
>
>>Were you (or anyone else) inside the computer doing
>
> stuff e.g., installing some new hardware) and then it
> wasn't working when you turned it on again?
> - nope... i was working on a school project, and all of a
> sudden i got a memory dump (with the blue screen, and all)
> error and that's when the problem started...
>
>
>>Was it dead out of the box?
>
> - nope. i've had it for a couple of years.
>
>
>>Assuming you walked up and turned it on one day and it
>
> didn't boot, something failed inside it or it got bumped
> and a cable or card dislodged. You could try opening up
> the case and seeing if anything was obviously amiss like a
> card half out of a socket or a cable not inserted
> completely.
> - hmmmmm... could be it... i got to check...
>
>
>>If it just stopped working and you don't know of
>
> anything in particular that could have happened to it,
> troubleshooting it is going to require some spare
> components that you know work. Try hooking a known-good
> drive with a known-good cable to the IDE controller (take
> the existing drive/cable off) and see if it finds the
> drive. If it doesn't, you have a bad controller or cable.
> If it does, the existing drive or cable is bad.
>
>>I'm going to assume you have enough native intelligence
>
> to figure out how to distinguish between a bad drive and
> bad cable given a good drive and a good cable.
> - thanks for the advice...
>
> one more thing, though, could it be a software problem,
> maybe a virus or something?
>
> anyway, thanks a lot for your response, it was very
> informative.
|