tommyp

That is pretty cool! Even MSFT doesn't know how to fix their code. Hey, is the problem just the Shimgvw.dll file? If it is, how does it get installed (what INFs)? If such is the case, we can let HFSLIP fix it! All that is needed is a few files placed in the HFCLEANUP folder and we're home free (and bug free too). If anyone knows the INFs I'll write up some files for your HFSLIPing pleasure.

Tom - No harm intended in my posting. I just wanted to point out to others that Microsoft is trying to brainwash us that sometimes worthless things are needed to keep windows update happy. I would say at first glance that the "recommended" ones and the two media updates won't be slipstreamable for now.

TC, the issues have been identified with the non-WMP type fixes. WMP and XPSP1 seems to be an afterthought with the way the setup files are. Therefore, the WMP fixes (817787 and 828026) aren't readily slipstreamable (if I had time I could do it though, but it's not worth it). I only concentrate on CRITICAL and not recommended. Google for the recommended fixes and you'll see why they are really worthless. I'm not sure why a codec is a recommended fix, or a fax preview is a fix. Go figure. The issue will be fixed at the next release of hfslip. (TC - please add 896426 to your HF folder, it looks like you missed it)

HFSLIP merges SPx.cab and the driver.cab to make a new driver.cab. There should be a file called driver.cab in the i386 folder. Are you sure it's not there? What happens when you expand the driver.cab file in the non-hfslipped-slipstreamed sp2 in your source folder? What is the hscxpsp1.cab file in the source\i386 folder? That filename is new to me. I'll bet that you have something wrong with your driver.cab file. The reason I say this is because HFSLIP expands that file, and after slipstreaming makes a directory listing of the extracted driver.cab file and puts it into the driver.inf file. But your driver.inf file is pretty much empty. So either you are missing expand.exe from your system32 or your driver.cab file is f'd up. Try this to test out your source\i386\driver.cab file. Open a command box and change the working directory to your HFSLIP directory (like I mentioned in a previous post). Type this in and see if there are errors in the sourcess\i386\driver folder: MD SOURCESS\I386\DRIVER EXPAND SOURCE\I386\DRIVER.CAB -F:* SOURCESS\I386\DRIVER BTW, have you tweaked your memory via regedits or anything like that?

With that list I PMd you with the other week, my SP1 was fully up to date according to the MS Baseline Analyzer and HFNETCHK. I didn't visit WU with it, only because MSBLA does a far better job at that sort of stuff. Are you sure you got the hotfixes specific for SP1? By the way, the HFNETCHK report lists invalid checksums (which happens with all OS checks) but only the media player and mdac are the only ones not up to date. The others all had valid version numbers. Did I miss something there? Oh, the reason why people don't report issues is probably because the non-HFSLIP people like pre-configured download packs that they can double click. FDV and I were talking about this the other day, most people who use HFSLIP are people who live outside the USA.

Sorry it didn't work. SP1 is such a hack of an OS, it made me sick testing it the other week. Perhaps it's best to pull support for sp1, unless someone wants to troubleshoot code. I got no time for tweaking code for an OS that I don't use. It is PAINFULLY slow and if installed on my main box, it would crash in about 10 minutes (XPSP2 crashes for me after 20 minutes of hardcore use, 2k never crashes on me; so much for the *new* flagship OS).

I have a link on my computer at work to make custom control panel icons. It's pretty easy to use. I'll post back on Monday.

Manually slipstream SP2 into the source folder, create an iso and see if it works. If it works, then proceed to filling the HF folders and running HFSLIP.

