There are several problems with HFGUIRUNONCE in the previous test releases that have been fixed. Please use the latest version.

Any issues with HFGUIRUNONCE should be posted in this thread until this feature is available in a "final" version of HFSLIP. After that, start a separate thread. The main post in the .NET 1.1/2.0/3.0 thread is intended as an informative post.

Any hotfix goes in HF except otherwise noted. This is mentioned on the Basic how-to page and in several other locations. So the Power Shell installer goes in HF, and .NET 2.0 must be placed in HFSVCPACK. HFSLIP will instruct Windows setup to install Power Shell at first GUI logon.

HFSVCPACK_SW is for installers that need switches.

TimeZoneSetup.msi and UFDSetupWizard.msi require .NET 1.1. A limitation in HFSLIP requires you to place .NET 1.1 in HFSVCPACK and those two MSIs in HFGUIRUNONCE. I'll fix this in the next version so that you can place those MSIs in HFSVCPACK_SW.

Windows Desktop Search is unsupported as a hotfix. All binaries inside this executable need to go into Program Files and a lot of them exceed the 8.3 file naming standard, so support would have to be hard-coded into HFSLIP. You should try to find an addon. I'll make one if I have the time.

Don't know about 6). Try the latest test version with every file in the correct place.

MSIFIRSTLOGON won't return because it's less powerful than the HFGUIRUNONCE folder.

thanks TC! i'll try my luck again ... ... i've posted some concerns about dotnet installers too
HFGUIRUNONCE seems to be quite difficult to tame for me ... any additional info about HFGUIRUNONCE will definitely be helpful ...
would any of the HFs have anything to do with this?
 lltd_driver.jpg ( 13.35K ) Number of downloads: 8

this one comes up before showing the desktop
oops, i suddenly remembered, cmd window still comes up of UPHClean-Setup.msi ...
are we waiting for the new MS HFs to be released before our new final? just asking ...

This post has been edited by Kiki Burgh: Feb 10 2007, 10:33 AM

Answered in the other thread.

Yes; WindowsXP-KB922120-v5-x86-ENU.exe.

Yes. And also for feedback on the usability of the "alternate input folders" feature.

hi again TC! my apologies if i've brought over some Qs i posted in another thread ...
 DNF11_30.jpg ( 18.32K ) Number of downloads: 9


 DNF30.jpg ( 16.4K ) Number of downloads: 4

 DNF30b.jpg ( 25.83K ) Number of downloads: 8



This post has been edited by Kiki Burgh: Feb 10 2007, 11:00 AM

Your comments are confusing!

Have you tried 70208a yet? Please use that version with all the files in the right places, like Tomcat76 said. Also, make sure your .NET files for the Silent .NET maker are in the correct location, the correct entries in the answer file are set, and ALL YOUR FILES are in the right place!

perhaps because of the quotes but my questions were really simple ... perhaps even too elementaryi certainly will ... when using HFGUIRUNONCE, does it really show a cmd window while still in the installation process ... you see that's what happened to me ... i'm not certain though if it was before T-13 or rightafter this part when cmd window came up ... i had to manually type names of .msis & .exe at the prompts (for those placed in HFGUIRUNONCE directory) for it to be executed ... i think there was 1 exe: DNF30 & 2 msis: timezone & ufd ... when everything else finished installing, i simply typed EXIT after this prompt: C:\WINDOWS\HFSLPGUI> to exit from this window to proceed with the normal installation of Windows ... there were 2 distinct results when putting (1) DNF11_30.exe or (2) DNF30.exe in HFGUIRUNONCE ... with (1) cmd window comes up with this prompt D:\$OEM$> while with (2)C:\WINDOWS\HFSLPGUI> ... you see i was under the impression that since this was for RunOnce, it should be prior to showing the desktop ... that's why i asked if it was how apps installation behaved for using HFGUIRUNONCE ... thanks!

This post has been edited by Kiki Burgh: Feb 11 2007, 08:33 AM

I've never gotten command prompt windows during HFGUIRUNONCE. Try including cmdow in HFTOOLS if you haven't already.

The latest test release changes the order in which EXEs and MSIs in HFSVCPACK_SW are installed. Maybe that will help.

thanks S-M! never have removed cmdow tool in HFTOOLS ... i think dealing with .exes & .msis as shown in changelog is great ... i'll try the latest test release ... i'm readying myself too for the new HFs that MS would be releasing soon

Yep, MS is readying about a dozen of them patches.

Hi all,

any chance in having Branding.cab supported again for IE7 as IE7 is "recompiled" for updates ?

I'd also ask for an update in the ALTDIR folders, can you inclue a function to have different files/folder in HF :

I'm building CDs for XP Pro and XP Home.
XP Home has issues with WMP11, witch make me have to remove \WMP11 and WindowsXP-KB898543-v3-x86-ENU.exe from the HF folder and add mp10setup.exe, HMTCDWizard_FRA.exe, windowsmedia10-kb902344-x86-intl.exe, WindowsMedia10-KB917734-x86-FRA.exe, WindowsMedia-KB891122-x86-FRA.exe, WindowsXP-KB923689-x86-FRA.exe Into HF.
Can ou include a exclusion/remplace list/function for the HF folder . (Currently i've build an HF Common folder, along with HFWMP11 an HFWMP10 and a batch file that copies/replace file in the HF folder)

Thanks in advance.

Hi Tomcat, I have tested a bit this release, I have an issue (I think). I have used the tool for compact DRIVER.CAB before run hfslip script. When hfslip script goes to DRIVER.CAB repacking it shows this.

 Driver.jpg ( 89.26K ) Number of downloads: 16


There is an issue or not? The script recompacts driver.cab even if I haven't put any new driver (I think)

hi S3pHiroTh! i'm not certain about this but wouldn't this:have anything to say about 0 files copied? which merging option did you use?

This post has been edited by Kiki Burgh: Feb 12 2007, 07:45 AM

Before, when I had tested the previous version of hfslip, instead of "0 files copied" there was some files... but today, I have used HFSLIP_prep.cmd before of hfslip-70211b.cmd. So I think is a new issue related to DRIVER.CAB that is been compressed before hfslip script.
I have set this in HFANSWER.INI: DRIVERCOMP=A

This post has been edited by S3pHiroTh: Feb 12 2007, 07:55 AM

S3pHiroTh--

I'm almost positive those errors don't come from the sections that handle DRIVER.CAB. Can you please try HFSLIP 70212a? It shows a bit more output text for the sections where those errors could be coming from. Maybe that'll help...

EmRoD--

You got BRANDING.CAB. I'll think about support for different HF folders but it won't be for the next final.

Slight bug with the NOLOGCOPY feature. I do not believe this was intended.

The log is no longer copied to SOURCESS until after the ISO is created. That essentially removes the usefulness of the variable and makes that feature the "default." This occurs regardless of whether the variable is actually set as there is no longer a copy command for HFSLIP.LOG before :MAKEISO is called.

Not really a bug with that feature specifically -- more a problem with the order of actions. But you're right: it's wrong

Fixed in 70212b... Hopefully...

@Tomcat76 thanks

Ok, I have tested once again with the latest build release, but the results are the same. I'll post the output messages that hfslip write, so, maybe, you can understand why this happen. (Can this happen if I slipstream, for example, KB888111 hotfix?)

been slipstreaming 888111 since it has been supported and i never had your results