Here's a new experimental release featuring complete WMP10 slipstreaming. This release is safe to use on Windows XP SP2. No more features will be added for Windows XP for the release of HFSLIP 1.0.

WMP9 and IE7 are a PITRE (don't ask ). This might take another while to complete and may not make it into the next final. The WMP9 code is still in (which is why the script is much bigger) but it's "locked". MP6 codecs slipstreaming is possible now too but it's still untested.

hi TP & TC & everybody! my apologies if i haven't been around lately to do some tests ... believe me i miss posting too ... however i underwent a lot of things lately (i.e., i was down for a week since i was sick but had relapse & was down for another week ... my pc broke down recently where i might have to change power supply, heatsink fan & video card ... & lastly Manila was hit by a strong typhoon that rendered the country without electricity until today ... he! he! tough luck!) ... as soon as i can ... i would be back to the vice of doing tests for XP SP2 ... cheers to all!

This post has been edited by Kiki Burgh: Oct 1 2006, 03:27 AM

Nice to see you back, Kiki. Hopefully the recovery is going smooth

You can safely unleash your powers on the current test release (hfslip-1.0b-61001a) but you'll probably use the HFSLIP 1.0 final by the time you get things up and running again. These releases should be right up your alley, hehe

Just a little FYI concerning WMP9 slipstreaming...

I'm still not sure if it'll make it into the next final. The thing that screwed up the Windows install was the file "PidGen.dll". This file is supposed to end up in the Windows Media Player folder but the Windows installation source already contains a file with that name. I had to give it another name and give it the correct name again during the copy process of Windows installation.

These problems remain (in an internal build):

a) The WMP9 shortcut is in the Start Menu but it doesn't work. The "Target" path is specified and is correct but the "Start in" path is blank and that's the problem.

b) The shortcut that's created in the Quick Launch bar after you go through the WMP post-install wizard (double click wmplayer.exe in the WMP application folder) also doesn't have the "Start in" path specified, making this shortcut useless too.

c) During Windows installation, you get an "Advanced INF" popup asking for the location of "Program Files\Windows Media Player" where you need to click OK (the correct path is already specified in the box). This comes from roxio.inf which uses a combination of "custom destination" and a regular string to get the WMP directory path (this is for a registry entry). I may need to have HFSLIP hardcode the reg entry beforehand and strip the relevant section out of roxio.inf.

d) WMP9 doesn't see the playlists even though they are in the correct location and the appropriate reg key is set. I may be looking for them in WMP in the wrong location, though: I click the arrow next to the "Now Playing" button and then mouse over "Auto Playlists"; is this where they are supposed to be shown in WMP9?

This post has been edited by Tomcat76: Oct 3 2006, 09:49 AM

Tomcat, I don't get why another copy of PIDGEN.DLL is required for WMP installation. The file is used by Windows Setup to verify the product key entered during setup and generate a Product ID.

I guess WMP probably uses this different version for generating an internal PID (which you see on the About screen). Hmmm...

Doesn't really matter. Temporarily renaming the file works around the issue.

I fixed the problem with the "Advanced INF" popup. There's an error in the "custom destination" section of roxio.inf: MS forgot to add ",5" to the end of one of the lines in there. HFSLIP (61004exp) is now stripping out that section and rewriting it the proper way.

This is just like codecs10.inf from WMP10 and wmfdist95.exe from both the KB891122 and KB900325 hotfixes... That file is trying to copy "codecs.10" into the INF directory and this hasn't been fixed in like two years...

The problem with the shortcuts was my doing. I now removed the silent Adobe Reader, .NET 1.1 and JRE 5u8 installers from RyanVM and stripped this out of my custom .REG file:
So one of those was responsible. My guess is that it's the registry entries, heheh. So be aware that modifying the registry with those entries (at least beforehand) will break the shortcuts to WMP9.

The problem with the playlists is still a mystery...

This post has been edited by Tomcat76: Oct 4 2006, 10:26 AM

XPSP2

Tried using hfslip-1.0b-61003a and am getting in the dos copy phase "can't find playlist.inf" (total wmp10 integration?). Then during graphical phase I get popup of missing "C:\WINDOWS\HFSLIP\playlist.inf" (Advanced INF Install) at T-13. Thought it was merge / no merge options, but just tried again with option A (previous try option D). same results.

