Tomcat76

Multiboot patch & DOSNET.INF: try the latest test release (60313a) in the other thread. LAYOUT.INF... Editing this file requires modded DLLs because it's a protected file. NTPRINT.INF... I have to check into this. Is it a protected file?

Windows Messenger... It would help if you actually included the hotfix in the HF folder. Please note the difference: WindowsXP-KB887472-x86-plk.exe (Windows Messenger hotfix) and WindowsXP-KB887742-x86-PLK.exe (Stop error)

You can rename WGA1.DLL back to LegitCheckControl.dll. It was just for testers. I believe that the *.cpl issue is actually a *.cpi issue. You should remove the ending "x" from the name of *.cpi files that have one because HFSLIP doesn't rename them. For example, "CDImagex.cpi" should be renamed to "CDImage.cpi". As far as LegitCheckControl is concerned... If you remove the version that's in HFEXPERT, are you still being asked to download "Windows Genuine Advantage Tool"? I'm looking into the Windows Messenger hotfix now.

Also, can you rename LegitCheckControl.dll in your HFEXPERT folder to WGA1.DLL? You do know there's a new version of LCC, right? Yes... HFSLIP needs to be run again.

@TAiN: OK... Thanks. The new solution is still better, though. I'm letting HFSLIP compress *.cpl files again just like before. Only the *.cpi files are left uncompressed. There's no point in not compressing either. @dziubek: Just for testers... can you remove winhttp.dll from your HFEXPERT folder?

In general: when did these problems start? Which HFSLIP release is working fine? For the *.cpl files... 60312-t1 doesn't touch *.cpl files anymore (as opposed to the last few builds) so the problem lies elsewhere. Do these come from application addons?

@TAiN & dziubek: Try the latest test build; it handles *.cp* files differently @TAiN: the latest test build has an updated ERROR_REPORT.TXT section @dziubek: I can't find the problem with KB842773. The files in the Polish package are identical to those in the other packages. Are you only experiencing this with Win2K or also with WinXP? Do any other people have problems with KB842773?

These versions are test builds and are pretty much stable. As usual, use them at your own risk. A new final was released on November 9, 2009. If you were referred to this thread prior to November 9, please get the final from the main thread. HFSLIP home page ********************************************************* I hope tomcat76 doesn't mind me [tommyp] editting this post to add in a beta test build. See attachment for beta testing in preparation for the next final. Bugfixes: Beta A - Added in WM11 codec slipstreaming (not the player, just the codecs by themselves). Reordered HFCLEANUP and Drivercab merging. HFCLEANUP made more friendly for slipstreaming drivers if removing with HFCLEANUP HFCLEANUP reducers for XP seem to work now after lots of testing. Beta B - Set HFSLIP to ignore KB968930 Redid parsing of KB975254 so that the new file is put in the right location. Beta C - Acheron set me straight with the processing of the IIS fix. Thanks! Beta D - Chop my fingers off, a typo. Hope all is fixed with the iis fix now. Beta E - Special FDV request. Beta F - Fixed a problem when slipstreaming drivers and not using hfcleanup. Thanks Inki! Beta G - Finally got a round tuit and fixed a lingering prob with some languages for slipstreaming the ms installer 4.5. Beta H - The IE8 installer was run twice in previous releases. Now it only runs once. Changed the IE8 installation INFs so that they are easier to remove IE8 using hfcleanup. Beta I - Various echo cleanups, hfslip.log cleanup, french xp home fix. Beta J - Fix for the xp home fix. No donations = no more support. Two and half years and ZERO donations tells me that it wasn't useful enough. Good luck all! ********************************************************* You can help by checking if the binary removal files (2000SP4.EXT, XPSP1.EXT and XPSP2.EXT) cover everything. Download dumpdupes.cmd and place it in the main HFSLIP folder (alongside the normal HFSLIP executable). Run this tool AFTER you ran HFSLIP (it namely requires a SOURCE and a SOURCESS folder to compare). If there are any duplicate binaries that can be removed, a file called EXCLUDE.TXT will be created. Let me know if it contains additional files to those that already exist in the current removal files. This program can be used to check Windows 2000, XP and 2003 sources. Dumpdupes.cmd has one limitation: it only checks for duplicates in the current sources. This tool would have to be run again whenever new hotfixes arrive in order to ensure the list is up to date. I'll probably make another tool that outputs a full list of any driver binary that isn't supposed to be loose in I386 once I evaluated the pros and cons of both.

