|
|
|
|
Joined: Nov 2005
Posts: 53 Likes: 1
Member
|
|
Member
Joined: Nov 2005
Posts: 53 Likes: 1 |
Or more like round 5. I've got another 7243 that won't read the hard drive; half the time the processor just stops running. It checks the ram, then identifies the hard drive, then it just dies (all this is from watching it boot up on Hyperterminal). New HDD, ram, bios, and even processor, and nothing helps. This is about the fifth one I've seen do this. Any ideas? I'm fresh out.
|
|
|
Visit Atcom to get started with your new business VoIP phone system ASAP
Turn up is quick, painless, and can often be done same day.
Let us show you how to do VoIP right, resulting in crystal clear call quality and easy-to-use features that make everyone happy!
Proudly serving Canada from coast to coast.
|
|
|
|
Joined: Aug 2005
Posts: 46
Member
|
|
Member
Joined: Aug 2005
Posts: 46 |
Hmmm....sounds tough. OK...how about this: is there ANY way that you can see the startup screen; as you see the start screen on a regular PC? Thinking outside the box, it sounds like the BIOS is set for the parameter "Halt On All Errors". I KNOW I could be wrong, but if it gets THAT far, I'm curious to see if that is a possibility.
If I'm wrong, I apologize now for wasting your time.
JM
|
|
|
|
|
Joined: Nov 2005
Posts: 53 Likes: 1
Member
|
|
Member
Joined: Nov 2005
Posts: 53 Likes: 1 |
The only way I know to do that is to open up keylink immediately after the VM loads the operating system, but it never gets that far (where it stops, that would be the next step actually).
On one of these boards I've changed every chip and crystal, metered every resistor, cap, and diode, and checked all the data lines for shorts. I still come up with squat. I'm really starting to hate these things :p
|
|
|
|
Forums84
Topics94,522
Posts639,997
Members49,851
| |
Most Online5,661
May 23rd, 2018
|
|
|
2 members (stwtech, AtcomJeff),
278
guests, and
34
robots. |
|
Key:
Admin,
Global Mod,
Mod
|
|
|
|
|
|
