MantisBT - DriverPacks BASE
View Issue Details
0000268DriverPacks BASEslipstreamerpublic2006-10-05 08:352006-10-05 12:33
RogueSpear 
BashratTheSneaky 
normalmajoralways
resolvedno change required 
6.10 
 
wnt5_x86-32 (Windows XP)
not applicable
not applicable
2
not applicable
0000268: TXTSETUP.SIF and/or DOSNET.INF are corrupted.
During the text mode portion of setup, setup complains that it cannot find a particular file. Inspecting the source reveals that the file is indeed present. The name of the file changes randomly with each slipstream.

I am using the RVM Integrator to integrate the latest update pack and then using nLite for a few things as well prior to using the BASE slipstreamer. If I do not use BASE at all, the problem goes away completely. This was also an issue with the last nightly build prior to the release of 6.10.

In my experience these symptoms are almost always the result of a problem with the txtsetup.sif file.
The attached 7-Zip archive contains both the modified txtsetup.sif and dosnet.inf file and their corresponding (.org) originals.
No tags attached.
7z Files.7z (81,251) 2006-10-05 08:35
http://bugtracker.driverpacks.net/file_download.php?file_id=200&type=bug
Issue History
2006-10-05 08:35RogueSpearNew Issue
2006-10-05 08:35RogueSpearStatusnew => assigned
2006-10-05 08:35RogueSpearAssigned To => BashratTheSneaky
2006-10-05 08:35RogueSpearFile Added: Files.7z
2006-10-05 08:35RogueSpearDestination OS Platform => wnt5_x86-32 (Windows XP)
2006-10-05 08:35RogueSpearInstallation Platform => not applicable
2006-10-05 08:35RogueSpearDriverPacks => not applicable
2006-10-05 08:35RogueSpearDriverPacks Method => 2
2006-10-05 08:35RogueSpearDriverPacks Finisher Method => not applicable
2006-10-05 12:33BashratTheSneakyStatusassigned => resolved
2006-10-05 12:33BashratTheSneakyResolutionopen => no change required
2006-10-05 12:33BashratTheSneakyNote Added: 0000573

Notes
(0000573)
BashratTheSneaky   
2006-10-05 12:33   
RogueSpear told me that it was not the DriverPacks BASE that caused this, but either the RVMIntegrator, his own AutoImage, or a crappy HDD (bad sectors).

This issue will be reopened if necessary.