WinNT is "better" because it's based on VMS (now OpenVMS). If Vista doesn't support 16-bit apps, then Canon will have a lot of work to do...

Well, what do you know... Our very own wmfdist.exe is spoiling the party... You know what the problem is? The msdmo.dll that's contained in the wmfdist.exe package is older than the one contained in dxnt.cab, yet it has a newer file date. In any case, download the March 9 version from the other thread (HFSLIP_60309c.CMD). I inserted an extra line the other day which happens to work around this problem.

"hfslip-small.png" has a blue background...

I bet msdmo.dll is part of the WMEncoder.exe package you got in your HFSVPK_SW folder. If that's the case, it replaces the "good" version of msdmo.dll at the end of Win2K setup. This is beyond HFSLIP's control... Where did you get the installer from?

Blame it on FDV... Mine was OK. But it also depends on how a screen handles background colors on pages versus colors in images. I'm actually not sure if it's the video card, the monitor, the OS or the browser that's to blame in that particular case. I use a gamma of 2.0 which is right in between default Mac and default Windows. The colors/brightness/contrast are adjusted from there. Never got it to work. CorelDraw and Photoshop are really straightforward. I'd need a 200 page manual to do basic stuff with PSPro. I tried it several times in the last couple of years... but you get sick after half an hour of not getting anywhere.

FDV... You got a transparent PNG version of the small one too? My list is way too long as well...

No. I'm waiting for you to spot an inf/ini collision

On the KB page for the Update Rollup, MS specifically say that the rollup only updates components that are part of Windows 2000 with Service Pack 4. As an example of updates/features the rollup doesn't update, they specifically name Internet Explorer 6 and Outlook Express 6. I have never installed the rollup on a system that's patched with IE6, but if the Rollup installer would go through till the end you'd have to install IE6 again afterwards, so there's no point in installing IE6 beforehand. I guess TommyP never tested "Win2K SP4 plus IE6 minus Rollup" because of the above and I don't intend to either...

As far as I know, it's because UR1 overwrites files updated by IE6 with a lower version. TommyP should be able to answer that. I didn't write the script and I never investigated it...

Those "false positives" are really becoming a nuisance. AVG is the king of that. Avast (apart from winning another award very recently) seems to be one of the best at filtering reals from fakes. This one should be able to handle hidden files: HFSLIP_60309-exp2.7z Edit: Not quite. This one does: HFSLIP_60309-exp3.7z Edit 2: See March 9 release.

You need to include the Update Rollup if you want to slipstream IE6. Please refer to the Windows 2000 link in my signature.

Are you including the Update Rollup for Win2K SP4? Are you using Win2K SP4 as the source?

I wouldn't trust the About box because its content can be modified. Up until recently, HFSLIP would add a few stuff into it for Windows 2000 to satisfy Windows Update but I did some extensive testing recently which showed that it's now only needed for Outlook Express updates. On the other hand, I'm using a version of IE6 customized with IEAK6 so it's possible that one of the Internet Explorer-related edits are still necessary for non-IEAK6 builds. The file ERROR_REPORT.TXT is created by HFSLIP every time, whether there was an error or not. It contains a list of the files you are including. This can help determine what's going wrong.

Try this experimental release: HFSLIP_60309-exp1.7z (see below for newer version)

I think that's making things too complicated (script-wise). If it's only cpl/cpi files then it's easier to filter them out. Do you know of any other "collisions" like this one?

There are several solutions, yes. The easiest would be to not compress these files. Do you want them to be compressed?

Have you always had this problem with HFSLIP or is it new? Also, are you just going by what's mentioned in the About box or do you experience other problems (eg, with secure sites) as well?