[Tomcat76]

S3pHiroTh, on Feb 6 2007, 11:01 AM, said:

This means that, if I use Windows XP SP2, I should remove the old variable INCWMPCSKIN and replace it with the new INCALLSKINS?
Or INCALLSKINS has an highest priority than INCWMPCSKIN?

It has a higher priority: if you set both to "1" then only INCALLSKINS will be taken into account since there's no need to copy the Classic skin twice.

Just note that all HFSLIP does is copy them over into the skins folder. Whether or not they are compatible with WMP 9, 10 or 11 is something else.

daddydave, on Feb 6 2007, 06:01 AM, said:

Tomcat76, on Feb 4 2007, 08:58 AM, said:

At this point I'm more interested in comments on the "alternate input folders" feature. At the current rate of interest it won't make it into the final...

Perhaps if I understood their intended purpose...

This feature is mainly for people who don't have a lot of disk space but wish to create different outputs. Instead of creating --say-- five HFSLIP working folders each containing a copy of the CD source, you can now have five working folders with only one containing the CD source. The FDVFILES, HF, HFCABS, HFCLEANUP and HFTOOLS folders are also cumulative (they only exist in the "main" working folder alongside the source). FIX, HFEXPERT, HFSVCPACK, HFSVCPACK_SW and HFGUIRUNONCE can exist in both the main working dir as well as in any alternate working folder you create.

This post has been edited by Tomcat76: 06 February 2007 - 06:14 AM

[pdxrob]

Tomcat76, on Feb 4 2007, 05:58 AM, said:

At this point I'm more interested in comments on the "alternate input folders" feature. At the current rate of interest it won't make it into the final...

Bad timing means I will not have time to test this until next week, but that said I like the concept and it would be of great use. I am currently maintaining 7 different builds buy making copies of all the HF supporting folders and copying them into a HF main folder to make the build, basically a manual process of similar to what you are attempting to automate. In a nutshell, good idea I like it.

[Super-Magician]

@Tomcat76

I still have no idea what's going on with my installation. I get four files in HFSLPGUI, but they aren't the ones you say should be there. This is what I see.

HFGUI1.EXE
HFGUI2.EXE
IE7_INST.EXE
PSHELL.EXE

[Super-Magician]

Something is not right. I just ran 70202b again, which worked before. Now I get the same error.

What's wrong?

[Tomcat76]

Super-Magician...

You can test something for me but I'd first like to see the TXTSETUP.SIF and DOSNET.INF files from SOURCESS\I386. I need to make sure everything's alright there.

[Super-Magician]

Sure, no problem.

 HFSLIP.zip (135.9K)
Number of downloads: 4

[Tomcat76]

OK... I see the problem. Good idea to ask you for the TXTSETUP.SIF file...

[Tomcat76]

70207a, at your service... Sir!

[Super-Magician]

Thanks. I will test it tomorrow.

[whitehorses]

@TC

I would like to ask a big favor. Would you make me a "personalized" version of 1.2.2 with additional comments for "IF EXIST filname" blocks at the following places:

:HFBLOAT
:POSTHFX
the INFCREATORS
and SVCPACK

It would be a great help to know what those processings are exactly.

This post has been edited by whitehorses: 07 February 2007 - 12:19 AM

[zedox]

Has Media Center support been dropped now?

[Super-Magician]

@Tomcat76,

70208a works without incident. Thanks!

[the_guy]

Bug Report: I just wanted to make the IE7 executable with all updates, and for some reason modifyPE is required. I'll put modifyPE in HFTOOLS to bypass the error.

the_guy

EDIT: Maybe I should've read the information better. Why is modifyPE needed anyway?

This post has been edited by the_guy: 08 February 2007 - 07:46 PM

[Tomcat76]

If IE7 hotfixes are found in the HF folder, a new IE7 installer is created in which those hotfixes are slipstreamed. This is done with iexpress.exe, but Windows setup won't allow the output file to be copied over from CD to the hard disk if it isn't modifyPE'd first.

ModifyPE is only really needed if doing a non-SVCPACK install (not specifying IE7SVCPACK=1) of the newly created IE7 installer but I decided to keep things more simple by making it a prerequisite either way.

[the_guy]

Thanks Tomcat.

Also, for some reason HFSLIP wanted to extract and recompress driver.cab. Is there any way that driver compression can be skipped over if no files need to go into the driver file and selected compression method is A?

the_guy

[tommyp]

the_guy - if you have a slipstreamed source, there is typically a SP#.CAB, where the # is the service pack that is slipsteamed. The SP#.cab files have some binaries that are updates of the driver.cab binaries. With 2k, some of the dx9 binaries have to get packed in the driver.cab. Sometimes, there are hotfix binaries that have to get packed into the driver.cab too. Perhaps there is a workaround to create an optional hfslip pre-processing script to merge the sp#.cabs and driver.cab. If a hotfix and/or hfexpert drivers needs to get added during the normal hfslip process, an spx.cab will be created. Whattaya think? TC?

[the_guy]

@tommyp: I understood that. What I meant is to not have driver processing if you just have IE7 updates in HF, or no files in HF, and option A was chosen for driver compression. What could be done is that there could be a variable in HFANSWER.INI such as RECOMPDRIVER=0 to cancel driver recompression, with the value ignored if DRIVERCOMP wasn't A.

the_guy

[Tomcat76]

@the_guy

Check out the HFSLIP Preparation Tool

[the_guy]

Interesting tool!

the_guy

[Kiki Burgh]

hi TC! my apologies if what i'm sharing here were based on several results from testing 70203b ...
(1) posted some dotnet issues in Unattended forum: Silent .NET Maker (latest update: 20070201), Create silent switchless .NET installers for Win2K/XP/2K3 x86 ... could it be posted here in Test Release or in the new topic you started: How to slipstreasm .Netframework 1.1 and 2.0
(2) Windows PowerShell 1.0 English-Language Installation Package for Windows XP (KB926139) didn't install ... tried it in HF & HFGUIRUNONCE ... no go from both locations ... i recall trying to slipstream this before but you informed me back then it wasn't supported ... until i read in

Quote

Extended changelog for HFSLIP 1.2.1
General updates:
PowerShell 1.0 is now installed at first GUI logon and localized versions are supported
Note: you need a silent .NET 2.0 installer in HFSVCPACK as this program requires .NET 2.0

(3) are there specific instructions in using HFGUIRUNONCE that i might have missed? do i really have to execute these files manually while the cmd window is active?
(4) are there specific HFSVCPACK_SW to do's prior to putting .msi files here? TimeZoneSetup.msi & UFDSetupWizard.msi didn't install (even if placed in HFGUIRUNONCE ... this was despite having dotnet1 & dotnet2 in HFSVCPACK (btw, aren't DNF11.exe & DNF20.exe, being switchless installers supposed to be placed in HFSVCPACK_SW?)
(5) is WindowsDesktopSearch-KB926356-V2-x86-ENU-6.0.5414.0 supported? i recall doing this the unorthodox way via HFSVCPACK before & if i recall it correctly, it worked ... officially though, is this download unsupported?
(6) i'm not sure if this has something to do with HFSLIP but installing drivers upon hitting GUI was problematic for me, specifically for older Install Shield Wizard ... they get stuck in the askbar without terminating automatically ... i always ended up rebooting the pc ...

please advise ...
thanks!

This post has been edited by Kiki Burgh: 10 February 2007 - 03:49 AM