Super-Magician

It did happen recently. You do not need it when Flash Player 7 or above is installed. Results from test of 60509b: Command line syntax error while processing KB913433.

Must have been for Microsoft AntiSpyware (I know there was one for that). Rogue - can you update your CCleaner one? Also, do you have any links to other silent switchless installer lists (not that yours isn't good for my needs )?

And you have the most up-to-date version of regular WGA (KB892130) installed? Hmmm... I've been using HFSLIP to slipstream updates such as WGA (both of these versions, see my signature), but WU does not complain.

How about this direct download link to WGA Notifications (KB905474)?

PVU, you have to use a clean source, which means you can't use one previously slipstreamed by HFSLIP. Tomcat, I'll be testing KB913433 using 60409b (I know this is only a temporary solution).

I may have misunderstood, but why does the batch file inside the installer remove the Start Menu and Desktop shortcuts? Isn't it supposed to add them in?

(2) Kiki, can you tell us the KB number that HFSLIP reports? (8) Nope! (9) I'd like something such as this, but because certain screens are echoed and cleared (CLS), it would not work. Normally, you would do something like HFSLIP_60507b>MESSAGES.LOG at the command prompt, but then the initial screens/messages, etc. won't show up on the screen. However, if you'd like to show any error messages in a file, type HFSLIP_xxxxx 2>ERROR.TXT. (10) I second this idea !

Yes. DirectX CABs go in HFCABS (only the *d3dx9* ones) and Windows Installer goes in HF.

Wow!! A whopping thirteen (13) patches next week! Quote from MSFN news page: Based on the InfoWorld article, nine of the patches will fix vulnerabilities in the Windows operating system.

Kiki - the SW in XPIZESW just means "switches", like in CDIMGSW and MKISSW (isoconf.txt).

Maybe you should include a fix for the FIX folder . Have HFSLIP rename "LegitCheckControl.dl_" or "WGA1.dl_" to "LCC.dl_", and compress "LegitCheckControl.dll" if that's in FIX.

Yes, that's true. I don't think there's an easy way to fix that. Tomcat - minor prob with writing the run time into HFSLIP.LOG. Obviously it won't get written into the ISO as that's created before the time is generated. Just a head's up .

But - the modification provided by Kramy - wasn't that to get rid of such error message?

That's what I figured after I thought about it for a while. Thanks.

Outatouch: I accidentally left out something in the getboot.cmd file I attached earlier. Please redownload it from that post. Thanks.

Time bug fixed! Thanks, Tomcat I did not see the error box saying "There is no disc in the drive," but that's because I didn't have bbie.exe in HFTOOLS so the script didn't process that section. (See my previous post if you don't know what I'm talking about.) If I run the following script, that error box pops up (note: this is an exact copy of the :GETBOOTBIN section with a few things at the top). @ECHO OFF CLS SETLOCAL ENABLEEXTENSIONS ENABLEDELAYEDEXPANSION :GETBOOTBIN REM Modified by Kramy -- Thanks! FOR %%i IN (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:\ IF EXIST %%i:\I386 SET HFSLIP=%%i HFTOOLS\BBIE.EXE %HFSLIP%:&COPY IMAGE1.BIN HFTOOLS\BOOT.BIN&DEL/Q/F IMAGE1.BIN GOTO EOF :EOF

Tomcat: Is there anything in the script that is processed before :GETBOOTBIN but is needed to parse :GETBOOTBIN properly? You modified the :GETBOOTBIN section of the script after Kramy suggested something to get rid of the error message that pops up. For some reason, I think the message still pops up. I haven't observed this, however, because I have boot.bin in HFTOOLS, and therefore the script skips that section when I run it. Nevertheless, when I copied that section into a separate batch file and ran it, the error message popped up. I will run HFSLIP without boot.bin and see if I get the message. Edit: Actually, I think I may have a special case. I have a drive, D:, that is a ZIP drive and normally does not have anything in it. If I run the test script (that has only :GETBOOTBIN) and leave echo on, the error pops up after it processes drive D. (The following has nothing to do with the above problem) On a side note, I think you should insert the following line into :GETBOOTBIN so that HFSLIP does not try to run BBIE if no disc is detected.

That is odd. And you have a genuine disc from Microsoft? Try the following. Download the attached script and place it in your HFSLIP working directory (i.e. D:\HFSLIP\). Run it with the XP CD in your drive and report what you see after it runs. P.S. You no longer need MSICabExtract in HFTOOLS. TommyP/Tomcat removed the need for that awhile ago. [attachment removed]

It should appear in HFTOOLS. Can you attach a copy of your HFSLIP.LOG file, or tell me the exact files in your HFTOOLS folder?

OK. Haven't had time to test, but will report back by tomorrow, if not sooner.

!! Unfortunately, the run time indicator has a bug !! Suggestion once you figure out the bug: have HFSLIP record the time when it actually starts running, not immediately after you start the script (the time will depend on how long it takes you to go through the initial screens and type the "I have read...").

Tomcat: Thanks for implementing the run time indicator! So it is possible with DOS? Great job on the coding there !! Now, I hope I'm not asking for too much, but how about dziubek's other suggestion on the difference in size between SOURCE and SOURCESS? Oh, and personally, I liked the old format for the hotfix extraction section (at least 60428a-60429a). Because HFSLIP showed the names of the files that were being copied, the script *appeared* to move faster. IMHO, the current test release (60429d) has too little information in that section .

TAiN - You are absolutely right about that second variable . Thanks.

Thanks for adding in the changes, Tomcat . You rule! If you have the time, please see if you can do anything with this: dziubek requested earlier this month (see his posts in this topic from Apr 15 and Apr 22) to have added to HFSLIP.LOG the time it takes for HFSLIP to run. I know that this is not possible with DOS, but it is possible to record the time HFSLIP starts running and the time HFSLIP finishes slipstreaming/repacking/etc. I think this is a great idea. Maybe you could make the following changes to the script. (Of course, if you decide to introduce them, you may improve/modify these changes) Edit: Added more possible changes

Well, thanks for responding, siginet! I'm looking forward to Beta 2. No rush, of course .