From: SteveH on
Jan Alter wrote:
> "Bug Dout" <buggsy2(a)mailinator.com> wrote in message
> news:87bphatn48.fsf(a)mailinator.com...
>> Have you tried running one of the Memtests on this new build? Might
>> be a good idea before fiddling more with the HD and the Windows
>> install. Put one of the memtests (either 86 or +) on a CD and boot
>> from the CD. Then you can eliminate the memory as the problem...or
>> find it there. --
>> Nothing is more surprising than the easiness with which the many are
>> governed by the few.
>> ~ David Hume
>
> It sounds more like a memory problem with it crashing and falling
> back to the bios screen. From your specs I can't tell if it's one
> stick of memory or two. If it's one stick try another memory chip, if
> two then remove one stick and try starting with the other. Try
> memtest if you get pleasure out of any of these procedures for
> confirmation.

He's got a drive with XP on from another system, almost certainly with the
wrong drivers etc. - there's a very good chance it's not going to work,
without at least a repair install. Yes, it could easily be the memory as
well, but considering its not a fresh install on a new system, I know where
my money is.

--
SteveH


From: Jan Alter on


--
Jan Alter
bearpuf(a)verizon.net

"SteveH" <steve.houghREMOVE(a)THISblueyonder.co.uk> wrote in message
news:F%E0n.22175$Ym4.21758(a)text.news.virginmedia.com...
> Jan Alter wrote:
>> "Bug Dout" <buggsy2(a)mailinator.com> wrote in message
>> news:87bphatn48.fsf(a)mailinator.com...
>>> Have you tried running one of the Memtests on this new build? Might
>>> be a good idea before fiddling more with the HD and the Windows
>>> install. Put one of the memtests (either 86 or +) on a CD and boot
>>> from the CD. Then you can eliminate the memory as the problem...or
>>> find it there. --
>>> Nothing is more surprising than the easiness with which the many are
>>> governed by the few.
>>> ~ David Hume
>>
>> It sounds more like a memory problem with it crashing and falling
>> back to the bios screen. From your specs I can't tell if it's one
>> stick of memory or two. If it's one stick try another memory chip, if
>> two then remove one stick and try starting with the other. Try
>> memtest if you get pleasure out of any of these procedures for
>> confirmation.
>
> He's got a drive with XP on from another system, almost certainly with the
> wrong drivers etc. - there's a very good chance it's not going to work,
> without at least a repair install. Yes, it could easily be the memory as
> well, but considering its not a fresh install on a new system, I know
> where my money is.
>
> --
> SteveH
>
Hi Steve,

Reading what the OP said it seems that the problem of rebooting was
happening from the first system the HHD was in and continuing with the next
system he placed the HDD. If that's the case it could very well be the start
up files. I still wouldn't rule out the possiblility that it was memory in
the first system, and in the second it was driver issues.

--
Jan Alter
bearpuf(a)verizon.net


From: SteveH on
Jan Alter wrote:
>>
> Hi Steve,
>
> Reading what the OP said it seems that the problem of rebooting was
> happening from the first system the HHD was in and continuing with
> the next system he placed the HDD. If that's the case it could very
> well be the start up files.

I can't see where he said that, but never mind.

--
SteveH