Assembled all new parts for my new system:
Asus P5N-E SLI motherboard w/ nVidia 650i chipset
Intel Core2 Duo e6420 CPU
Crucial Ballistix DDR2 800 2 X 1 GB
Antec True Power Trio 550 W PSU
Seagate SATA II 400 GB HDD
Lie-On EIDE 20 DVD/CD drive
Antec P180 case
Windows XP Prof CD formatted the HDD just fine, but when it came time
to load Windows, there were immediate error messages. " Setup could
not copy the file *.sys. Press <Enter> to skip file. Press <F3> to
quit..... Windows CD may be damaged " RATS!! My CD was pristine. I
was thinking bad CD ROM reader, bad EIDE cables, BAD SATA HDD, missing
SATA driver from early Windows XP CD, bad motherboard memory
controller. An Internet search resulted in many opinions as to what
the cause might be. The most reliable opinions seemed to point towards
faulty memory. One Microsoft Knowledge Base article also attributed
this error message to defective RAM. I remeber that I had an old copy
of the free download memory testing program Memtest86.
My system failed the memory diagnostic program Memtest86 miserably (>
1 million errors on first pass). Memtest86 ran error free on my older
well-used PC. I tried using just one module of DDR2 and Voila!
Memtest86 ran flawlessly. By using multiple configurations of the
paired modules, either one or both at a time, it was proven that bank
B1 on the motherboard was faulty. Memtest86 ran perfectly by using
both RAM modules in A2 and B2 but I'll be returning the motherboard
anyway. I have not gone on to try to load Windows after the re-
positioning of the RAM modules to the good slots.
<ajklein4@gmail.com> wrote in message
news:1182664954.916477.202420@z28g2000prd.googlegr oups.com...
> Assembled all new parts for my new system:
> Asus P5N-E SLI motherboard w/ nVidia 650i chipset
> Intel Core2 Duo e6420 CPU
> Crucial Ballistix DDR2 800 2 X 1 GB
> Antec True Power Trio 550 W PSU
> Seagate SATA II 400 GB HDD
> Lie-On EIDE 20 DVD/CD drive
> Antec P180 case
>
> Windows XP Prof CD formatted the HDD just fine, but when it came time
> to load Windows, there were immediate error messages. " Setup could
> not copy the file *.sys. Press <Enter> to skip file. Press <F3> to
> quit..... Windows CD may be damaged " RATS!! My CD was pristine. I
> was thinking bad CD ROM reader, bad EIDE cables, BAD SATA HDD, missing
> SATA driver from early Windows XP CD, bad motherboard memory
> controller. An Internet search resulted in many opinions as to what
> the cause might be. The most reliable opinions seemed to point towards
> faulty memory. One Microsoft Knowledge Base article also attributed
> this error message to defective RAM. I remeber that I had an old copy
> of the free download memory testing program Memtest86.
> My system failed the memory diagnostic program Memtest86 miserably (>
> 1 million errors on first pass). Memtest86 ran error free on my older
> well-used PC. I tried using just one module of DDR2 and Voila!
> Memtest86 ran flawlessly. By using multiple configurations of the
> paired modules, either one or both at a time, it was proven that bank
> B1 on the motherboard was faulty. Memtest86 ran perfectly by using
> both RAM modules in A2 and B2 but I'll be returning the motherboard
> anyway. I have not gone on to try to load Windows after the re-
> positioning of the RAM modules to the good slots.
>
<ajklein4@gmail.com> wrote in message
news:1182665959.222609.54210@o11g2000prd.googlegro ups.com...
> No need to...I know what the problem is now if you read the post. But
> thank you for the reply.
>
>>I have not gone on to try to load Windows after the re-
>>positioning of the RAM modules to the good slots.
not sure what you solved, it seems you could still have the problem. 9 of 10 times failing
to copy a file or CRC errors are bad disks and or ROM. Memory is another culprit and that
maybe the case here, but you haven't proved it yet.
"Conor" <conor.turton@gmail.com> wrote in message
news:MPG.20e85864104caadf98abaa@news.karoo.co.uk.. .
> In article <eYnfi.31$gf2.28@newsfe06.lga>, says...
>> clean your CD or try a different rom
>>
> Pointless. Such errors are always the RAM.
>
>
> --
> Conor
>
bull**** almost ALWAYS the CD - rarely ram
"John Doe" <jdoe@usenetlove.invalid> wrote in message
news:Kgrfi.5209$Rw1.1886@newssvr25.news.prodigy.ne t...
> "JAD" <john doe harvesting.addys.for.****.spam> wrote:
>
>> clean your CD or try a different rom
>
> Typical JAD, didn't even read the original post.
>
>
>>I have not gone on to try to load Windows after the re-
>>positioning of the RAM modules to the good slots.
I did read it did you? dipstick "memtestXX" utter bull**** memory tester.
In article <XMwfi.11$_e7.3@newsfe04.lga>, says...
>
> "Conor" <conor.turton@gmail.com> wrote in message
> news:MPG.20e85864104caadf98abaa@news.karoo.co.uk.. .
> > In article <eYnfi.31$gf2.28@newsfe06.lga>, says...
> >> clean your CD or try a different rom
> >>
> > Pointless. Such errors are always the RAM.
> >
> >
> > --
> > Conor
> >
> bull**** almost ALWAYS the CD - rarely ram
>
Whatever. You've been proven thousands of time to be talking out your
****.
--
Conor
Light travels faster than sound. This is why some people appear bright
until you hear them speak.........
"Conor" <conor.turton@gmail.com> wrote in message
news:MPG.20e8c32f250aa08098abb4@news.karoo.co.uk.. .
> In article <XMwfi.11$_e7.3@newsfe04.lga>, says...
>>
>> "Conor" <conor.turton@gmail.com> wrote in message
>> news:MPG.20e85864104caadf98abaa@news.karoo.co.uk.. .
>> > In article <eYnfi.31$gf2.28@newsfe06.lga>, says...
>> >> clean your CD or try a different rom
>> >>
>> > Pointless. Such errors are always the RAM.
>> >
>> >
>> > --
>> > Conor
>> >
>> bull**** almost ALWAYS the CD - rarely ram
>>
> Whatever. You've been proven thousands of time to be talking out your
> ****.
>
>
practice what you quote eh?
Windows XP Setup cannot copy file..... 
Linear Mode
