Windows XP Setup cannot copy file.....

[ajklein4]

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.

 

[JAD]

clean your CD or try a different rom

 

[ajklein4]

No need to...I know what the problem is now if you read the post. But
thank you for the reply.

 

[JAD]

No need to...I know what the problem is now if you read the post. But
thank you for the reply.

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.

 

[John Doe]

clean your CD or try a different rom

Typical JAD, didn't even read the original post.

 

[Conor]

clean your CD or try a different rom

Pointless. Such errors are always the RAM.

 

[JAD]

Pointless. Such errors are always the RAM.

bullshit almost ALWAYS the CD - rarely ram

 

[JAD]

Typical JAD, didn't even read the original post.

I did read it did you? dipstick "memtestXX" utter bullshit memory tester.

 

[Conor]

bullshit almost ALWAYS the CD - rarely ram

Whatever. You've been proven thousands of time to be talking out your
arse.

 

[JAD]

Whatever. You've been proven thousands of time to be talking out your
arse.

practice what you quote eh?

 

[AJ]

The only reason I posted this was because I spent a few hours on
multiple search engines to gain some perspective as to what might be
the cause of my problems. I thought it might help someone else a
little if this showed up in Google searches since I had the benefit of
previous but much older posts. So it is hopefully not pointless. The
weight of the opinions leaned toward a RAM problem. I left out ththat
Seagate's Seatools Diagnostics showed a problem with the NTFS
formatting of the new drive. Windows installer would not copy files.
Memtest86 went crazy with any module in slot B1, which was populated
with one stick when I tried to format and install the OS. The memory
test was error free in all other configurations. I have satisfied
myself enough to return the motherboard to the vendor and I am
expecting a clean install when it arrives.

 

[spodosaurus]

The only reason I posted this was because I spent a few hours on
multiple search engines to gain some perspective as to what might be
the cause of my problems. I thought it might help someone else a
little if this showed up in Google searches since I had the benefit of
previous but much older posts. So it is hopefully not pointless. The
weight of the opinions leaned toward a RAM problem. I left out ththat
Seagate's Seatools Diagnostics showed a problem with the NTFS
formatting of the new drive. Windows installer would not copy files.
Memtest86 went crazy with any module in slot B1, which was populated
with one stick when I tried to format and install the OS. The memory
test was error free in all other configurations. I have satisfied
myself enough to return the motherboard to the vendor and I am
expecting a clean install when it arrives.

I had a very similar problem with a SIS chipset ASUS motherboard a
couple of years ago. Exchanged it and was fine after that (they were out
of stock of the SIS one, so I paid the extra $5 for the VIA chipset).

Ari

--
spammage trappage: remove the underscores to reply
Many people around the world are waiting for a marrow transplant. Please
volunteer to be a marrow donor and literally save someone's life:
http://www.abmdr.org.au/
http://www.marrow.org/

 

[John Doe]

The only reason I posted this was because I spent a few hours on
multiple search engines to gain some perspective as to what might be
the cause of my problems. I thought it might help someone else a
little if this showed up in Google searches since I had the benefit
of previous but much older posts. So it is hopefully not pointless.

That sums up one of USENET's best uses IMO.

That and like especially if I find little or no help in the USENET
archives or any place else.

Then there's someone who follows advice here and goes to the trouble
of posting the actual experience of fixing his (or her) computer
afterwords. That's cool too IMO.