@retalv,

This is already supported. Create a batch file with the necessary commands called HFSPLUG2.CMD and place it into HFSVCPACK.

Keep this in mind - the CMD is executed right before the log file is generated. The path is your HFSLIP folder.

Excuse me, but I don't understand…

The only reference to HFSPLUG2.CMD is this…

IF EXIST HFTOOLS\HFSPLUG2.CMD CALL HFTOOLS\HFSPLUG2.CMD

… and is one call in phase of construction, not of installation… and it's not documented.

Bye!

hi retalv! perhaps this would be of help: http://www.msfn.org/board/index.php?showto...amp;hl=USERNAME ...

Ok, but the name of the script can be whichever name, JUMP.CMD DonaldDuck.CMD or… HFSPLUG2.CMD…

In other words one does not join null to how much I had already written in the previous post.

Perhaps the little familiarity of the language makes me badly to comprise…

However thanks to all.

Bye!

@retalv, you must use the name 'HFSPLUG2.CMD'. Simply write whatever you want to do in the batch script, then place it in HFTOOLS. If you're not sure how to do so, I'm not so sure how we can help as it was an older feature (i.e. HFSPLUG1.CMD existed before but we later incorporated that stuff back into the script).

HFSPLUG2.CMD is called almost at the end of an HFSLIP run. After that, the log file is created and then the ISO is made and burned (if applicable). So its purpose was (and apparantly still is ) to make last-minute modifications to a new source that's already slipstreamed.

Perhaps I continue to not understand…

Please, answer to me single yes or not.

The making of script HFSPLUG2.CMD it's equivalent to ADD command lines to HFSLIP.CMD (created beginning from UPDATE_INIT)...

REM ===============UPDATE_INIT==================
:UPDATE_INIT
ECHO @ECHO OFF>>SOURCESS\I386\SVCPACK\HFSLIP.CMD
REM CLS >>SOURCESS\I386\SVCPACK\HFSLIP.CMD
ECHO IF EXIST %%SYSTEMROOT%%\SYSTEM32\CMDOW.EXE cmdow @ /HID >>SOURCESS\I386\SVCPACK\HFSLIP.CMD
ECHO Title HFSLIP >>SOURCESS\I386\SVCPACK\HFSLIP.CMD
ECHO FOR %%%%i IN (C D E F G H I J K L M N O P Q R S T U V W X Y Z) DO IF EXIST %%%%i:\%MBOOTPATH%I386\SVCPACK SET HFSLIP=%%%%i:\%MBOOTPATH%I386>>SOURCESS\I386\SVCPACK\HFSLIP.CMD
GOTO EOF
REM =========================================

...and runing at T13 of the O.S. installation ?

Practically it is this that timidly I asked to implement (if it does not exist already) with this line…

IF EXIST HFTOOLS\AHFSLIP.TXT FOR /F "DELIMS=" %%I IN (HFTOOLS\AHFSLIP.TXT) DO ECHO %%I >>SOURCESS\I386\SVCPACK\HFSLIP.CMD

...that transfers the content of AHFSLIP.TXT to HFSLIP.COM.

Bye!

@retalv,

You're kind of confused there. I'm not quite sure where you're getting this information .

OK, kindly read Tomcat's post above and the information below.

HFSPLUG2.CMD does not modify any predetermined file. It only does what you tell it to do. That is, the file is called by the HFSLIP program at the end of the slipstreaming process right before the log file is written.

If you want HFSLIP to do what you requested, simply create the plug-in file like this...

HFTOOLS\HFSPLUG2.CMD

We can't implement exactly what you told us because that would just be redundant.

Now I have understood! It's obvious!

I did not consider that whichever external call is sufficient in order to activate it or for direct imput of HFSLIP.CMD.

Excuse me, but evidently a swarm of neutrinos has increased my stupidity…

Thanks!

No. As I said in my previous post, HFSPLUG2.CMD is called when the new source is ready. So HFSLIP.CMD already has the word "EXIT" at the end. If you add anything below "EXIT", it will be ignored when it's run (at T-13).

Try this:

FINDSTR/VI "EXIT" SOURCESS\I386\SVCPACK\HFSLIP.CMD>>HFSLIP.CMD
ECHO>>HFSLIP.CMD net user "Proprietario" /DELETE
ECHO>>HFSLIP.CMD net user "MYUSERNAME" "" /ADD
ECHO>>HFSLIP.CMD net localgroup Administrators "MYUSERNAME" /ADD
ECHO>>HFSLIP.CMD net accounts /maxpwage:unlimited
ECHO>>HFSLIP.CMD EXIT
MOVE/Y HFSLIP.CMD SOURCESS\I386\SVCPACK

Thanks for the advice
This solves the reseal issue !

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!

@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

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.

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.

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?

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.

O I see...
Isn't there a way for HFSLIP to mark whether wmfdist95.exe is already present and if it is, then replace it with the one from KB900325
If it isn't then del it after HFSLIP is finished?

Thanks for changing the CAPITAL stuff!

Doesn't CDIMAGE and MKISOFS do this automatically (or if not, with the right switches)?

@antonio_king, I believe HFSLIP already does that.

@Super-Magician
If thats the case it's not working correctly for me.

