MantisBT - DriverPacks BASE
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0000401DriverPacks BASEDPs BASE misc.public2007-10-10 11:072007-10-11 17:40
Reportervcc 
Assigned ToBashratTheSneaky 
PrioritynormalSeveritycrashReproducibilityalways
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version7.04 
Target VersionFixed in Version 
Destination OS Platformwnt5_x86-32 (Windows XP)
Installation Platformdisc (CD/DVD)
DriverPacksnot applicable
DriverPacks Method2
DriverPacks Finisher MethodGUIRunOnce
Summary0000401: Product Version: 7.05.2
DescriptionAfter the driverpacks unpack (Windows XP GUI setup) I get an Error that states SXS.DLL: Syntax error in manifest or policy file "D:\ROOT\XPPC\I386\asms\1000\MSFT\Windows\GDIPLUS\GDIPLUS.MAN" on line 4
Then it goes on to say that A component's file does not match the verification information present in the component manifest.
Steps To Reproduce
Additional InformationI thought this might be a result of some addons I was using, so I decided to do some diagnostics and only integrate the Driverpacks alone. I am using Siginet's Powerpacker 1 RC9 (which I have been using successfully for some time now. The only thing new with this disk is the DriverPacks. I have tried reburning the disk and even using a different burner since the SXS.dll error seems to not be new when doing a google search, but many say the disks are dirty. I'm using new disks and have tried many.
TagsNo tags attached.
Relationships
Attached Files? GDIPLUS.MAN (391) 2007-10-10 11:07
http://bugtracker.driverpacks.net/file_download.php?file_id=273&type=bug
Issue History
Date ModifiedUsernameFieldChange
2007-10-10 11:07vccNew Issue
2007-10-10 11:07vccStatusnew => assigned
2007-10-10 11:07vccAssigned To => BashratTheSneaky
2007-10-10 11:07vccFile Added: GDIPLUS.MAN
2007-10-10 11:07vccDestination OS Platform => wnt5_x86-32 (Windows XP)
2007-10-10 11:07vccInstallation Platform => disc (CD/DVD)
2007-10-10 11:07vccDriverPacks => not applicable
2007-10-10 11:07vccDriverPacks Method => 2
2007-10-10 11:07vccDriverPacks Finisher Method => GUIRunOnce
2007-10-10 11:12vccNote Added: 0000687
2007-10-10 11:15vccNote Edited: 0000687
2007-10-10 12:22vccNote Added: 0000688
2007-10-10 12:37vccNote Added: 0000689
2007-10-10 12:52vccNote Added: 0000690
2007-10-10 13:22vccNote Edited: 0000690
2007-10-11 17:38BashratTheSneakyNote Added: 0000691
2007-10-11 17:40BashratTheSneakyStatusassigned => closed
2007-10-11 17:40BashratTheSneakyResolutionopen => fixed

Notes
(0000687)
vcc   
2007-10-10 11:12   
(edited on: 2007-10-10 11:15)
I just verified that there is nothing different from the original file and the one after packing. (That is the GDIPLUS.MAN file) and the SXS.DL_ file does not seem changed either.

I'm going to try running the DriverPacks with the RunOnceEx Finisher Method instead and see what happens. - I'll add a note when I'm done to share my finding.
(0000688)
vcc   
2007-10-10 12:22   
Still having problems. After changing to RunOnceEx, I now get the same Fatal Error, but different file (SXS.DLL I guess is the manifest checker utility) but the file it complains about now is in ...asms\52\MSFT\WINDOWS\NET\DXMRTP\DXMRTP.MAN" on line 5.

I guess I can try building the disk without the driverpacks, or even an older version of the driverpacks to see what happens then. I don't know why the driverpacks would have an effect on these files though.
(0000689)
vcc   
2007-10-10 12:37   
I'm also trying another computer to see if it is either the computer or the DVD drive in the destination computer, maybe it is not reading the disk properly (these are not old computers by the way. The destination computer is less than a year old). If this other computer does not have the same problem as my original destination PC, I will then try another DVD drive in the destination computer I've been having problems with.
(0000690)
vcc   
2007-10-10 12:52   
(edited on: 2007-10-10 13:22)
:-) Well, I'm pleased to say that it appears to have nothing to do with the DriverPacks. Sorry to falsely accuse the DriverPacks, but maybe this Bug report will help someone in the future that may run across the same Error.
The other computer I tried the disk in did not stop with a Fatal Error.
Now I'll be using the same DVD drive it is succeeding on in the original Destination computer. I'm thinking that it will work.
Darn bad hardware :-(
Bashrat, go ahead and close out this bug report.

*** Update (just FYI) ***
Ouch, well I used the same disk and drive from the computer that had success. It still failed. Maybe the reason I'm reinstalling Windows on this computer is a bigger issue than I anticipated. The original problem was many virtual memory errors that seemed related to this particular computer not being able to run Symantec Antivirus (version 10.1) properly, it wouldn't run the Auto Protect feature at all. So, on to warranty repair.
(0000691)
BashratTheSneaky   
2007-10-11 17:38   
Indeed, this can't be caused by the DriverPacks.