Tomcat76

Updated again. I assumed a particular working folder would be empty when HFEXPERT stuff is processed so I used that, but apparantly it's not empty. This caused everything to be processed twice. Thanks Tommy. 60317b-expert

@TAiN I have reordered quite a lot in 60317a-expert. Hopefully everything works as intended.

I think I know what the problem is. Give me a little while... Edit: No. What I was thinking of is not the issue. Would you mind giving me the txtsetup.sif and dosnet.inf files from SOURCESS\I386?

Based on your post in the other thread it's clear that you don't have a proper CD tag file. Check in SOURCE\I386 if there's a file called SP1.CAB. If it's there, download the attached ZIP and extract the content into your SOURCE folder. You seem to be using Professional so I included the tag file for XP Pro SP1. If you don't have SP1.CAB, your source was never patched or wasn't patched properly.

That either means your source wasn't patched with a Service Pack or that the Service Pack wasn't properly applied (or you deleted the SP tag file by accident).

When asked for a path at the beginning of the HFSLIP program, what did you enter?

That's a weird message. Do you get that during Windows installation? I wonder what INF file is being referred to...

No problem, Wela. I learned something too. Thanks for the info, Axed. The picture is quite bad with TCPMP and the player itself could use some improvement (turn off Full Screen without pausing the video and open files on a different hard drive from File> Open file), but I experienced not a single hiccup playing a DivX movie and a 320kbps MP3 file. I'm gonna keep this one until I find a better solution. I tried those ffdshow builds you're talking of over a year ago. I'll give the latest version a shot.

If KB912945 got installed properly using HFSLIP_60315c.CMD then you don't need to test HFSLIP_60316d.CMD for that. The LegitCheckControl fix was updated again, though, so you can test it for that.

Uh... "fixed" after installing wga1b.inf or also "fixed" after installing Windows again with the updated HFSLIPWU.INF?

I'd like to release a new final this week when there are no issues with LegitCheckControl.dll and KB912945. Dziubek said all's fine with KB912945 but I'd prefer more confirmations. The HFEXPERT change will not be implemented yet. It still remains to be seen that there are no nasty side effects so it will only exist in a test release for now.

It is possible there's a typo in the line that fixes the LegitCheckControl issue but someone else said it's working so I didn't bother testing it further. Install the attached wga1b.inf when you're booted into the fresh system (right-click and choose Install). If that seems to do the trick, download the attached HFSLIPWU.INF into your SOURCESS\I386 folder (no need to run HFSLIP again), burn a CD and install again.

The most recent CD tag file is used by HFSLIP to determine the Service Pack level. It is important to know the Service Pack level in order to integrate the correct version of files in hotfixes (among other things). The CD tag file resides in the root of your installation CD and should be copied over into the SOURCE folder. If HFSLIP does not detect a CD tag file, it assumes that the Service Pack level is "0" or "Gold". Windows XP Professional SP1: win51ip.SP1 Windows XP Professional SP2: win51ip.SP2 Windows XP Home SP1: win51ic.SP1 Windows XP Home SP2: win51ic.SP2 Windows Server 2003 Standard Server SP1: win51is.SP1 Windows Server 2003 Advanced Server SP1: win51ia.SP1 Windows Server 2003 Datacenter Server SP1: win51id.SP1 Windows Server 2003 Web Server SP1: win51ib.SP1 This does not apply to Windows 2000. For that OS, it is assumed that the source is patched with SP4.

It doesn't matter. Any HFSLIPWU.INF that was created by a test release of HFSLIP. Give me the one from the latest sourcess that you installed.

Good catch, noomsybaby. I haven't tried Win2K ADV nor DCS yet so it hasn't occured to me either. Give me a minute or two to update the test builds in the other thread... @EmRoD: Can I have the HFSLIPWU.INF file from the SOURCESS\I386 folder?

My thoughts too, Murvun. @dziubek: Check 60316a when it's out. I'm working around this issue. When the author updates his/her addon, it will still work.

How's KB912945 doing? @dziubek Is everything OK with CDImageGUI?

