Tomcat76

Sorry... I didn't see this earlier. KB923191 for Win2K with IE6 is not supported by the current "final" version of HFSLIP. This is one of those special hotfixes which contain one or more separate files for Win2K with IE5 and Win2K with IE6; the files for Win2K with IE6 are in a subfolder called "xpsp2_binarydrop". The problem with this hotfix is that the file in xpsp2_binarydrop is about two hours older than the file for Win2K IE5. Version 60810 of HFSLIP only overwrites the files intended for IE5 if the IE6-versions are newer. That problem is corrected in the current test releases.

@Wela: Nevermind. Try 61017b. @Kiki: What Super Magician said. But that switch had nothing to do with SVCPACK installs; it was for the internal HFSLIP hotfix filter that distinguishes between Type 1 and Type 2 hotfixes; they need to be handled in different ways. Either way, it doesn't matter because it's removed again with 61017b. @Oleg II: To be precise, KB888111 is slipstreamed but with the current final (60810) it needs the word "Windows" in its name for it to be detected properly.

OK, Wela... Can you please do this: Run 61017a. While the hotfixes are being processed, you should see HF.TXT, HF1.TXT, HF2.TXT and HF2T.TXT in the main HFSLIP folder. Copy them to another location before they are deleted. Then ZIP them up and post it here. Thanks...

I can't confirm this. Are you using any unsupported hotfixes?

@retalv OK... Test version 61017a is treating these obsolete updates as Type 2 hotfixes. Should fix your problem.

Not all test releases Those updates are obsolete. Please use IE6.0sp1-KB925486-Windows2000-x86-ITA.exe and WindowsXP-Windows2000-Script56-KB917344-x86-ita.exe.

Please read my previous post.

It's done (61016a). Also, nothing is added to DOSNET.INF if it isn't detected. This also applies to HFEXPERT\DRIVERCAB.

Yeah, I've read some articles on the time zone change too. It's been like that for a few months already. BTW... "T-13" is not exactly right. The change is implemented when SYSOC.INF gets processed; I think that's T-19 but I'm not sure.

Seeing the post by Glentium, I wanna propose the following (for HFSLIP): SYS files > 1,,,,,,3_,4,1,,,1,4 INF files > 1,,,,,,,20,0,0,,1,20 other files > 1,,,,,,,2,0,0,,1,2

@Wela: run dxdiag.exe from the Run box and wait till the blue boxes go away. @Kiki & Bugs Bunny: your problems should be fixed with 61015b

I saw a problem with DX9 slipstreaming which only affects Windows 2000. I fixed it up and will now check in a VM if it solves the dxdiag problem... BBIAB...

@Bugs Bunny: I can confirm this. Are you sure it doesn't happen with the latest stable release?

Concerning the Sri Lanka update... Just copying the binary doesn't do it. It's actually nothing more than a "helper file". Kiki (or anyone else)... Do you know if the time zone change from 6:00 to 5:30 is temporary or permanent? If it's permanent, I'll just hard code the two necessary registry changes for everyone and you can ditch the update. @Bugs Bunny... I didn't run into that problem but I'll check it again.

Using 61015a, fsdkreboot.exe and cstupd*.dll are deleted and srilanka06.dll is temporarily renamed to slanka06.dll (given back original name during textmode copy of Windows setup). Will check later if this is enough for srilanka06.dll.

Using 61015a, non-SYS files are compressed into SOURCESS\I386 and added into TXTSETUP.SIF with "1,,,,,,3_,4,1,,,1,4" and into DOSNET.INF.

The next version will delete cstupd1394sidspeed.dll. The Sri Lanka time zone update is a strange hotfix. The installation INF does not contain information as to where the srilanka06.dll file should go and if anything else should be done with it. I'll have to test this in a VM. There's nothing wrong with WMC 2.0. HFSLIP doesn't extract it so the fsdkreboot.exe file does not come from that application. It must be another Windows media update that isn't on our lists. Maybe I'll just delete the file since we aren't doing anything with it anyway.

And there's a problem with CopySendAddons_1.1.7z. Where can I find it? @the_guy HFSLIP doesn't extract WMC 2.0 so it must be something else.

Kiki... Where do these files come from? cstupd1394sidspeed.dll fsdkreboot.exe srilanka06.dll

Using "1,,,,,,_x,4,1,,,1,4" or "1,,,,,,,_x,3,3"?

Oleg... Situation in 61014c: 1) Multiple INI files are accepted; they should start with "STORAGE" and end with the .INI extension. Long file names are accepted but spaces are not. Examples: STORAGE.INI, sToRaGe1.iNi, STORAGE999.INI,... Their contents are copied into TXTSETUP.SIF 2) SYS files are compressed into SOURCESS\I386, and entries are added in TXTSETUP.SIF and DOSNET.INF 3) Other file types are merely copied into SOURCESS\I386 (uncompressed, and no references for them in TXTSETUP.SIF or DOSNET.INF)

Does it have to be in that order? It's going to be difficult to split STORAGE.INI. HFSLIP currently outputs in this order: 1-3-2-4. I'll see what I can do with support for multiple *.ini files. As far as "garbage" is concerned... Are only .sys files required? If so, I can hard code that into HFSLIP.

OK, Glentium... Check 61014a...

Should be fixed in 61014a. Thanks, both

Don't know what you guys are talking about. The [sCSI.Load] code has been in there since the beginning... ECHO>>WORK\SCSILOAD.TXT %%~nI = %%I,4 This is then copied into TXTSETUP.SIF. @Oleg II: I don't think it's necessary to have STORAGE.INI in HFTOOLS. I'll just have HFSLIP check for *.SYS files.