The order of preference of the updates...... I had to read between the lines (with FDV's guidance) on this. 1. GDR 2. QFE In other words, if a hotfix has a GDR and QFE, the GDR will get copied over. If the the hotfix has a QFE only, then the QFE gets copied over. But to answer your Q, the GDR is copied over. There is nothing to worry about HFSLIPwise.

Dumb question, but do you want to make an XPSP2 slipstream/hfslip? If you want SP2, you need to manually slipstream it. FDV's site has info on how to do it. Once you manually slipsteam sp2 into the source folder, make another ISO and test it to see if your SP2 source is OK. Once that is done, then proceed to filling the HF folder with the patches for SP2. If on the other hand you need a fully patched SP1 (i.e. no SP2), then make sure you use only fixes for SP1. If you use a hotfix designed for SP2 and you are working with SP1, then you'll have junk in the sourcess.

I noticed that in your messages here that you mention SP1. Are you working with XPSP1 or XPSP2 in the source folder? Also, what operating system are you using to run HFSLIP? In other words, not the source OS, but the machine you are presently using.

How much free hard drive space do you have? Is the drive error-free? HFSLIP needs some space when running.

Try this, open a dos window and CD to the working directory of HFSLIP. I'm not sure if your familar or not with command prompts, but click start/run and type in CMD. Type in CD.. a few times so the prompt says C:>. Once it says C:> type in "cd xp" (no quotations). then type in "cd hfslip". The prompt should say c:\xp\hfslip at this point. Then type in the following exactly. copy hftools\boot.bin source HFTOOLS\mkisofs.EXE -relaxed-filenames -d -D -N -J -b boot.bin -no-emul-boot -boot-load-size 4 -o MYISO SOURCE If you get an error about boot.bin not being there, then you need a boot.bin file. The second command will make a bootable iso. If it doesn't, then report back and post your new error_report.txt file. If you want to speed things up, and if you are only using this CD to make clean installations, you can safely delete the contents of some folders. Check out unattended.msfn.org for details.

1. HFSLIP won't be able to make the ISO because you don't have mkisofs or the cdimage program. The instructions are on the same page listed above. 2. Why not try a simple version of slipstreaming (hotfixes only) and once that is done, then do your unattended programs. 3. Verify your hotfix list, you have un-needed files there. Garbage in=garbage out. Tomcat and Bilou have lists for XP. See the stickies. 4. Can you make a bootable ISO using your source folder? If your source isn't bootable, then the slipstreamed one won't be bootable either. Garbage in=garbage out. 5. Instead of "systematically started removing elements " of your source folder, why not copy the contents of your original XP cd? HFSLIP is expecting an unadulterated installation source to work properly.

Graham - Welcome to MSFN. We also welcome constructive criticism. Your findings are correct. Tomcat & the_guy, can you update your lists?

The versions are more important in this case, not the dates. I tested a few files from the MCE and from the KB891122 version. Both are the same, and both extracted exe files result in 60 files. It's the same package with different timestamps. The filedate change is a common thing now with microsoft. They are getting sloppy now with their binaries and save dates.

I'm not sure if this really answers your question, but HFSLIP uses the wm9/10 codecs of this: http://support.microsoft.com/kb/891122/ There are two downloads, one for 2k and the other for xp. I do not think they are interchangeable. If in doubt about the latest and greatest, extract the executable, and compare the DLL revisions (I did that too many times when writing hfslip). When WMCSETUP is placed in the HF folder, it gets installed via svcpack (in other words not slipstreamed). So it won't matter if you have newer ones already slipstreamed (the installer will not overwrite a newer binary). An alternate route is to skip the wmfdist95 in the HF folder, but keep the WMCSETUP in the hf folder, and just let the WMCSETUP install its own wmfdist95. FYI, when HFSLIP is run and the wmfdist95.exe is in the HF folder, HFSLIP will extract the contents and repack it into the sourcess folder. If there is a real need for this, I'll look into slipstreaming it.... but don't hold your hopes up. What are the benefits to WMCSETUP? Does it work on W2K?

A little followup on this matter. NLITE doesn't like renamed files. For example, INF renamed to IN_ and DLL renamed to DL_. Also, NLITE doesn't like modified setup dlls in the source either (setupapi.dl_, sfc.dl_ and sfcfiles.dl_). So watch your toes if using advanced features of HFSLIP when using NLITE. I posted my findings of all of this (and others) here: http://www.msfn.org/board/index.php?showto...&gopid=439898

Another option is to let HFSLIP create a bootable ISO. http://www.vorck.com/hfslip-info.html

Oleg - Nlite didn't remove any cat files in my svcpack.

Found the problem. The new version of nlite doesn't like to see modified INF files in your sourcess folder. I had a modified mplayer.inf file, but when changing it back to the original, it worked. I like the older version of nlite better.

I think NLITE has changed the way of crunching the source. I tried a bunch of times to nlite a source, only to get an error. Anyone else have problems? Looks like I'm going to be counting on Oleg's reduction fileset pretty soon as an alternative.

Another option is to make an ISO out of the SOURCE folder instead of SOURCESS. If your SOURCE folder won't boot/install right, neither will an HFSLIP'd one. Garbage in=garbage out so to speak.

Wela, as a special christmas present to all, the directx9 works for XP, 2k and 2k3. As long as the extracted installer CAB files are placed in the HFCABS folder, you're good to go.

TC - See this link: http://www.vorck.com/2ksp5.html; the scsiport.sys was fixed with the 2nd issue of the 2k rollup. Please advise if it needs to be the SP4 version instead. The only issue with the rollup is the international webvw.dll, all other binaries are OK.