Don't know about MKISOFS but you need an extra switch for this with CDIMAGE.

Are you referring to the current test release?

Just tried the newest release... works fine after all... ooops

Just want to report that AUTOIT support is working like a champ in 70102b. I have scripts for Wink and SimpleOCR if anyone is interested.

T H A N K Y O U!

@Tomcat: Is there any way that you can code HFSLIP to process KB900325 for non-MCE computers? The only difference would be to exclude the KB900325.exe file unless the source was MCE. This is especially useful as there are normal XP hotfixes included in the Rollup.

the_guy

@ the_guy
Surely if Microsoft saw these as vulnerabilities in a standard XP system they would have released the hotfixes for all XP flavours?

@antonio_king: The majority of them were released. A few don't even have a kb article. it just makes sense to me as they aren't MCE only updates anyway.

the_guy

KB900325 still shows up on Windows Update.

In fact, even after manually installing the KB900325 update all the other updates show up even though I slipstreamed them with HFSLIP?


Also have another REQUEST...

Could we have a folder within the FIX one for MEDIACTR,

So we can copy modified files and have it recabbed in the MEDIACTR.CAB when HFSLIP does this?
This would be a fantastic addtition imo as I have to copy over the Royale.Theme file after Install to use my custom icons.

thanks!

Look at the last few lines of the script.

Whoops!

Hehe.

This has been there for a while. I must've been playing with that section once.
It's harmless... Two lines of code that are never called.

I'll have it fixed in the next release.


Alright. I checked out MedCtrOC.log and noticed that the updated files rely on .NET 1.1 too much. I slipstreamed CasPol.exe, fusion.dll and ngen.exe, but that only got me error messages during Windows setup about missing dependent files. So I added mscorwks.dll and msvcr71.dll, which got me a failed copy at the beginning of Windows setup for mscorwks.dll. Ran MODIFYPE on it and tried again. Now it also needed machine.config, and one other error message popped up saying that "a resource could not be found in a resource file" or something like that... but no file name was mentioned. Added machine.config, which got rid of all errors except that one that doesn't reference a name. At this point, MedCtrOC.log complains about failing to install an assembly (SonicMMBurnEngine) and to turn off CasPol logging.

I'm now going to add those four files that I have HFSLIP remove from the .NET 1.0 update (HFSLIP removes them because the installation INF doesn't do anything with them). If this doesn't help either, it'll make things very difficult. I'll have to find out which .NET 1.1 files are a minimum requirement for the installation of the Media Center rollup.

BTW... It's time that MS release an update of the rollup. When installing it "normally", I noticed that it fails miserably if WMP11 is installed -- it displays an error, and when you click OK the installer quits and initiates a system restore. Why can't it just check if the WMP10 update is needed or not, and simply skip it if WMP11 is detected? Oh well....

What do you mean by "all the other updates"? Those within the rollup package or also the regular XP hotfixes?

I'll see if something can be done here, but it won't be with the FIX folder because that's intended for last minute changes. Most likely I'll just let you put it in the HFCABS folder. This isn't top priority now, though...

@Tomcat: Microsoft states on there site that the rollup is required before wmp11 can be installed.

the_guy

These are all of the MCE updates windows update asks for on my installation...
WindowsXPMediaCenter2005-KB900325-usa
WindowsXPMediaCenter2005-KB925766-ENU
WindowsXP-KB912024-v2-x86-ENU

So those are the ones I slipstream.

When I run windows update it says KB900325 is missing.
As you said yourself the standard installer doesn't work if Windows Media Player 11 is installed so I extracted KB900325.exe and ran that file.

Windows update now says that it needs KB925766, KB912024 and Windows Media Player 11 for Media Center Edition.

Ah, OK. That's understandable. KB925766 and KB912024 update files which also exist in the main update rollup.

This rollup is really bad -- it replaces existing files that are newer when you install it...

Windows Media Player 11 for Media Center Edition? Whoops... I've been testing with the wrong version...


BTW... Adding in those four .NET 1.0 files from the NDP update didn't fix anything. This could take a loooong time to debug.....

Tomcat, are you using proper windows MCE discs or do u install MC from CMDLINES.TXT?

"Regular" MCE 2005, not cmdlines. The Media Center stuff is installed from SYSOC.INF in these.

Hi man, only a question. After I have installed the slipstreamed CD there are 3 errors in setuperr.log:
-Impossible to registrer OLE control C:\Windows\system32\macromed\flash\flash.ocx
-C:\windows\system32\msxml2.dll isn't correctly signed by microsoft
-C:\windows\system32\msxml2r.dll isn't correctly signed by microsoft

Anyone have these problems? I'm an italian user and I'm so sorry for my bad english.
I have used the latest hfslip for test (70105b version). I have attached the log of hfslip maybe someone can help. Thanks

Your English is fine

The error for Flash 9 is normal. The registration part of the newest OCX from Adobe is just broken so we'll have to wait for them to release a new version. For Win2K and Win2K3 I even had to work around this otherwise an error dialog appeared during Windows setup. Weird that they haven't updated it yet... Who'd think anyone would slipstream Flash, right?

I know about the errors for MSXML2 but am not sure why they occur. HFSLIP is including the catalog file so I guess Windows setup uses these DLLs before it checks the catalog files.