Hi glentium Remove WindowsXP-KB904706-x86-ENU.exe. It's an older version of the other DirectX 9 hotfix you're slipstreaming (WindowsXP-KB904706-v2-x86-ENU.exe). Also, remove this file: WindowsServer2003.WindowsXP-KB904942-x64-ENU.exe. It is intended for 64-bit versions of Windows XP and Windows Server 2003. You're looking for WindowsXP-KB904942-v2-x86-ENU.exe. Edit: I recommend against including WindowsXP-KB912945-x86-ENU.exe for the moment. It appears that mshtml.dll (which is part of that package) can't be slipstreamed. You can use one of the test releases of HFSLIP where an attempt is made to work around the problem.

Hey... The HFSLIP community consists of more than two people...

I don't intend to break anything. Just let me know of potential issues and I'll see if they can be fixed. I don't think that the question should be "which comes first". It's more a question of "which is allowed to undo changes of which". In the previous releases of HFSLIP, HFCLEANUP (additionally) removes files that are added through HFEXPERT\WIN. Maybe I see it wrongly, but to me that totally nullifies the use of HFEXPERT\WIN. Why would one place files in HFEXPERT\WIN if they may be deleted? I think that the only interaction between them which should/could be allowed is to force-add files that are deleted by one or more reduction filesets. This way, you don't need to edit filesets to try out different things. The basic purposes are not changed: HFCLEANUP is used to remove stuff and HFEXPERT is used to add stuff. I'm only changing a con into a pro: Old con = HFCLEANUP removes files that are added through HFEXPERT New pro = HFEXPERT\WIN can be used (misused) to override decisions of HFCLEANUP

Isn't the purpose of HFEXPERT\WIN to just add files to the source... no registration, no special stuff done to them? Please note that I'm not talking about HFEXPERT\CODECS nor HFEXPERT\APPREPLACEMENT. These are "special". No installation INFs are created for files in HFEXPERT\WIN... Did I get this wrong?

Personally, I'm not using ffdshow either. It breaks everything... litterally. I get hiccups so often that it spoils the fun in listening to music. I tried it on both a "manually installed" Win2K system and an HFSLIPped Win2K system -- no difference. I use K-Lite Mega 1.50 now with the bare minimum: XVID, DIVX, 3IVX, MPEG4, OGG, Real & QT. Coupled with the regular WMP6 and WMP9 codecs, that gets me all I ever need. I still get breaks at times in DIVX movies but they are kept at a minimum because I disable post-processing and smooth playback. MP3 files are usually fine now that I don't install ffdshow, MP3, AC3 and ON2 filters/codecs.

I don't really know what you mean by "routine", but if you think I switched them around then I have to say I didn't. Everything is still in order. I always thought that the purpose of HFEXPERT\WIN was to add files, and the purpose of HFCLEANUP to remove files. This apparantly wasn't the case as TAiN found out. IMHO, I think it's illogical that HFCLEANUP removes stuff you add through HFEXPERT\WIN. It defeats the purpose of HFEXPERT. All I did was fix this "collision"... I'll undo it if you still want it...

Just an FYI... These files are not parsed by HFSLIP when dealing with Windows XP: BDA.cab BDANT.cab These files are not parsed by HFSLIP at all: Apr2005_d3dx9_25_x64.cab Aug2005_d3dx9_27_x64.cab Dec2005_d3dx9_28_x64.cab Dec2005_MDX1_x86.cab Dec2005_MDX1_x86_Archive.cab DirectX.cab dxdllreg_x86.cab dxupdate.cab Feb2005_d3dx9_24_x64.cab Feb2006_d3dx9_29_x64.cab Feb2006_MDX1_x86.cab Feb2006_MDX1_x86_Archive.cab Feb2006_xact_x64.cab Feb2006_xact_x86.cab Jun2005_d3dx9_26_x64.cab Oct2005_xinput_x64.cab Oct2005_xinput_x86.cab I'm still not convinced you have the CD tag file in your SOURCE folder.

I don't know for sure, but if you can't play this video you need them: http://www.jengajam.com/r/Ballmer-Sells-Win1