Setup unable to copy file:

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am trying to install XP Home SP2 on a "fresh" computer with no luck. I have
had numerous problems with this proccess. I repeatedly am getting messages
during initial setup that setup cannot copy files. First message told me that
the disk may be damaged and to seek a possible replacement. It is an OEM
version bought from a supplier and I was told (I could be wrong) that I
shouldn't have any problems installing with it. Can anyone explain to me what
I should do next? I'm pulling my hair out trying to get my computer working
again and, as of now, have gotten nowhere fast. Please advise me.
 
Rey said:
1. faulty CD drive - try another one.
2. faulty CD - try another one, perhaps just borrow for trouble shooting
purposes.
3. Faulty RAM - check if your memory sticks are seated properly, remove one
stick at a time moving the other to another slot to see which is faulty or
perform memory test http://www.memtest86.com

A nice story simillar to this at:
http://www.hardwareanalysis.com/content/topic/30558/
Click to expand...

And, of course, the obvious when an OEM cdrom of dubious source is
involved...

5. Bios-locked OEM cdrom for specific brand of computer.
 
Well, I have gotten throught the first part of setup. Only now, the computer
restarts and says that it has caused a critical error and will shutdown. It
has a missing file somewhere from what the screen says. I loaded my bios to
defaults and got throught the first part with this. Now, I'm running chkdsk
/r to see if it will help. Any suggestions as to what else I may be able to
do (besides banging my head off the wall)?
 
Jay said:
Well, I have gotten throught the first part of setup. Only now, the computer
restarts and says that it has caused a critical error and will shutdown. It
has a missing file somewhere from what the screen says. I loaded my bios to
defaults and got throught the first part with this. Now, I'm running chkdsk
/r to see if it will help. Any suggestions as to what else I may be able to
do (besides banging my head off the wall)?
Click to expand...

Well, good luck. But if the answer to GHalleck's question is true,
then there will be problems. Just what type of Windows XP OEM cdrom
is it? Is it for a specific make of computer or is it the "generic"
Microsoft OEM version?
 
No don't bang your head on anything, we're still here ready to help you the
best we can. Just give us some more info. Were you able to install? What or
how did you do it? I believe the missing file is from what was installed. Is
the missing file something HAL.DLL? It's very important to know.
 
This is the info that windows is giving me after initial install and restart:

Error:
SXS.dll: Syntax error in manifest or policy file
"D:\I386\asms\10\msft\windows\gdiplus.man" on line 4

Error:
Installation failed D:\I386\asms. Error Message: A components file does not
match the verification information present in the component manifest.

Fatal Error:
One of the components that Windows needs to continue setup could not be
installed.

A components file does not match the verification information present in the
component manifest.

The WinXP cd is not a locked cd. It's the standard OEM WinXP SP2 cd. I
stripped the computer down, checked the RAM, checked the cd for anything
wrong, tested the cd-rom drives. Only thing in the computer now is hard
drive, RAM, AGP card and keyboard and mouse plugged in. About 2 months ago, I
upgrade my CPU from a celeron 335 to a P4 3.0E (Prescott). I'm wandering if
this might be the problem. My friend has come over and tried to install with
his XP cd and same result. I also tried re-installing Win2K, not luck there
either. With Win2K, I receive a message saying that setup was unable to
continue because ascpi.(whatever extension) was corrupted. Setup consequently
stopped. Could this be a hardware conflict somewhere?
 
UPDATE: I got Xp to go through the setup. Problem now is that my computer
restarted and now it gets to where XP should load (splash screen) and
immediately restarts. Never ending restart cycle.
 
I'm right back to the error mesages below. I looked on my motherboards
website to see if they had any good input on this. It seems that XP SP2
doesn't like Prescott (P4) C-0 stepping. I already had the latest BIOS on the
motherboard to solve this problem and it still doesn't want to work for me.
I'm beginning to think that this is impossible to complete.

 
Looks like XP's missing it's partition so it can recover.Your trying to put
it on D /drive not C/drive XP likes D for said partition...
 
Jay said:
I'm right back to the error mesages below. I looked on my motherboards
website to see if they had any good input on this. It seems that XP SP2
doesn't like Prescott (P4) C-0 stepping. I already had the latest BIOS on the
motherboard to solve this problem and it still doesn't want to work for me.
I'm beginning to think that this is impossible to complete.
Click to expand...

That is not true. However, setting up Windows XP does depend on the
motherboard being configured properly. Just what motherboard and bios
version? In some instances, the latest bios version is still a beta.
And an over-clocked CPU or RAM is also not contributory to achieving
a satisfactory Windows XP installation and initial startup. And the
same applies for mismatched hardware on the motherboard. Just what
are the hardware components that make up this system? How much true
upgrading was there in moving up from the Celeron to the P4 Prescott?
 
GHalleck said:
That is not true. However, setting up Windows XP does depend on the
motherboard being configured properly. Just what motherboard and bios
version? In some instances, the latest bios version is still a beta.
And an over-clocked CPU or RAM is also not contributory to achieving
a satisfactory Windows XP installation and initial startup. And the
same applies for mismatched hardware on the motherboard. Just what
are the hardware components that make up this system? How much true
upgrading was there in moving up from the Celeron to the P4 Prescott?
Click to expand...

I upgraded from the Celeron 2.8 to a Prescott core P4 3.0 HT. I read some
articles last night that say that certain Hyper Thread systems need an update
for XP to recognize them. I re-installed my Celeron just minutes ago and
started up my computer and it's going through setup with no problems.

Soyo SY-P4VTE Motherboard.
1 GB Ultra PC3200 400 Mhz SDRAM
P4 3.0E HT (prescott) or Celeron 335 2.8
256MB 8X AGP NVidia GFX

Recommendation on Microsoft website is get the computer working and updated
before switching back to P4 Prescott core. Hyper Thread messes with it until
update is installed.
 
Back
Top