Tomcat76

Hi ZileXa HFSLIP and the RVM Update Pack more or less do the same: they replace existing files. You can let HFSLIP handle the RVM Update Pack if you want (place it in HFAAO), but remember to remove any hotfixes from HF that are already covered by the Update Pack. The difference between HFSLIP and the Update Pack is that HFSLIP puts you in charge when deciding which hotfixes to include and which not. The Update Pack is an "all or nothing" thing. Some people prefer the flexibility while others prefer to download one package (the Update Pack) instead of several smaller ones (hotfixes). To my knowledge, nLite integrates standard hotfixes into SVCPACK, yes. But don't take my word for it. When using nLite after HFSLIP, you need to be careful not to remove certain files. FDV has more info on his site: http://www.vorck.com/hfslip-info.html#nlitekeep

They are already in that folder per your DOS command...

@Camarade Those two folders (and any other irrelevant tag folders) should be removed now when using 718exp1. I'm not sure if this will fix your problem, though. I find it quite a coincidence that Windows setup trips over the exact same file that's also in pconfig. Earlier versions of HFSLIP always removed pconfig so that's what 718exp1 is doing now too. If you still get the installation error, I'll copy pconfig into ASMS.

You could call it like that, yes.

No; support for FORCEXPIZESVC was removed.

I'll bet that's the problem here too.

You need admin priviledges to do an "admin install" of MSI packages, which is what HFSLIP is doing to obtain the needed MSXML files coming from *.msi packages. That explains everything. Neither MSXML3 nor MSXML6 were processed because you aren't running Windows with admin rights while running HFSLIP. If you'd use the MSI package of MSXML4 too, you'd have the same problem there.

Tomalak --- I checked it out on XP Pro German with only these two files in the HF folder: msxml3.msi WindowsXP-KB835935-SP2-DEU.exe The MSXML3.DL_ binary gets updated. Are you running HFSLIP while logged on as an administrator? If so, can you verify if it gets updated for you when you use only the above two files? You don't need to do a test install; just look at the file date.

I'll check it out, Tomalak.

I'll try to find out on the XPize site if the slipstreaming procedure was changed recently. Did you attempt a non-nLited HFSLIP installation as well as a non-HFSLIPped nLite installation to make sure it's HFSLIP's problem?

Hi xper. Would it have anything to do with the issue discussed in a previous topic?

Hi Muppet Hunter. I updated the HFSLIP code some time ago to have DX9c slipstreamed into Windows 2003 SP1 but removed it after some two weeks since noone seemed to care. I don't have this problem myself so I can't check if the solution works. I couldn't find the test releases from back then so I had to do it over again. Try the latest test release here: http://www.msfn.org/board/index.php?showtopic=69809 It now allows 2K3SP1 to pass through the filter; it also makes sure there are no duplicate entries in TXTSETUP.SIF and DOSNET.INF. Your dxdiag report is puzzling me, though. Why is it reporting that joy.cpl is missing when that file isn't installed for 2K3? The relevant line is commented out in dxnetsrv.inf and it's followed by the word "locked", indicating that it "doesn't apply"... So why is it complaining?

We eat chowder from time to time but I'm not sure on the ingredients. It's got cauliflower, meat, potatoes and some other stuff. No idea. So I voted "something else" to be on the safe side. Gimme scallops. The plural form is used intentionally... Voted "brunette/grey". Not because of the second color. It's symbolical for what's in between brackets, right? I'll keep using Windows 2000. I hope someone will have cooked up a perfect 2000-like skin for Windows XP or 2003 by 13-Jul-2010...

I changed it to 47. The blue one is OK but I think the red is important to show that it's experimental. BTW... The next update is going to be even more experimental, so that one will have to burn. What about yellow text on a red background? Just kidding...

You like 47 better?

That's good to hear. BTW... There's a new one...

I sometimes experience the opposite of gzduke's problem, where MPC can't properly play back MPEG1 video files (grinding background noise with hiccups) but WMP6.4 can. But this is not with your codecs-- I haven't tried them yet.

@Kiki Burgh: Technically, yes. The background color is different, though... @Camarade_Tux: No problem. I wish I had you in here earlier to see if XPSP1 is OK... BTW... I searched around the Internet a few days ago for "HFSLIP" in different languages and found a couple of forum posts from you. So thanks to you too...

Sh**. Thanks...

I think it's nice that the_guy's lists have a completely different approach to mine. Some people prefer it one way, some the other. I wouldn't remove them. My lists on this forum don't need to be here, but TommyP prefers to see them here too.

Everything appears to be OK with WinXP SP2. Does anyone know how XPSP1 is doing? After I hear back from TommyP, I'll make it a final.

OK. Thanks.

That one slipped right past me. OK... I changed HFSLIP so it checks for *.hp.* instead of *.hp.sys.

There are only two hotfixes ATM which have these *.hp.* files and they're all *.hp.sys files. I'm a bit afraid of making generic fixes *too* generic so I wanna hold off changing that to *.hp.* until there are more file types involved....

Looks like we got something to keep ourselves busy with during the holidays. // end sarcasm