Tomcat76

The hotfix is only an update...

This error log is insane. I doubt this source is usable. I need to know if your source is OK. Can you do this? 1) Create a folder called "SOURCESS" inside the HFSLIP work folder (delete or rename existing SOURCESS folder) 2) Copy the content of SOURCE into SOURCESS 3) Create the folder SOURCESS\I386\SVCPACK 4) Copy 0_dotNET11SP1.exe into SOURCESS\I386\SVCPACK 5) Delete SVCPACK.IN_ and/or SVCPACK.INF if existing in SOURCESS\I386 6) Create SVCPACK.INF in SOURCESS\I386 with the following content: [Version] Signature="$Windows NT$" MajorVersion=5 MinorVersion=1 BuildNumber=2600 [SetupData] CatalogSubDir="i386\SVCPACK" [ProductCatalogsToInstall] [SetupHotfixesToRun] 0_dotNET11SP1.exe 7) Edit SOURCESS\I386\DOSNET.INF by adding this to the bottom: [OptionalSrcDirs] svcpack 8) Make a new CD. If you don't know how to do this, read Step 6 in the Basic how-to guide and then run HFSLIP typing "MAKEISO" instead of "I HAVE READ THE INSTRUCTIONS" 9) Install from CD and see if .NET 1.1 is installed.

SVCPACK.INF is OK. It seems like Windows setup never uses SVCPACK.INF. Is SVCPACK.INF present in WINDOWS\INF after installation? Can you attach setuperr.log from the WINDOWS folder? This should be the last file...

That looks OK. I'll test a slipstream later today, then.

*grin*

It isn't necessarily an error with ie4uinit.exe. Can you attach IEACCESS.IN_ from the SOURCESS folder?

AlBundy33-- That doesn't work for me. The hidden dialogs still take focus, ALL file names are shown during the extraction process (including the _sfx_ files), and I'm getting errors all over the place: The process cannot access the file because it is being used by another process. A subdirectory or file TEMP already exists. The directory is not empty. Access is denied. File creation error - The system cannot find the file specified. And if I use this in conjunction with START/WAIT, I get tons of DOS boxes flashing in my face too. However, I'm not sure I get what you mean by this: ... DO %RUNHIDDEN% %%I /Q...There is no "DO" in the syntax HFSLIP is using to extract hotfixes: START/WAIT HF\%HF% /Q /X:TEMP (for type 1) START/WAIT HF\%HF% /Q /T:"%PREP%TEMP" /C (for type 2) Either way, chances are slim I'll be experimenting with CMDOW.EXE some more. Someone else suggested to move away from CMDOW.EXE to something like hidcon.exe or hidec.exe because of the many anti-virus programs that tag it as a trojan. I'm already working on that.

Well... Slipstreaming the .NET 1.0 update is only possible if a source is detected as MCE. This is done by checking for the existence of SOURCE\CMPNENTS\MEDIACTR\I386. If that folder isn't there, it won't be slipstreamed.

What I wanted to check is if either the variable didn't get set or if you have an I386\SVCPACK folder structure in the root of one of your hard drives. Neither appears to be the case. Can you ZIP SVCPACK.INF and attach it here? However, the fact that Adobe Reader didn't install is quite suspicious. Double-check that the CD/DVD you're using hasn't gone bad and that there are no errors on your hard drive. It would be wise to open up a command prompt (Start > Run > CMD) and type in the following: chkdsk /r x: ...where "x" is the drive on which your HFSLIP working folder resides.

I'll consider deleting mstscax.dll if lhmstscx.dll exists. But this will only work in the long run if MS don't change their mind on the naming of these files.

I can't work around a problem before I know what it is. I don't have XP x64. Do you have iexpress.exe in the SYSTEM32 folder of your work system?

With ISONAME you can define the name of the ISO. I thought that was clear... As far as defining the folder is concerned... "Refer to previous statement" on the SOURCESS folder... I'll check out your suggestion. No promises, though...

You have a Windows source with CAPICOM? MSI files (except msxml*.msi) should go in HFSVCPACK_SW (for installation at T-13) or in HFGUIRUNONCE (for installation at first GUI logon). Wouldn't it be easier to get the CAPICOM 2.1.0.2 full redist?

The files are fine as far as .NET 1.0 is concerned. I wish I could test this better but I don't own a copy of XP MCE.

Where/When do you get that error? No problems here with two test installs thus far (one in VM and another on a real PC).

@AlBundy33 #1. Already exists. I don't make it public because people should read the instructions. If you look around, you'll find some HFANSWER.INI files in attachments. #2. Already exists. MAKENOISO=1 skips creation of the ISO as explained in the documentation. #3. This won't be done. It would make things too complex. The "SS" stands for "SlipStreamed". #4. DOCS, SUPPORT, DOTNETFX, etc. go in the SOURCE folder, just like the I386 folder and the CD tags. This is explained in Step 2 of the Basic how-to guide. #5. This isn't HFSLIP stealing focus but the hotfixes. The /Q switch that HFSLIP uses hides the dialogs you'd normally see when the hotfixes are extracted, but even when hidden they take focus. I don't know how to get around that.

What a scam... That file is not an update. It contains the original msxml6_x86.msi which can be downloaded separately from here. HFSLIP supports either the exe or the msi -- your pick. With the exe it's slower because one more extraction needs to take place, but we're talking milliseconds.

OK... Here's the instructions. This should be done on the new CHT system. 1) Download the attached file and extract it to your Desktop (file: HFSLIP2.CMD) 2) Insert the CD with which you installed Windows (exit installation if it starts) 3) Run HFSLIP2.CMD and read what's reported ykchanaed.zip

1) Q282784_W2K_spl_X86_EN.exe is not supported by HFSLIP. You should use Q282784_WXP_SP1_x86_ENU.exe (even for Windows 2000) as explained here. I suppose putting qfecheck.exe in HFEXPERT\WIN\SYSTEM32 will work but I haven't tested that. The only difference is that placing Q282784_WXP_SP1_x86_ENU.exe in HF copies over the security catalog file as well, and adds a few lines into the registry affirming that it has been installed. 2) I need to see what's inside msxml6sp1-KB934268-enu-x86.exe before I can say if it's supported or not. If it contains a file called msxml*.msi then it will work.

You shouldn't remove the hotfix if you need it. HFSLIP supports it. The file that dumpdupes.cmd picks up is a dead file taking up space; Windows setup uses the file that's in DRIVER.CAB or SPX.CAB which was updated by HFSLIP.

I could only find KB932394 after a brief search on the MS Download Center site, but .NET 3.0 hotfixes are not yet supported.

Can you start a new thread for the .NET 1.0 problem and include the TXTSETUP.SIF file from the new source? Also check if NETFX.CAB was updated (newer date). Nothing was changed in regard to the handling of MCE 2005 hotfixes since the release that initially added support for these (1.4.2). If the game you want to play requires the d3dx10 files then you need them. MS wouldn't include them in the DX9 installer if they weren't supported. HFSLIP allows slipstreaming of the d3dx10 files into Windows 2000 but this is not supported by MS. That's why my 2K list doesn't include them.

You can delete that file from the new source. I'll update XPSP2.EXT.

Supported with test release 70506a...

Don't bother. It's not supported by the current releases. The structure is different.