Tomcat76

It doesn't even appear on Windows Update -- at least it didn't today. I removed KB920958 from my hotfix page (sig), added KB925308 instead and labeled it a security hotfix.

Thanks. I noticed today that dwintl.dll is already in the Win2K source so that makes it easier, hehe. Today's release handles WMP9...

It's as easy as slipstreaming WMP10... I don't have a machine handy with WMP9 installed so I need to know the location of these files: wmburn.exe dwintl.dll wmerror.dll

OK... Here's a new one. Not for the faint at heart!

That's a problem because KB891122 is not supported. HFSLIP doesn't do anything with wmfdist95.exe if it is inside a package; it only handles it when it's "loose" inside the HF folder.

It's supported.

They are. XP MCE isn't supported by HFSLIP yet because the main rollup contains hotfix executables instead of separate files.I don't have a current list but see how far you get after installing these: WindowsInstaller-KB893803-v2-x86.exe WindowsXPMediaCenter2005-KB900325-usa.exe WindowsXPMediaCenter2005-KB919803-ENU.exe

Is it possible that this only appears on WU for English versions of XP SP2? I just went to update a Dutch XP SP2 system with the latest hotfixes on Microsoft Update and all I got under "Optional updates" was WMP10 and .NET 2.0...

Coming up: - [XP] improved slipstreaming of KB887472, KB896344, WMP10 and wmfdist95.exe - [2K] improved slipstreaming of wmfdist.exe - automatic support for new binaries/files in future hotfixes This will take a few more days to complete. I'm very busy these days and I will also need to do some thorough testing with all OS's before releasing a test version.

I haven't actually done a full Win2K install with the latest hotfixes yet, but there are no new files included and the installation INFs are OK so I don't see why there should be a problem. RJARRRPCGP... If you're experiencing specific problems, can you explain which they are?

All I can say is that I have LegitCheckControl.cab in HFCABS for all OS's and KB905474 in HF for XP SP2. Never had a problem with it....

Yeah... MS scared us before with a supposed update of the UPHCS. If they update the online documentation they shouldn't update the date in the yellow/blue box. Version 1d was made on April 27, 2005.

I can't see what might've caused the TXTSETUP.SIF corruption, but I suggest you use the latest test release from today (60911a) which fixes support for the latest versions of the RVM Update Packs. Good luck...

Thanks. Try the latest...

I'd bet it's the winnt.sif file. I can't think of anything else that would cause Windows setup to not display any installation options... BTW... It looks to me that that WU.TXT file is a result of a scan on the C: drive. I thought the installation of Windows you're having problems with is located on your second partition.

To be honest, Kiki, I'm a bit confused here. What exactly are your problems after using HFSLIP version 60810 when using the correct version of the KB918899 update (the one for XP SP2)? Do you get the same problem(s) with an older version of HFSLIP if you run such older version again? I couldn't see anything wrong with the setup files you provided in your post. Can I have a look at your SYSOC.INF too?

I remember there was an optional update (showing on Windows Update!) which replaced a critical update but I don't remember which two updates were involved. So it's possible that Windows Update complains about a missing critical update if you don't include the optional updates from my list.

It doesn't show for me. I think you misread OE's post: he was testing with a clean SP2 source. It does happen that Windows Update lists replaced updates along with the newer versions if both are newer than what's installed.

Personally, I'd prefer to avoid anything that relies on the XP/2K3 built-in burning engine. It needs to work on Win2K too. I think the best thing is that everything is regulated from HFANSWER.INI and that HFSLIP assumes no defaults. These would be the variables: NOBURNISO= BURNISOCMD= The BURNISOCMD variable should contain the command to execute the ISO burning. If this is not set or if it is empty, no burning will take place. If you want to bypass ISO burning even when you added the BURNISOCMD command, set NOBURNISO to 1. What do you think of this?

Will be done next time. And I changed the subtitle of the main thread...

So if you remove either the Vista icon pack OR XPize 4.5, everything is OK?

Good idea, TAiN. I added anchor links on the Advanced Features and Special Features pages. @Kiki Thanks for reporting the bad link. For the moment, all hfcleanup files are hosted on hfslip.org. @Kiki again I'm thinking of doing any of the following: - add a black&white printer stylesheet so the pages can be printed off the web (might not work reliably in IE) - offer a PDF file for download containing the site in plain b&w format This might take a while to achieve, but is it along the lines of what you were after?

@Kiki... Are you having the same problems with themes and everything if you try now with v60804 and v60712?

Thanks, Wela.

Hi Kiki. I wish I could help out but I'm much too busy these days. I already had a look at your TXTSETUP.SIF and HFSLIPWU.INF files and they look OK to me. The only advise I can give ATM is this: 1) Disable anti-virus 2) Copy a fresh source from the CD 3) Redownload additional programs including CMDOW.EXE 4) Run HFSLIP and burn new CD 5) Re-enable anti-virus