[Tomcat76]

Hi glentium

Remove WindowsXP-KB904706-x86-ENU.exe. It's an older version of the other DirectX 9 hotfix you're slipstreaming (WindowsXP-KB904706-v2-x86-ENU.exe).

Also, remove this file: WindowsServer2003.WindowsXP-KB904942-x64-ENU.exe. It is intended for 64-bit versions of Windows XP and Windows Server 2003. You're looking for WindowsXP-KB904942-v2-x86-ENU.exe.

Edit:
I recommend against including WindowsXP-KB912945-x86-ENU.exe for the moment. It appears that mshtml.dll (which is part of that package) can't be slipstreamed. You can use one of the test releases of HFSLIP where an attempt is made to work around the problem.

This post has been edited by Tomcat76: 15 March 2006 - 09:16 PM

[glentium]

thanks for the quick response..

yup, i wasn't very careful in downloading that KB904942 update not noticing that i mistakenly downloaded the one for x64. oops! will be more careful next time. thanks for that info.

i'll try the test builds now.. will be back.

thanks again!

[EmRoD]

Still having issues with the WGA "FIX"

legitcontrol.dll in FIX folder or renamed to WGA1.DLL doesn't work.

juste created a sfx for it and everything rules

[noomsybaby]

First Thanks Tommy excellent tool (and all other contributers)

I have found a problem tho if you use advanced server it doesn't detect that it is the server version. A quick mod of the script file as below will fix this problem.

the additions are in bold

FINDSTR /I WINDOWS SOURCE\I386\PRODSPEC.INI>WORK\VERSION.TXT
FOR /F "TOKENS=2,3* DELIMS=, " %%I IN (WORK\VERSION.TXT) DO (
SET V1=%%I
SET V2=%%J
SET V3=%%K
)
IF "%V1%"=="2000" SET VERSION=2000
IF "%V2%"=="2000" SET VERSION=2000
IF "%V2%"=="Server" SET SERVER=SERVER
IF "%V3%"=="Server" SET SERVER=SERVER
IF "%V1%"=="XP" SET VERSION=XP
IF "%V2%"=="XP" SET VERSION=XP
IF "%V1%"=="2003" SET VERSION=2003
IF "%V2%"=="2003" SET VERSION=2003

this is just under the call folderprep statement

Regards

Nelly

This post has been edited by noomsybaby: 16 March 2006 - 07:35 AM

[Tomcat76]

Good catch, noomsybaby. I haven't tried Win2K ADV nor DCS yet so it hasn't occured to me either. Give me a minute or two to update the test builds in the other thread...

@EmRoD:
Can I have the HFSLIPWU.INF file from the SOURCESS\I386 folder?

[EmRoD]

Tomcat76, on Mar 16 2006, 02:52 PM, said:

@EmRoD:
Can I have the HFSLIPWU.INF file from the SOURCESS\I386 folder?

Sure

do you want it with witch configuration for the fix ?



original name ?

WGA1.DLL ?

compressed WGA1.DL_ ?

Another one ?

[Tomcat76]

It doesn't matter. Any HFSLIPWU.INF that was created by a test release of HFSLIP. Give me the one from the latest sourcess that you installed.

[EmRoD]

This one is done with te original dll name in the FIX folder
Using :
HFSLIP_60315c.CMD

Attached File(s)

•  HFSLIPWU.INF (17.1K)
  Number of downloads: 33

[Tomcat76]

It is possible there's a typo in the line that fixes the LegitCheckControl issue but someone else said it's working so I didn't bother testing it further. Install the attached wga1b.inf when you're booted into the fresh system (right-click and choose Install). If that seems to do the trick, download the attached HFSLIPWU.INF into your SOURCESS\I386 folder (no need to run HFSLIP again), burn a CD and install again.

This post has been edited by Tomcat76: 16 March 2006 - 08:52 AM

[EmRoD]

fixed

thanks a lot

[Tomcat76]

Uh... "fixed" after installing wga1b.inf or also "fixed" after installing Windows again with the updated HFSLIPWU.INF?

[EmRoD]

right clicking the wga1b.inf

[SnidelyW]

Hey now! Thanks for this very useful and powerful tool. I am a newbie, and I am stumped. Once I get over this first hurdle I think I will be in good shape. I am starting with a very, very basic configuration with no hot-fixes and no cabinets. I just want to be able to get past this first step before I drag all the hotfixes and cabinets into the build.

