Thanks for the advice
This solves the reseal issue !

This post has been edited by EmRoD: Dec 18 2006, 02:25 AM

Thanks for the kind answer, and excuse if I not have understood endured what you had written in previous post, but the translation problems exist.

Now the solution is much clear…

Bye!

This post has been edited by retalv: Dec 18 2006, 04:06 AM

@retalv

Glad you understand. If you use HFSPLUG2.CMD, you don't have to modify the main HFSLIP script at all!

Re: 61227a and autoit support:

If I am reading this correctly, the setup .exe files (which should be in the same folder as the .au3 scripts - I think that is the usual convention) do not get copied to I386:

COPY HFEXPERT\AUTOIT\%AUTOEXE% SOURCESS\I386
copies the executable into I386. Are you saying now that there's more executables?

Don't know if it's of any use, but I was also thinking of expanding the feature a little by allowing more than one subfolder starting with "AUTOIT" (eg, AUTOIT2, AUTOIT3, AUTOIT4, etc) in case people need to use scripts that haven't been updated yet. This is trivial but I need to know if it can be considered useful or not.

In addition to the autoit3.exe, there would be an executable of each setup that is automated by each .au3 script

This post has been edited by daddydave: Dec 28 2006, 10:36 AM

Autoit3 is pretty dominant, I think. The program became a lot more user-friendly with version 3, I think, and I haven't seen an Autoit2 script on these unattended boards

What about AutoHotKey scripts ?

(and AHK handles AutoItv2 scripts )

I can't add support for any installer type out there. Is it used a lot?

I don't know which one is more popular. But don't bother with this : I find it a pity fast noone knows about AHK on this board (and only on this board).

Yes, I was going to make that point.. AHK, while a great program, is dead to all the MSFN boards. Furthermore, almost every posted script and every utility I've seen posted for simplifying the creation of unattended scripts, that I've seen at least, is geared toward almost nothing but AutoIt3, not Autohotkey or AutoIt2.

I install both AutoHotkey and AutoIt3 on my system. I use AutoHotkey mainly for scripts that do not exit, like autocorrect, "FavoriteFolders", and making Alt-F4 work in cmd windows. I considered using it for unattended installation scripts, but it appeared I would be the first one doing so, so I quickly added AutoIt3 to my toolbox.

OK, Kiki Camarade_Tux, I searched and did find a few. I may have exaggerated slightly.

This post has been edited by daddydave: Jan 3 2007, 09:37 AM

hi daddydave! perhaps you meant Camarade_Tux?

Oops, yes

@Tomcat76

Maybe we could have a slight update to this section?

Setup pauses and never recovers on Registering components T-12 Part.
When Slipstreaming KB900325 into MCE.

Please make sure that your SOURCE folder is properly set up for MCE 2005. I just updated the description near the top of the main post in this thread.

Just to point out, I did have my SOURCE folder setup correctly.

I've got it to work, I think maybe things I do to my install after HFSLIP may cause it to break (ie: Nlite)

I ran a test install, only using HFSLIP, Its perfect! And it even means users will no longer need to install NET 1.0 SP3!

Something does break the install, but I don't think its a problem with HFSLIP but possibly Nlite.
I think when nlite edits the files it may possibly remove information added by HFSLIP to the TXTSETUP file.
I'm going to keep trying until I find out what exactly causes the install to break and will report it to all.

This post has been edited by antonio_king: Jan 3 2007, 07:05 PM

When hotfix WindowsXPMediaCenter2005-KB900325-usa is extracted.
wmfdist95.exe is not deleted at the end of install from the HF folder.

Also, one request...

Could the MEDIACTR, TABLETPC, NETFX, SONIC, I386 folders and cabs be renamed using all caps when being recreated/recabbed?

This post has been edited by antonio_king: Jan 4 2007, 03:12 AM

ha! ha! i always rename this myself too after before finalizing the ISO!

OK. The folders are capitalized as well as the cab files that HFSLIP updates.

This is by design. If the user has a more recent version of wmfdist95.exe in the HF folder he/she should not be forced to redownload it after running HFSLIP.