Gonzalo Servat wrote:
> > Have you done the basic cable/chip wiggle test? (remove+replace),3, *
> > every cable and chip[1].
>
> Sorry Terry, I don't follow this "(remove+replace),3,*" process?
You take cable, remove from pins, replace cable on pins, and repeat this
process three times. Do this with all your socketed chips on the
motherboard as well (if you need to)
15 years ago I was told I was a nut case for thinking this would fix a
faulty computer, but I kept on fixing them this way. Think "sick
building syndrome". Basically, new office/office works and factories
produce lots of "fumes" that can deposit on nice new shiny pins and
provide an insulating layer of gunk that causes intermittent problem.
Your mobo is new. It has basically come from a factory full of all sorts
of fumes.
You will also see this trouble in old computers as well, or any computer
in an office that has been newly fitted out, or even painted.
> > Checked error/message logs?. A faulty CD drive/HD on the way out can do
> > this (timeout messages)
>
> Sure did. Absolutely nothing that would indicate a fault in the logs.
Well that is good news then.
Well, maybe not so good news. HW faults usually have a definite fix.
Software, like drivers can be messy and you basically have to swap
out/deactivate bits and try different drivers until you work it out.
Try a google on your motherboard and pray that someone else has already
solved it {:-)
--
Terry Collins {:-)}}} email: terryc at woa.com.au www:
http://www.woa.com.au
Wombat Outdoor Adventures <Bicycles, Computers, GIS, Printing,
Publishing>
"People without trees are like fish without clean water"
--
SLUG - Sydney Linux User's Group - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug
