Tomcat76

WindowsMedia-Q828026-x86-ENU.exe is out of place here. That update is obsolete for Win2K and is the only one from your list that may interfere with the proper slipstreaming of the rollup, though the binary in question (msdxm.ocx) is older than the one in the rollup so HFSLIP should've kept the newer one. Either way, if removing WindowsMedia-Q828026-x86-ENU.exe doesn't help you should try installing without WINNT.SIF once. You're missing two security updates, btw. Don't know if that's important. KB917537 and KB926247. Edit... Does xpicons_silentv2.ex_ replace any binaries that exist in the rollup?

Did your motherboard come with a floppy with drivers for the hard disk controller? It may be that Windows doesn't recognize it.

This is the source of your logagent.exe and KB917008 problem: CDTAG - undefined You MUST have the CD identification files in your SOURCE folder, else copying of logagent.exe and other files will fail. These files are copied at a later stage during Windows setup because most of these have to be placed in the Program Files folder which can't be done from TXTSETUP.SIF. MDAC 2.8 SP1 and the hotfix go in HF (remove the MDAC 2.5 SP3 updates). You can also put MPSetup.exe and the Roots update in HF. They are all slipstreamed. You should also remove all obsolete updates. Check the_guy's Windows 2000 list in this forum or my Windows 2000 list (linked from my signature) if in doubt. See if WU still complains about the rollup after fixing the above.

Hi there. Welcome... Can you provide a copy of your HFSLIP.LOG file (zipped)? 7008 patch? Why would you put it there? The second version of UR1 works fine. HFSLIP hasn't deleted that file in several months. Not sure what you're doing here. HFSLIP 1.5.0 slipstreams MDAC 2.8 SP1 + hotfixes. Did you place these files in the correct folder?

I'll notify TAiN of this.

Can you burn a CD/DVD and try it like that?

The latest test release removes SOURCE\I386\SVCPACK if the source is considered "clean" otherwise. This is reflected in HFSLIP.LOG but it says "INFO" instead of "WARNING" to shush the paranoid (SOURCE\I386\SVCPACK is not removed if the source was patched with USP5)

Latest test release: if no IE updates are present, HFSLIP force-adds the compatibility flag that was added by KB890046.

I mean, KB890046 adds the following into the registry which KB920213 doesn't: HKLM,"Software\Microsoft\Internet Explorer\ActiveX Compatibility\{F5BE8BD2-7DE6-11D0-91FE-00C04FD701A5}","Compatibility Flags",0x00010001,0x400 However, that is added to the registry if you include either IE7 or the cumulative update for IE5 or IE6. So I don't feel the need to hardcode it into HFSLIP as well...

The newer SP2 disks install a non-public IE6 update from SVCPACK. The existence of the SVCPACK folder causes HFSLIP to trigger the warning. The reason I haven't come up with a solution for that yet is because, if that update is not installed (which happens after running HFSLIP) and you don't include the latest cumulative update for IE6, you get tons of errors reported in setuperr.log. So I don't want to simply ignore the existence of the SVCPACK folder as a whole. Instead, the warning message needs to be different.

1) Are you referring to the "ActiveX Compatibility" setting for F5BE8BD2-7DE6-11D0-91FE-00C04FD701A5? That's dealt with through the installation INFs from IE7 and the cumulative updates for IE5 and IE6. 2) Does it appear on Windows/Microsoft Update?

OK. That works The VM froze as soon as I hit Apply. I closed the VM window and started it again... It's now freezing a few seconds after login. If I move the cursor in front of the Windows Taskbar, I get this Vista animated graphic for what used to be an hourglass in earlier versions of Windows. 5 minutes later, it's still frozen. Here's a screenshot of what's visible (or what is not)...

Thanks for the reply. Maybe there's a problem with how you're checking if .NET 2.0 is installed. The settings panel got installed even though I didn't have .NET 2.0 installed. Instead, after installation of the Vista Pack completed and after rebooting, I tried to open the settings panel but got an error message saying that I need to have .NET 2.0 for this to work. So it does get installed regardless of whether .NET 2.0 is installed or not. Maybe because I had .NET 1.1 installed? Either way, the settings panel worked fine after installing .NET 2.0. I forgot to mention last time that I tried this in a VM. Maybe that has something to do with it too.I'll reinstall the Vista Pack to comment on the rest.

I mean an AV running while the CD is being burned. Of course there's no AV running during txtmode copy.... I don't remember how VMWare does it, but MS Virtual PC remaps hardware to basic hardware (S3 Graphics, SB16, Intel NIC, etc). That could be why everything appears to be fine in the VM. Have you tried letting nLite create an ISO of the SOURCE folder to see if the problem occurs like that too? Of course you won't get any copy errors but is the Properties button on the Monitor tab still disabled? Have you tried not using nLite to create the ISO? Everything seems OK with the files you attached. I'm not sure if the files with long names will copy fine if you initiate the install from Windows, though.

The only difference between those files is the addition of the Microsoft Update shortcut to the Start Menu from HFSLIPWU.INF. I'm sure that's not the problem but you can test it by removing MUWEB_SITE.CAB from HFCABS (or just swapping the HFSLIPWU.INF file). Can you verify that both SOURCESS folders contain the same amount of files?

That's an awful lot of hotfixes you're slipstreaming. Concerning those updates which don't appear on Windows Update, I have to say that by "supported" I mean that HFSLIP does what it's supposed to do: replace existing files and make the necessary changes to the registry. I don't have the time to actively test them on different systems so I can't say if any of those is buggy. Also, since the majority of them are non-public, they aren't tested as much as the public hotfixes which makes them more "vulnerable" to errors. What could also be the case is that the disabled Properties button is an intentional or known side effect of one or more of those extra updates. Personally, I think that the problem lies with the media you're using to install Windows on your host PC. This includes a bad CD/DVD, a bad CD/DVD-ROM drive or controller, a program burning the disc the wrong way or an anti-virus application preventing the CD from being burned properly. Which burning program are you using? Are you importing the ISO image or are you letting the burning program take care of making a CD bootable? Have you tried disabling your anti-virus?

Are you presented a dialog where you can provide the location of dotnet2.exe? If so, what happens when you point it to I386\SVCPACK on the CD?If this is a network install, that's probably the source of the problem. In that case, please give me a copy of HFSLIP.CMD in SOURCESS\I386\SVCPACK.

Those files are part of IE7. Can you verify that advpack.mu_ and ieframe.mu_ are present in SOURCESS\I386 and on your new CD/DVD? Can you ZIP TXTSETUP.SIF and HFSLIPWU.INF from SOURCESS\I386? >> also, i couldn't install drivers for my monitor once setup was complete. I suppose you mean the video card drivers. Which video card/chip are we talking about? What's the exact problem? Do you get a successful install message at the end of the wizard (if you're using that)? Do you get an error message?

Can you give me following files from both runs (SOURCESS\I386)? SVCPACK\HFSLIP.CMD DOSNET.INF DRVINDEX.INF HFSLIPWU.INF SVCPACK.INF SYSOC.IN_ TXTSETUP.SIF

I know it's full... I'll deal with it later... Thanks for the info.

Well... I asked about RC8 because, between v1.4.5 and 1.5.0, nothing was changed that affects driver installation. The only change from RC8 to the 1.5.0 final was the addition of the Microsoft Update shortcut in the Start Menu so if RC7 works RC8 should be the one that introduced the bug for you. Are you using different HFSLIP work folders for RC7 and 1.5.0 final? Did you run RC7 again to verify that it's really working or did you just install from an already existing SOURCESS folder (or ISO)? Personally, I'm wondering if this is really an HFSLIP issue. When I connect a new SATA drive in my computer and start a non-HFSLIPped Windows, I'm also asked to "reboot for the changes to take effect"...

Do you have the same problem with RC8?

I have tried out v1.3.8 for fun and have some comments. Don't know if they are useful... 1) The Vista Pack 2000 Settings panel (XPize Settings panel) requires .NET 2.0; you should mention that. 2) Settings in XPize Settings panel don't stick (even after checking the box to the left of the setting I want to change and checking "Load on startup" under the Misc tab). What I change here (on every reboot, for now) is the transparency of the text on desktop icons. 3) The entire Windows Taskbar has the Windows 2000 style. After some searching, I found something to enable skinning in the TClock3 Properties panel (last tab), but that only gives me icons on a black background and there is no Start Menu icon; I see that it gives me the option to skin it with backgrounds myself but where do I find these? 4) [bug?] Changing the "Show icons using all possible colors" in Display Properties > Effects first causes the quality of all icons to worsen and my customizations in the XPize Settings to reset. After a reboot or after a relogin, all icons except those in UI toolbar buttons are missing and I haven't found a way to get them back. Uninstalling Vista Pack 2000, the icons are still missing. 5) The Segoe UI font is not applied to title bars; is that by design? 6) In System Properties, I get a button "Gebruikersinformatie". Why does this button show? It wasn't there before and it shouldn't be there on a regular install. 7) In Display Properties, Web tab, the picture within the computer monitor graphic exceeds the inner boundaries of the monitor graphic. 8) Is it possible to include important information in the main post of this thread? That way, (new) people don't have to read through numerous pages possibly containing obsolete information...

In principle, you don't need IEAK7 for this. You can create your own install.ins file and cab it into BRANDING.CAB. Expand INSTALL.IN_ from SOURCE\I386 and open in Notepad. This is only to see how it's done. Don't use it as a base. Expand the main IE7 installation package and open install.ins in Notepad. Make your changes in there, based on how it's done in the one from SOURCE\I386. It's pretty much the same as what you do in WINNT.SIF. Compress your customized install.ins into BRANDING.CAB and place it in HFCABS.

@CharlyBrown Are you also using "BrandIEUsingUnattended"?