I started with a fresh copy of the XP Pro CD and slipstreamed in SP2. I can build a bootable CD from that folder and all is well.

I copied the SP2/i386 folder and CD tag files WIN51, WIN51IP, and win51ip.SP2 to the HFSLIP/SOURCE folder.

When I run the HFSLIP_60310.CMD command, it chugs along for awhile, runs without any error messages, and finishes up by creating the HFSLIP/SOURCESS folder and an ISO bootable image.

But, when I create a CD from the HFSLIP/SOURCESS folder and boot it on a machine, or boot the ISO image in VMWARE, it starts up just fine, and then quits with a message "Setup cannot access the CD containing the Windows XP Installation."

When I boot the CD or ISO image, it starts Windows Setup, and loads the first set of drivers. Then it says "Starting Windows" and goes through the dialouges for selecting a partition and optionally formatting the partition. When the format finishes, it quits with the "Setup can not access the CD" instead of going to the next step of copying all the files to the freshly formatted partition.

Any suggestions would be greatly appreciated, thanks!

Included are the WU.TXT file from HFNETCHK and the ERROR_REPORT.TXT from HFSLIP_60310.CMD.

TIA!

JR

Attached File(s)

•  wu.txt (3.71K)
  Number of downloads: 24
•  ERROR_REPORT.TXT (1.13K)
  Number of downloads: 25

[Tomcat76]

SnidelyW, on Mar 16 2006, 09:50 PM, said:

I copied the SP2/i386 folder and CD tag files WIN51, WIN51IP, and win51ip.SP2 to the HFSLIP/SOURCE folder.

When asked for a path at the beginning of the HFSLIP program, what did you enter?

This post has been edited by Tomcat76: 16 March 2006 - 03:01 PM

[Kiki Burgh]

Hi Sirs!
I came across HFSLIP while browsing for some possible resolution to my concerns:
http://www.msfn.org/...showtopic=69925 (chaining of hotfixes problems)
http://www.msfn.org/...showtopic=69415 (stuck at 39 minutes)
I hope HFSLIP would be able to resolve this for me.

BTW, could I use renamed files?

[tommyp]

kiki - You're best bet is to not rename your hotfix files. Good luck slisptreaming them all in. Please post your results.

SnidelyW - Are you doing a CD installation? How did you slipstream SP2? Are you sure that your SP2 source works, prior to running HFSLIP?

[Kiki Burgh]

Thanks sir tommyp for the encouragement ... Ü

Although i might be in a fix here as those official hotfixes that i downloaded from Microsoft have all been renamed to the KB###### or KB######-v# format. I did this way to make it easier to sort by file name via nLite. Further, this format seemed to be the naming convention of the unofficial hotfixes i added to the official ones.

Sir, would there be any other way that I could make use of such files (I would have about 270-280 hotfixes already) as I encountered somewhere in this guide that we could actually add prefic to such files for sorting purposes?

Any work around that you could advise would be certainly appreciated.

Thanks in advance!

-KIKI-

This post has been edited by Kiki Burgh: 21 March 2006 - 09:47 PM

[Tomcat76]

I think for Windows XP SP2 you should keep the original names of these:
WindowsUpdateAgent20.exe
LegitCheckControl.cab

The other files should be fine as long as they have at least "KB######" in their name.

270~280 hotfixes? Are you sure you aren't using Windows '87?

But seriously... I can't imagine you need all those hotfixes and I doubt HFSLIP handles them all. Check in my signature for the hotfixes you need for Windows XP SP2.

This post has been edited by Tomcat76: 21 March 2006 - 10:20 PM

[tommyp]

For starters, type 1 hotfixes should be have the word "Windows" in it. Type 2 hotfixes are various, but you probably want to re-download them to get the correct filename. Refer to this for the difference between type 1s and type 2s. http://unattended.ms...xp/view/web/24/

Your best bet would be to use the same file naming scheme that MSFT uses. BTW, are you sure that all of those fixes are for SP2? It seems quite excessive, unless you have every problem/issue on your machine as listed on the KB article.

This post has been edited by tommyp: 22 March 2006 - 05:32 AM

[Tomcat76]

tommyp, on Mar 22 2006, 12:30 PM, said:

For starters, type 1 hotfixes should be have the word "Windows" in it.

That's right... I forgot about that...