Re: Setup unable to copy file:
- From: Jay <idontlikespam@xxxxxxxxxxxxx>
- Date: Sun, 6 May 2007 06:54:02 -0700
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?
"Rey Santos" wrote:
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.
--
By rating a post as an answer or helpful, you help others find the answer
more quickly.
"Jay" wrote:
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)?
"GHalleck" wrote:
Rey Santos wrote:
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/
And, of course, the obvious when an OEM cdrom of dubious source is
involved...
5. Bios-locked OEM cdrom for specific brand of computer.
- Follow-Ups:
- Re: Setup unable to copy file:
- From: Jay
- Re: Setup unable to copy file:
- References:
- Re: Setup unable to copy file:
- From: GHalleck
- Re: Setup unable to copy file:
- Prev by Date: Re: save target as
- Next by Date: Re: Setup unable to copy file:
- Previous by thread: Re: Setup unable to copy file:
- Next by thread: Re: Setup unable to copy file:
- Index(es):
Relevant Pages
|
