Tomcat76

Hmm... It looks like it's HFSLIP after all. But this dates back a very long time... Funny that noone ever came across this problem before. See test release 60518b

Because the Classic.wmz handling was taken out. It's in an external file now Let us know how it goes with the CD...

No, but here's a general note for you: you don't need to include everything that's available; just take whatever you need.

Found the prob. Sorry... (60518a)

Can you do this: 1) Get the latest internal build 2) Download cabsdk.exe, get EXTRACT.EXE out of it (it's in the BIN subfolder) and place it in HFTOOLS 3) Remove hotfixes that are included in the RVM Update Pack 4) Remove duplicate addons See if you still get the "File not found" messages.

Please try the latest test release and verify that the hscxpsp1.cab line is still in the generated txtsetup.sif. As far as "WMPClassic" goes... What value did you set it to? If it's "1" (the default), HFSLIP 60510b will only instruct Windows setup to copy over classic.wmz if it exists in the original source. This variable has no effect in version 60517a.

HFSLIP would ignore their presence, yes.

OK. The new version is there...

I don't know, but wouldn't it work if the relevant line was removed from SYSOC.INF prior to making the CD? IEAccess=ocgen.dll,OcEntry,ieaccess.inf,,7

These lists are for HFSLIP and HFSLIP doesn't support XP Gold. I don't know about TommyP but I don't support service packs that are no longer supported by Microsoft. In the same vein, I'll stop updating my SP1a list and will stop adding "fixes" for SP1a hotfixes on November 14, 2006 (unless MS extend support for SP1a again).

Problem in the handling of SWFLASH.CAB on non-English systems (to be more precise: those languages for which the swflash.inf in the original Windows XP source is in Unicode format). This will be worked around. Does SWFLASH.CAB integrate properly on English systems?

Oops. Reload...

HFSLIP does a generic fix, independent of the hotfix that contains webvw.dll. The only way I can imagine this wouldn't work is when HFSLIP fails to detect that your OS is a non-English Windows 2000. Can you check in SOURCESS\I386 that you have a file called webvw2.dl_?

Yep. Whatever you saw is an internal build. You can do that if you prefer. I figured double-clicking the answer file would be easier. But don't talk about the undocumented, OK?

As it stands now, there won't be two versions. But it will take a while before you'll see the next version. TommyP and I are cleaning up the code and it's taking some time. He hasn't seen it in months so I need to explain quite a few things, hehe.I hope we can get a test release out soon because I got a surprise for the WinXP users...

WINDOWS ==> HFEXPERT\WIN WINDOWS\SYSTEM32 ==> HFEXPERT\WIN\SYSTEM32 WINDOWS\CURSORS ==> HFEXPERT\WIN\CURSORS WINDOWS\FONTS ==> HFEXPERT\WIN\FONTS etc.

Misunderstanding

Hi! Adding support for it (an SVCPACK install) is trivial but I need to run this by TommyP. I'll run this by TommyP too I'd prefer to have a removal file for use in HFCLEANUP. I feel the same about the CAT files...

@Camarade_Tux: HFSLIP is not going to extract a Microsoft installer and compress it again just to delete the CAT files inside it. @Super-Magician: Yes, but hold on just a while. You'll see for yourself...

If you have a modded SFC file but are still getting CAT files in the SOURCESS\I386\SVCPACK folder they can only come from these locations: - original SOURCE - XPize - HFEXPERT\WIN

If you want calls "in many places" then you'll have to do that yourself. I've been talking back and forth yesterday evening with TommyP about this and we agree that if any external files are going to be called it will be limited to two. The current "internal" build calls two files, HFSPLUG1.CMD and HFSPLUG2.CMD, aside from the answer file (of which the functionality will be reduced). HFSPLUG1.CMD currently processes MDAC_TYP.EXE, UPHClean (for Win2K), application addons and the WMP Classic skin. HFSPLUG2.CMD handles XPize (both SVCPACK install & slipstream). The demands/wishes in this thread are far apart so it's impossible to please everyone. I don't think the next version will be a "basic" version but it won't have all the bells n' whistles of the current versions either. Some features/enhancements will be removed, among which the possibility to have EXPAND.EXE in a different location, the section that creates the short KB titles you see flash by as hotfixes are processed, and the new backup routines. The current internal build also handles the Service Pack from the HF folder so the HFSPACK folder can be removed.

If there's a way to call SECTIONS (labels) in secondary CMD files I'll take it upon me to take out all the bloat from HFSLIP, and then write a different app that calls specific sections in the main HFSLIP application. I'll maintain the documentation on that "different app" so FDV can take some time off with the misses again...

OK. I went the extra mile and released a stripped down version in the Test releases thread.

Not possible. Those "extras" should be run while HFSLIP is running and that at different times. If you don't want HFSLIP to run any external CMD files, the only solution is two different programs.I got a new version running with quite a few "features" taken out of HFSLIP into external files: - make backup - restore backup - extra DX9 files, IUCTL.CAB, OPUC3.CAB, SWFLASH.CAB, MSXML, Application Addons, UPHClean on Win2K and MDAC_TYP - XPize (SVCPACK) - XPize (slipstream) - time calculator There are in total 8 calls of which 6 (see above) are used. You can always remove those calls if you don't like them. This version is working 100% as far as I can see so it's ready to be released. Oh, and %XPAND% has been replaced with EXPAND again. I'll hear with TommyP about what should be done.

Yup. That's what I meant. When using the HFTOOLS folder, it becomes more complicated. I think that's the problem, haha!