This is not an HFSLIP issue. There was a non-critical MSFT update for 100% svchost.exe probs. Sorry I don't a link or the KB number, but it was mentioned a few weeks ago on some MSFN board.

I have searched on the forum and, I discovered that, maybe, its depends on Windows Update/Microsoft Update, and the guilty probably is msi.dll library. 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?


P.s. Office Template and Media Control is updated.

This post has been edited by S3pHiroTh: Mar 5 2007, 08:03 AM

Thank you for the instruction.

When WMP11 is integrated in slipstreams, the phenomenon of OOBE's breaking is recognized, and solved by integrating WindowsXP-KB894871-x86-JPN.exe.

The last few test releases rename that file (as mentioned in the changelog). It's supposed to happen. From the INF file:

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.

OK. Did these .NET 3.0 components take a while to install?

OS install seems ok ... although i have no idea what possible repercussions missing almost all hfslp###.infs in my install now ... what could be its worst effects? ;( i hope we could resolve this ... thanks!yes it did ... quite sometime actually would this be bad?

No; this is normal, and it indicates that HFSLPGUI.CMD is executed at the right time. But .NET 3.0 is not in Add/Remove Programs afterwards?

great! dotnet3 is present in Add/Remove Programs ...

Now I'm confused. Didn't you say that .NET 3.0 didn't install?

it did ... it even has an entry in Add/Remove Programs

Tomcat, I've a request for you. Because some updates are not public and hard to find on the net (in os native language), I have put some files as MSOBMAIN.DLL (in italian, found in RyanVM italian package) in FIX directory because I don't find the respective hotfix in my language. In this way, after I have installed Windows, in setuperr.log, obviously tell me that msobmain.dll isn't signed well by Microsoft.
Can you add a directory for put in the cat files necessary for removing the error? Or can you tell me how can I do for removing that error?
I already tried to:
-copy the cat file in i386\svcpack of the source directory but it doesn't work (and it tells me that the source isn't clean)
-modified hfslip script that after it creates the WORK directory, it copies the cat files into WORK\SVCPACK directory but it doesn't work.

Any other method? Thanks for your answer and patience

Did you makecab msobmain.dll before putting it in the FIX folder?

You don't need the English version of the hotfix if you have the Italian files, btw. The INF file within the hotfix only adds info into the registry confirming that this particular hotfix was installed, something that would be necessary if KB898543 (or whatever hotfix the msobmain.dll file that you are using is coming from) appears on Windows Update, but Windows Update doesn't show it so all you need is the Italian msobmain.dll and the accompanying CAT file. Theoretically, it should work with the compressed DLL in FIX and the CAT in SOURCE\I386\SVCPACK; just ignore the warning about having an unclean source. But remove the English hotfix from the HF folder.

I have tried in this way, but in SVCPACK.INF file there isn't any entry about KB898543.cat file

EDIT: Someone know how to download kb925720 february update?

This post has been edited by S3pHiroTh: Mar 8 2007, 02:17 AM

here ya go. uploaded KB925720

http://rapidshare.com/files/20369612/Windo...86-ENU.exe.html

hi tomcat and tommyp, i was wondering since you've managed to slipstream the .net patch as well (KB887998) couldn't you somehow magically also try and slipstream .net 1.1 and 2.0 themselves into the windows source as well ? it would save a hell of a lot of time during the installation at T-13...

Where did you find the link for kb925720 february update? I need italian version.

This post has been edited by S3pHiroTh: Mar 10 2007, 11:40 PM

If you applied the update via Windows Update or Microsoft Update you should be able to find the link in C:\WINDOWS\WindowsUpdate.log.

I tried this some time ago but gave up on it because I was starting to go insane, haha.

Copying files is not an issue; it's more what goes in the registry and what commands should be run post-installation.

here's where I got it. here's where I've uploaded it.

maybe you could start with something like roguespear's switchless installer rather than the stock one and see how things go from there

This post has been edited by johndoe74: Mar 11 2007, 10:10 AM

The problem remains the same. There's no file that clearly states what needs to be added into the registry and which files need to be run post-installation.

Would u be motivated to do it if there were ? What i have in mind is you guys get in touch with one of the switchless addon makers, like for example roguespear or somebody/whoever makes the switchless addons on ryan's site. my guess is those guys might know what steps are involved in the installation and in what order. What do you think ? Worth a try at least ?