Old Hardware help needed: Update.

I don't know if you guys remember my posts from a couple of weeks ago (I
can't just add this to that thread as I've just done a clean install) where
I couldn't get an old AT machine working for the life of me, swapped out
everything to no avail.

I was asked to report back when I solved it so here it is:

It was running a P166MMX and originally wouldn't always start, hitting reset
worked for a week then it died. I swapped everything out (and I mean
*everything*). The culprit? The CPU. I had swapped it out for another 166MMX
that I had here that had been a good pull and it didn't work either. I don't
know if the original mobo fried the second CPU after I fitted it and tried
it (I swapped mobos after I tried swapping CPUs) or what happened. They were
both more than adequately cooled. I've never had CPUs fail before so didn't
think they'd both be shot. I finally fixed it when I tried a third 166MMX in
the second mobo. (Lucky I've got piles of Socket 7 CPUs lying around!)

Just thought I'd post a follow-up to let y'all know what it was.

Thanks to all who helped me with this.
--
~misfit~


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.522 / Virus Database: 320 - Release Date: 29/09/2003

~misfit~ wrote:
I don't know if you guys remember my posts from a couple of weeks ago (I
can't just add this to that thread as I've just done a clean install) where I
couldn't get an old AT machine working for the life of me, swapped out
everything to no avail.

I was asked to report back when I solved it so here it is:

It was running a P166MMX and originally wouldn't always start, hitting reset
worked for a week then it died. I swapped everything out (and I mean
*everything*). The culprit? The CPU. I had swapped it out for another 166MMX
that I had here that had been a good pull and it didn't work either. I don't
know if the original mobo fried the second CPU after I fitted it and tried it
(I swapped mobos after I tried swapping CPUs) or what happened. They were
both more than adequately cooled. I've never had CPUs fail before so didn't
think they'd both be shot. I finally fixed it when I tried a third 166MMX in
the second mobo. (Lucky I've got piles of Socket 7 CPUs lying around!)

Just thought I'd post a follow-up to let y'all know what it was.

Thanks to all who helped me with this. -- ~misfit~

If I follow that correctly you say the third CPU worked in the "second" Mobo and
postulate the first mobo killed the second CPU. So both the 'first' mobo AND
'first' CPU (subsequently second CPU in first mobo) were bad, right?

Sounds to me like the original Mobo was the culprit since it apparently
destroyed the second CPU. And since it did that one could imagine it was
responsible for the first CPU failure as well.

That's always a risk when testing by part swapping: bad part taking out a
replacement during the test.

Btw, a bad Vcore regulator on the original mobo could easily do that and would
damage any processor put in. (could be caused by a poor solder joint, or some
other loose connection, which would explain why it was initially intermittent)
Could be other things too.

"David Maynard" wrote in message
...
~misfit~ wrote:
I don't know if you guys remember my posts from a couple of weeks ago
(I
can't just add this to that thread as I've just done a clean install)
where I
couldn't get an old AT machine working for the life of me, swapped out
everything to no avail.

I was asked to report back when I solved it so here it is:

It was running a P166MMX and originally wouldn't always start, hitting
reset
worked for a week then it died. I swapped everything out (and I mean
*everything*). The culprit? The CPU. I had swapped it out for another
166MMX
that I had here that had been a good pull and it didn't work either. I
don't
know if the original mobo fried the second CPU after I fitted it and
tried it
(I swapped mobos after I tried swapping CPUs) or what happened. They
were
both more than adequately cooled. I've never had CPUs fail before so
didn't
think they'd both be shot. I finally fixed it when I tried a third
166MMX in
the second mobo. (Lucky I've got piles of Socket 7 CPUs lying around!)

Just thought I'd post a follow-up to let y'all know what it was.

Thanks to all who helped me with this. -- ~misfit~

If I follow that correctly you say the third CPU worked in the "second"
Mobo and
postulate the first mobo killed the second CPU. So both the 'first' mobo
AND
'first' CPU (subsequently second CPU in first mobo) were bad, right?

Yep, at least I think that was how it went down.

Sounds to me like the original Mobo was the culprit since it apparently
destroyed the second CPU. And since it did that one could imagine it was
responsible for the first CPU failure as well.

Agreed.

That's always a risk when testing by part swapping: bad part taking out a
replacement during the test.

Yeah, first time it's happened to me though.

Btw, a bad Vcore regulator on the original mobo could easily do that and
would
damage any processor put in. (could be caused by a poor solder joint, or
some
other loose connection, which would explain why it was initially
intermittent)
Could be other things too.

Shrugs Who knows, the original mobo is long gone to the big rubbish tip in
the sky, as is about 16+ hours of my time. :-)
--
~misfit~


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.522 / Virus Database: 320 - Release Date: 29/09/2003

~misfit~ wrote:
"David Maynard" wrote in message
...

~misfit~ wrote:
I don't know if you guys remember my posts from a couple of weeks ago

(I

can't just add this to that thread as I've just done a clean install)

where I

couldn't get an old AT machine working for the life of me, swapped out
everything to no avail.

I was asked to report back when I solved it so here it is:

It was running a P166MMX and originally wouldn't always start, hitting

reset

worked for a week then it died. I swapped everything out (and I mean
*everything*). The culprit? The CPU. I had swapped it out for another

166MMX

that I had here that had been a good pull and it didn't work either. I

don't

know if the original mobo fried the second CPU after I fitted it and

tried it

(I swapped mobos after I tried swapping CPUs) or what happened. They

were

both more than adequately cooled. I've never had CPUs fail before so

didn't

think they'd both be shot. I finally fixed it when I tried a third

166MMX in

the second mobo. (Lucky I've got piles of Socket 7 CPUs lying around!)

Just thought I'd post a follow-up to let y'all know what it was.

Thanks to all who helped me with this. -- ~misfit~

If I follow that correctly you say the third CPU worked in the "second"

Mobo and

postulate the first mobo killed the second CPU. So both the 'first' mobo

AND

'first' CPU (subsequently second CPU in first mobo) were bad, right?


Yep, at least I think that was how it went down.


Sounds to me like the original Mobo was the culprit since it apparently
destroyed the second CPU. And since it did that one could imagine it was
responsible for the first CPU failure as well.


Agreed.


That's always a risk when testing by part swapping: bad part taking out a
replacement during the test.


Yeah, first time it's happened to me though.


Btw, a bad Vcore regulator on the original mobo could easily do that and

would

damage any processor put in. (could be caused by a poor solder joint, or

some

other loose connection, which would explain why it was initially

intermittent)

Could be other things too.


Shrugs Who knows, the original mobo is long gone to the big rubbish tip in
the sky, as is about 16+ hours of my time. :-)
--
~misfit~

I don't doubt it. Would have probably gotten a few ball pen hammer whacks from
me before it exited the premises by hand launched air express.

"David Maynard" wrote in message
...
~misfit~ wrote:
Shrugs Who knows, the original mobo is long gone to the big rubbish
tip in
the sky, as is about 16+ hours of my time. :-)
--
~misfit~

