Tomcat76

@kontini KB928365 replaces the other .NET 2.0 updates. I checked the binaries inside. I'll update the instructions in the main post. @zedox I have never experienced that error message (even with other programs) and haven't got a clue what it means. Do you also get it when installing DNF30.exe by hand after Windows setup has completed? @mystek To be honest, those Event Log errors have always appeared for me when installing .NET 2.0 at T-13 -- even using others' silent .NET installers.

Non-public hotfixes are not as well tested as the public ones. You may experience problems installing them. Also, there may be some which are not supported by HFSLIP (because of an unusual or unknown internal composition, because files need to be renamed, because files need to be embedded in CAB packages existing in your SOURCE which are not yet covered by HFSLIP, or because files need to be copied into a non-standard location on the hard disk during Windows setup). Test at your own risk

I suggest you bring this up in the XPize forum, although I'm not 100% sure XPize is supposed to be compatible with a source that has IE7 slipstreamed into it.

Weird. I just tested this myself and it's working for me too now. I did do a couple of runs with IE7 slipstreamed occasionally but haven't checked transparent PNGs recently. The only thing I'm really doing differently nowadays is taking advantage of the HF\BASIC and HF\NOREG folders. I can't think of anything else -- at least nothing HFSLIP-related.

There's a new roots update for XP/2K3.

Its time stamp is July 9/10. You can get it here.

I think it's either winnt.sif or XPize. Can you try a run without those two?

Agi.... I could be wrong, but that doesn't sound like sweet-talk to me....

Can you show me your HFSLIP.LOG file? Have you tried without TCPIP.SY_ in FIX? BTW... That's 70722a; not 70222a.

Topic moved.

I don't have the uncompressed sfcfiles.dll in my source. That info on FDV's site is way obsolete. HFSLIP hasn't deleted halmacpi.dll and scsiport.sys anymore in well over a year. Removal of scsiport.sys was abandoned shortly after v2 of the rollup was released and halmacpi.dll is kept since ~December 2005 combined with the inclusion of the omitted reg hack for HT/dual core CPUs.

Windows setup doesn't like to see a modified LAYOUT.INF. System File Protection needs to be modfied/disabled for this which is what I don't want HFSLIP to do. TommyP may have a different take on this but I won't do it. I'm sorry.

Also gut... Machen wir einmal auf Deutsch... Verschiedene Sachen in dein HF-Verzeichnis sind gar nicht unterstützt von HFSLIP. Bitte brauche meine Windows 2000 Update Seite damit du weisst, was wohin geht und was völlig entfernt werden soll. Es ist ganz einfach: zuerst markierst du unter "Update your Windows 2000 configuration" was du extra integrieren wolltest, und dann vergleichst du die Liste unten mit was du bereits im HF-Verzeichnis hast. Regel: Was nicht in meine Liste vorkommt, ist möglicherweise nicht unterstützt, so z.B. dxwebsetup.exe und Journal-setup.exe. Verstehen wir uns schon besser?

That's interesting. Do you have both files in your original source too? If so, I suggest you remove the uncompressed one. Those two hfsec* files you mentioned are a bit of a mystery. They are supposed to be run at different stages but there are no multiple installation stages in a slipstreaming context. I deliberately ignored the installation commands so nothing wrong can be done. There are no errors during Windows setup, WU is clean and (most importantly) Windows is running fine, so I left things like that. HFSLIP also ignores ris.vbs. As far as I can see, that file is useless because the "NullSessionPipes" registry entry already has the intended value and the OE 5.5 string doesn't need to be updated for Q823353 (cumulative Outlook Express update from July 2004 which is embedded in the rollup update) because the string updates are no longer required (they were when IE and OE updates were released in Type 2 format).

That's strange. Version 5.0.2195.6717 is the original 2K SP4 file. Can you check in SOURCESS\I386 immediately after running HFSLIP that SFCFILES.DL_ was updated? It should have the current date/time.

Your list looks OK to me, except for Windows2000-KB917344-56-x86-ENU.EXE but that's due to an error in my hotfix list. I just fixed that. But that's certainly not the source of the problem. Can you tell me the exact size in bytes for the rollup update you have (right-click and select Properties)? It should be 32 724 472 bytes. If you have WinRAR or 7-zip installed, also right-click the rollup update and select "Extract to Windows2000-KB891861-v2-x86-ENU\". See if an error message is displayed while doing so.

As I said, the HFSVCPACK folder is for installers that don't require installation switches. Otherwise put: the original .NET installers, language packs and updates are not supported. If the "Microsoft" entry pops up in the new TXTSETUP.SIF even after removing the .NET Framework installers, you have slipstreamed an unsupported hotfix. Please attach a zipped HFSLIP.LOG file.

It wasn't supported before HFSLIP 1.6.0 but it is now. I forgot to update my hotfix list.

I wouldn't do that. As I mentioned some time ago in another thread, this is one way to see if the main INF file was executed properly. For this reason, I prefer not to give an answer file option to not have this created. If you still want this out.... The easiest way is to place a .reg file in HFSVCPACK before running HFSLIP containing: REGEDIT4 [-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\HFSLIPTotalSlipstream]

If you know how InstallRite works you can use that to find out what should be done to satisfy Windows Update in your case. Just put the hotfix in HFSVCPACK_SW1 if you don't.

I meant: are you installing IE7 manually afterwards (or installing it via Windows Update)? The hotfix you have placed in HF is for IE6, so, if IE7 is installed afterwards, Windows Update will ask to install the IE7 version of KB929969.

Thanks It's pretty simple. Just click the Change/Remove button and it will be removed immediately.

They aren't supported. I don't know where the files that are updated are located in the source.

Not really different, but they would be treated as Type 2 hotfixes. I'll need to check how they are composed on the inside to see if it's worthwhile having HFSLIP treat them as Type 1 hotfixes.

Are you installing IE7 afterwards?