QUOTE (450 @ Mar 5 2007, 03:04 PM)

When WMP11 is integrated in slipstreams, the phenomenon of OOBE's breaking is recognized, and solved by integrating WindowsXP-KB894871-x86-JPN.exe.
QUOTE (S3pHiroTh @ Mar 5 2007, 02:37 PM)

With the patch KB927891, as Microsoft said, resolve this issue, but the file for Windows XP (as described in the hotfix knowledge) is called msi31.dll, not msi.dll.
After I have slipstreamed that patch in my source, with hfslip, that file (msi31.dll) doesn't exist, but there is a version of msi.dll that is the same of the "patched" msi31.dll.
Does hfslip rename that file to msi.dll?
The last few test releases rename that file (as mentioned in the changelog). It's supposed to happen. From the INF file:
CODE
[MSI31.System32.files]
msi.dll,SP2QFE\msi31.dll
QUOTE (Kiki Burgh @ Mar 5 2007, 04:53 AM)

became much worse this time ... still the same prompts for
hfslp101.inf until hfslip103.inf ... then it continued on from
hfslp200.inf until hfslp365.inf ... presumably all hfslp###.infs

... i've attached some files that might be useful from this run) ... checking i386 folders though in the cd shows all hfslp###.infs present
Well... I'm lost then. All files are in the new source, TXTSETUP.SIF and DOSNET.INF are instructing Windows setup to copy them over during txtmode copy, and HFSLIPWU.INF has the correct info to install them. I don't know what could be wrong with your set up, and especially why all of the sudden the HFSLP200~ files cannot be found by Windows setup either.
QUOTE (Kiki Burgh @ Mar 5 2007, 04:53 AM)

QUOTE (Tomcat76 @ Mar 5 2007, 06:36 AM)

For DNF30.exe, you should've seen the installation dialogs pass by (Windows Presentation Foundation, Windows Communication Foundation and Windows Workflow Foundation). If you've seen these, was that at T-13 or at first GUI logon?
these all came up after window to register ...
OK. Did these .NET 3.0 components take a while to install?