Tomcat76

I don't know... I never used another version than the one that comes with Windows... Whoops... I better check if it's still compatible then... I don't think so. Windows should just not check if a file is original so I guess the SFC_OS.DLL file you have is good. I never messed with SFC* files myself. Does anyone know this?

You're welcome

I wouldn't worry about this. SP2 has a similar problem with a DX9 file that doesn't contain a registry section even though the DX8 version of that file did. Windows setup still tries to register it even though it's not possible resulting in an error message being logged. I suppose your problem stems from Windows setup expecting the WMP9 versions of those two files.

I would start off by only including the updates listed on the site in my signature. Also use the latest final version or the latest test release (recommended) of HFSLIP to be sure.

Heheh... Or undo fixes two weeks after....

HFSLIP doesn't handle it? You get the "bad" TXTSETUP.SIF after including VistaCG? If so, please download the latest version of the VistaCG addon (it's now at version 1.0 but you're still using 0.98) and run HFSLIP again. After that, see if TXTSETUP.SIF still is 3.13KB large. I don't know this personally (I never used XPize) but other people say it's needed.

It's been a long time I used Nero; I forgot how it handles bootable CDs. I use CDIMAGE.EXE through a seperate batch file to make an ISO (the .BIN boot file is there too) and then burn the ISO with Sonic RecordNow DX 4.61. But I think any burning utility should be capable of handling ISOs... HFSLIP uses the /D switch on the XCOPY command which only overwrites files if the ones in the source location are newer. The file dates are checked, not the version numbers.

@Kiki I had a look at the other addons you mentioned (except Microsoft MakeCab v1.00.0601 which doesn't seem to be available anymore) and don't see a problem. Please use the latest test release (60503c at the moment). If you still get an error referring to "line 1" of TXTSETUP.SIF, I'll have to take a look at your TXTSETUP.SIF file.

@Kiki 60503b fixes the XPize problem. I also added something that alerts you which hotfix adds those extra folders. Please let me know which one it is. When you install KB888111 by hand, Windows assumes that you need it. I'll search around to see if it's really better to have Windows force-install it from SVCPACK. Everything should be fine with VistaCG (only checked version 1.0). I'll check the other addons you mentioned. Yeah... That's why CounterStrike isn't made for DOS...

@dziubek You have a couple of addons with spaces in their name. Are those the original names or did you change (or make) them yourself?

Hah... Well... Should I let HFSLIP extract the ISO, update HFSLIP.LOG and remake the ISO?

@Kiki: Themes_rytukz_VistaCG_addon_v1.0.cab (and other addons of that type) should be supported with 60503a... @TAiN: You mean that one reference to the HFSVPK folder? Updated.

There's still another way. Just rename it to WGA1.DLL and put it in HFSLIP\HFEXPERT\APPREPLACEMENT\. The only thing you'll need to be sure of is that the file is newer than the one coming from LegitCheckControl.cab.

Is qfecheck capable of detecting it? As far as I know, it is only installed if Windows setup thinks it's necessary. It's just a driver update. Are you having audio problems? Really strange. SVCPACK.INF doesn't contain the switches even though they are specified in XPize.txt. Can I have a look at your xpize.txt file?

I don't know what Rock Ridge is. Someone else should be able to answer that. What worries me more is the renaming of General_Settings.reg. What are the switches in your ISOconf.txt file? I see nothing wrong in TXTSETUP.SIF and SYSOC.INF, but if you're using switches that change files to 8:3 format you might get in trouble with UserPass2.inf. Also, note that HFSLIP adds file names into SVCPACK.INF representing the files in the HFSVCPACK and HFSVCPACK_SW folders the way they are called in there. If General_Settings.reg is renamed to GENER000.REG it won't be installed/executed. Can you delete ISOconf.txt and test again?

Something else. I see you got LegitCheckControl.dll in the FIX folder. Three comments: 1) It should be compressed with MAKECAB so the extension is ".dl_". HFSLIP only *copies* the files from FIX into SOURCESS\I386; it doesn't compress them. 2) In the current final version (60422), it should only be named "LegitCheckControl.dl_" if you include a LegitCheckControl executable (ie, a hotfix type). You are including LegitCheckControl.cab instead, of which HFSLIP renames LegitCheckControl.dll to WGA1.DLL so the file in your FIX folder should be named "WGA1.DL_" (makecabbed WGA1.DLL). 3) In the current test release and the upcoming final version, *ALL* files named LegitCheckControl.dll coming from either a hotfix executable or from LegitCheckControl.cab are renamed to LCC.dll for the sake of conformity. So the file in your FIX folder will have to be called "LCC.dl_" then (makecabbed LCC.dll).

You need to have either mkisofs.exe or cdimage.exe in the HFTOOLS folder. You didn't mention having it. Since March 27/28, HFSLIP no longer fetches the boot image if neither mkisofs.exe nor cdimage.exe are detected. There's also no point in getting the boot image if it won't be used by HFSLIP.

It at least gets rid of an error message appearing when a drive letter doesn't exist. As far as I know... yes.

It sounds logical... HFSLIP needs to check for the existence of an I386 folder before it determines that it's a drive containing the Windows CD. For that, the drive needs to be accessed...

I added the GOTO EOF to the GETBOOTBIN section in 60501a. Thanks. As far as the other problem is concerned... This can't be fixed. It's the same as when you double-click on a CDROM/ZIP/USB drive icon when there's nothing loaded in it.

I found it. It looks like DOS freaks out with some (not all) numbers that have a leading zero. It's worked around in 60430c.

It's supported but you'll end up with duplicate TXTSETUP.SIF and DOSNET.INF entries. You can use the latest test release instead; it's updated for MSXML3.MSI.

Is this VBS or something?

If it's this complicated I don't even feel like trying it. The best would be if the author provided advanced switches for silent installation just like for XPize...

I saw that once but it should've been fixed. I did some changes. See if you still get the error...