As I was posting this looked over and saw that you released another version. Will try that unless there is any files that I should up for you to look at.

This post has been edited by NtegrA: Oct 4 2006, 02:10 PM

NtegrA: The new version won't necessarily fix your problem. Only changes to WMP9 slipstreaming were made.

Is PLAYLIST.IN_ present in the I386 folder of the new source?

If it's in the new source then 61004b should fix it.

Hmmm...I find it amusing that 61001a was 141 KB and 61004b is back to 147 KB !

Sorry for the delay, I was done for the day. (should actually be a YAWNING smilie)

yes. it is there.Giving it a go right now. will let you know in a few hours how it went.

11am:
YOU ARE DA MAN! (as always). Build completed 100% no errors.

This post has been edited by NtegrA: Oct 5 2006, 09:28 AM

WMP9, ya know...


Nice

I know HFSLIP recently added support for MSXML2, but I have 2 questions:

1)If I were to slipstream MSXML 3 SP7 on 2000/XP (2003 SP1 includes it), would I have duplicate entries in txtsetup.sif/doesnet.inf?
2)Is KB832414 supported for MSXML 2.5 on 2000 SP4 (included in XP SP2 (not sure about SP1) and 2003 SP1)?

Other that that, Looks great Tomcat.

the_guy

Seems we're pretty much ready for a new final - especially since we haven't released one since August!

But, I guess we should wait until AFTER October 10 .

Don't see why. The file names are different: msxml2.dll and msxml2r.dll vs. msxml3.dll and msxml3r.dll...

It is now...

I prefer to have some more test results come in...

This is a good way to test how well the renewed HFSLIP script does...

@Tomcat: I just read my question, and it doesn't apply to 2000 as 891861 is what introduces MSXML 3. What I meant was, XP SP2 includes MSXML 3 SP5, and if I were to slipstream MSXML 3 SP7, would there be duplicate entries? They both include msxml3(a/r).dll.

the_guy

Your posts are getting confusing. I'll clarify....

Win2K has:
- MSXML 2.5 version 8.0.6730.0

Win 2K can be upgraded to all of these:
- MSXML 2.5 version 8.0.7002.0
- MSXML 2 SP6 version 8.30.9531.0
- MSXML 3 SP7 version 8.70.1104.0
- MSXML 4 SP2 version 4.20.9828.0
- MSXML 6 version 6.0.3883.0

WinXP SP1 has:
- MSXML 2.5 version 8.0.6730.0
- MSXML 2 SP? version 8.30.8709.0
- MSXML 3 SP3 version 8.30.9926.0

WinXP SP1 can be upgraded to all of these:
- MSXML 2.5 version 8.0.7002.0
- MSXML 2 SP6 version 8.30.9531.0
- MSXML 3 SP7 version 8.70.1104.0
- MSXML 4 SP2 version 4.20.9828.0
- MSXML 6 version 6.0.3883.0

WinXP SP2 has:
- MSXML 2.5 version 8.0.7002.0
- MSXML 2 SP? version 8.30.9529.0
- MSXML 3 SP5 version 8.50.2162.0

WinXP SP2 can be upgraded to all of these:
- MSXML 2 SP6 version 8.30.9531.0
- MSXML 3 SP7 version 8.70.1104.0
- MSXML 4 SP2 version 4.20.9828.0
- MSXML 6 version 6.0.3883.0

Win2K3 SP1 has:
- MSXML 2.5 version 8.0.7002.0
- MSXML 2 SP? version 8.30.9528.0
- MSXML 3 SP7 version 8.70.1104.0

Win2K3 SP1 can be upgraded to all of these:
- MSXML 2 SP6 version 8.30.9531.0
- MSXML 4 SP2 version 4.20.9828.0
- MSXML 6 version 6.0.3883.0


No; HFSLIP only adds entries in TXTSETUP.SIF and DOSNET.INF for new binaries, not updated binaries.

What I mean is:
I have XP SP2 in my source folder. It has MSXML 3 SP5. I put MSXML 3 SP7 in to be slipstremed (msxml3.msi in HF). Will I have d1,msxml3.dll showing up twice in my dosnet.inf? That's what I meant. That list you posted is quite good, thanks Tomcat.

the_guy

Doesn't this right here answer your question quite clearly??