0000401: Product Version: 7.05.2

Notes
(0000687) vcc (reporter) 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 (reporter) 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 (reporter) 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 (reporter) 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 (administrator) 2007-10-11 17:38	Indeed, this can't be caused by the DriverPacks.

Issue History
Date Modified	Username	Field	Change
2007-10-10 11:07	vcc	New Issue
2007-10-10 11:07	vcc	Status	new => assigned
2007-10-10 11:07	vcc	Assigned To	=> BashratTheSneaky
2007-10-10 11:07	vcc	File Added: GDIPLUS.MAN
2007-10-10 11:07	vcc	Destination OS Platform	=> wnt5_x86-32 (Windows XP)
2007-10-10 11:07	vcc	Installation Platform	=> disc (CD/DVD)
2007-10-10 11:07	vcc	DriverPacks	=> not applicable
2007-10-10 11:07	vcc	DriverPacks Method	=> 2
2007-10-10 11:07	vcc	DriverPacks Finisher Method	=> GUIRunOnce
2007-10-10 11:12	vcc	Note Added: 0000687
2007-10-10 11:15	vcc	Note Edited: 0000687
2007-10-10 12:22	vcc	Note Added: 0000688
2007-10-10 12:37	vcc	Note Added: 0000689
2007-10-10 12:52	vcc	Note Added: 0000690
2007-10-10 13:22	vcc	Note Edited: 0000690
2007-10-11 17:38	BashratTheSneaky	Note Added: 0000691
2007-10-11 17:40	BashratTheSneaky	Status	assigned => closed
2007-10-11 17:40	BashratTheSneaky	Resolution	open => fixed

Relationships