I don't doubt it. Would have probably gotten a few ball pen hammer whacks
from
me before it exited the premises by hand launched air express.

Nah, I've had to give up on the 'air express' thing. The missus complains
that she has to keep pulling mangled PC bits out of the lawnmower blades.
;-)
--
~misfit~


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.522 / Virus Database: 320 - Release Date: 29/09/2003

~misfit~ wrote:
"David Maynard" wrote in message
...

~misfit~ wrote:

Shrugs Who knows, the original mobo is long gone to the big rubbish

tip in

the sky, as is about 16+ hours of my time. :-)
--
~misfit~

I don't doubt it. Would have probably gotten a few ball pen hammer whacks

from

me before it exited the premises by hand launched air express.


Nah, I've had to give up on the 'air express' thing. The missus complains
that she has to keep pulling mangled PC bits out of the lawnmower blades.
;-)

Hahaha. Well, I end up relocating the wandering part to put it in it's
final resting place but I still get a bit of temporary satisfaction from it

"David Maynard" wrote in message
...
~misfit~ wrote:
[...]
Shrugs Who knows, the original mobo is long gone to the big rubbish
tip in
the sky, as is about 16+ hours of my time. :-)
--
~misfit~

I don't doubt it. Would have probably gotten a few ball pen hammer whacks
from
me before it exited the premises by hand launched air express.

I remember a thing on the net somewhere about a guy (kiwi?) who went nuts at
his RAM because it failed a memtest86 run ... started with lighter fluid,
then black powder, then finally thermite IIRC. I think it was suggested that
he RMA it after all that Unfortunately, I can't find it any more though


Oh well, this is almost as good:
http://www.killacomputer.com/PC-6-2003.htm


--
Michael Brown
www.emboss.co.nz : OOS/RSI software and more
Add michael@ to emboss.co.nz - My inbox is always open