whitehorses

Oh my god, wait!!! ... yes of course Well, maybe. Are you thinking of regex searches with .rin files?

Well about the source I'm using... it is english W2K SP-not-4, and I patched it to SP4 with the conventional manual method. It was on a cd which contained both Professional, Server, and Advanced Server. Is this abnormal?

I don't know if it's needed when using fdv at all. Fdv's fileset removes Task Scheduler by default doesn't it? Removing entries from fdv IE.INF with hfcleanup is risky, and the only benefit is when it removes iexplorer.exe, but that can be done manually. One uses FDV IE.INF because wants it to apply it's changes right? If does not want those changes, but wants to remove strings arbitarily from IE.INF then I suggest not using fdv, because using both might give unwanted results. EDIT: What I said above was not concerning this MSTaskScheduler issue, but more general.

@TC Hmm... I was wondering while there was differences in style between hfcleanup and the other parts of the script. Anyway, this exaple simply demonstrates how the script in hfcleanup takes at least the dots in every search string as wildcard characters, and that it does possibly filter out more lines than it should. The following change is suggested here, and the similiar places: FINDSTR /V /B /I [color="#FF0000"]/L [/color]/G:WORK\HFCU\FILTER.TXT SOURCESS\I386\TXTSETUP.SIF >TXTSETUP.SIF I would even suggest changes troughout the script, to clarify up these things: - if wildcard searches are needed, use RegEx with /R switch - else use /L or /C: switches to make sure no wildcard searches occur. If anyone in doubt here is what I'm talking about: ECHO Filtering TXTSETUP.SIF ... this might take a few seconds Everyone who have ever run hfcleanup knows this line well. And it's true it really takes 10-20 second to process txtsetup. It's because it takes lot more processing power to make a wildcard search than a literal! After applying the /L switch hfcleanup filters txtsetup.sif like a flash. So I suggest removing that comment too EDIT: I haven't tested the differences in results... it depends on the exact searching pattern, and the strings searched for, but at least the possibility is there to be determining

@TP Which version of HFSLIP are you using? I don't know if it has changed in the latest test release, but I doubt anyone had run hfcleanup with really "good" results till this day Refer to "Test Releases" section for details.

I see. I have to go now. By the way, I had some clean installs since then so probably this is a big catch.

@TC - please look at that sample, because it is really ... interesting... I'm leaving in an hour or so, and it seems to me it's a high priority stuff.

What I'm thinking of is the additional inf file. I think that's the only thing there which could cause a behavior like this. Maybe not. I need a bit more time to see trough that.

@FDV I like that. would listen my shiny new Original Master King Crimson ITCOCK [iECP 10003] sleeve on that B) But currently I just listen VICP 63171 , VICP 63175 , UDCD 598 , UDCD 621 on a laptop speaker in my dark closet, so almost any improvments are well appretiated.

Hi TP! Would you check this thing for me: - OSOptions_MSTask deletes lines in fdvs ie.inf, but makes reverse effect than what it should, because those entries are in the del.reg section. same is the problem with ZZ_IE1 and 2, and two others, but MSTask makes a very strange effect: in control panel a "ghost" folder of the task scheduler appears. It looks like a normal folder, only the popup description says it's task scheduler. Doubleclicking does nothing of course. Am I correct?

ouch... that hurts, thank you very much! You won. OK...

@Oleg Can you explain the differences between your fileset and tommyp's? Is that the mini2.zip? or there is a newer "version".

nothing. It's just a string. That's the datatype of the registry entry. Those FirstEntry LastEntry values have different datatype than the ones which store the customizations. This leaves in First/LastEntries. Maybe you'll get surprised some day ... Oh ... I have a little present just for you... a little surprise Gfinder.rar

Well I made some modifications, but mainly it's the same, take a look: FOR /F "TOKENS=* DELIMS= " %%I IN ('FINDSTR /I /R "Time.Zones.*Dynamic.DST" TEMP\UPDATE\_TZC.inf') DO ECHO>>WORK\TZCINF.TXT %%I FINDSTR /V /I /R "South.America.*0x1, Central.Brazilian.*0x1," WORK\TZCINF.TXT >> SOURCESS\I386\HFSLPHIV.INF ECHO/>>SOURCESS\I386\HFSLPHIV.INF ECHO>>SOURCESS\I386\HFSLPHIV.INF [Strings] FOR /F "TOKENS=* DELIMS= " %%I IN ('FINDSTR /I /R "_Std.*= _Dlt.*= _Display[^_]*=" TEMP\UPDATE\_TZC.inf') DO ECHO>>SOURCESS\I386\HFSLPHIV.INF %%I It does the job. Uses one temp txt, and removes trailing spaces. You mean that other compression cycle? What do you mean about "existant"? And now that we are thinkering near these codes... can you tell me what is this line: FOR /F "TOKENS=1 DELIMS=" %%I IN ('DIR /B /A:D /S WORK\I386E') DO IF ERRORLEVEL 0 DIR /B /A:D "%%I" >NUL 2>&1&&CALL :DPSCANSDIRS "%%~I" This is the most cryptic line in the whole batch EDIT: That ASM folder stuff can be written like this: IF EXIST WORK\I386E\ASMS ( IF NOT EXIST SOURCESS\I386\ASMS ( RD /Q /S WORK\I386E\ASMS ) ELSE ( ECHO Processing ASMS XCOPY /E /H /Y WORK\I386E\ASMS SOURCESS\I386\ASMS >NUL RD /Q /S WORK\I386E\ASMS ) ) Not that crucial, anyway

@Oleg here's the link: http://www.hfslip.org/advanced.html @Tux But why others never experiance this, just you and me? What are those cat files by the way exactly. I don't know... I'd like to finaly understand why this hfcleanup never works for me.

Oleg2 Hmm... are you saying there are new filesets? Where can they be obtained, the ones on hfslip.org are the same as I use.

What is 78rpm records for iPod?

I must check it. Maybe you're right. Are you saying that "." is a wildcard even without regex? findstr /? does not say anything about that at least, but I will check it EDIT: Hmmm... I've just understood why those brazilian and south american updates are filtered: they have a linebrake, and you added them manually instead... nice EDIT 2: Ow crap MS, you're right. I have seen many search utilities but MS can always give some surprising moments with their "standards". So no /R is needed in that case EDIT 3: I have changed mine to the following: ... FINDSTR /I /R "Time.Zones.*Dynamic.DST" ... ... FINDSTR /V /I /R "South.America.*0x1, Central.Brazilian.*0x1," ... Notice "0x1,"? That's the most unique difference I could found EDIT 4: I found a "bottleneck": In :INTEGRATE in the main binary compression FOR cycle there is a double use of if statment. There are many throughout the script by the way, but this one is the most inefficent since this cycle runs around far more than 500 times (as many files it has to process, it can be much more) I suggest to change it to something similiar to this instead: FOR /F %%I IN ('DIR /B /A:-D WORK\I386E') DO ( ECHO Processing %%I IF NOT EXIST SOURCESS\I386\%%I ( MAKECAB /D CompressionMemory=%COMPMEM% /D CompressionType=LZX WORK\I386E\%%I /L SOURCESS\I386 >NUL ) ELSE ( COPY WORK\I386E\%%I SOURCESS\I386 >NUL ) )

You are right, I missed that. Hmm... Then yours is the right string to search for, with regex of course

I must make another test... maybe I made something wrong, sorry

I had this problem for a long time occasionaly, but always when I used hfcleanup. Now I have found out that these occasions are when I use Oleg's 2000-only removal files. Since I choose to delete catalog files, and FDVs fileset provides the modified SFC.DLL and such, I don't see why does this happen. If I don't Use HFCLEANUP or (now I know) if I just don't use Olegs files, these popups won't appear. These are the entries which are removed from syssetup.inf NT5.CAT NT5PRTX.CAT CJIME.CAT MQEXCHNG.CAT PHIME.CAT PYIME.CAT SCRDBCAT.CAT HPCRDP.CAT MW770.CAT IASNT4.CAT SP4.CAT Any ideas/suggestions? NOTE 0: I use W2K (as always) NOTE 1: I use FDV fileset (as always) NOTE 2: I use DX9 (as always) NOTE 3: I use basic hotfixes, nothing more (as always)

What do you mean? (What first and last entry?)

BUMP I though I should close this topic finally by describing what was the cause of the issue described by me in the topic post: When this happened with me I used HFSLIP in a way that I made a separate .cmd file to run hfcleanup separately from the slipstreaming process, i.e. I made a HFCLEANU.CMD file, copied some parts of the code, and modified it to run as a separate batch script to be used on an already HFSLIPPED SOURCESS folder. (it was similiar if I set DIAGNOSIC==1) The problem was, that this way my HFCLEANUP.CMD have not recognised that the SOURCESS folder had FDV fileset, as it would if I ran it according to its normal use in HFSLIP. HFCLEANUP recabs FDV fileset properly that way. Problem solved. My fault Thanks for everyone's time who answered

@ TC :TZ928388 The code in question was this, it's from 70130c test release:FINDSTR/VI "America.Standard.Time.Dynamic.DST...2 Brazilian.Standard.Time.Dynamic.DST...2" WORK\928388A.TXT>>SOURCESS\I386\HFSLPHIV.INF Just look at this string. "America.Standard"... you find no dots in the .infs, at least not in update_SP2QFE.inf of the hotfix WindowsXP-KB928388-x86-ENU.exe. Since a dot means any character in RegEx, it would recognise the line, if RegEx was enabled. But that needs /R. But I suggest not to use regex at all, because it's not really needed there. Use this instead: FINDSTR /V /I /C:"America Standard Time" /C:"Brazilian Standard Time" WORK\928388A.TXT>>SOURCESS\I386\HFSLPHIV.INF :POSTHFX I didn't know about that. I would ask MS why that 4 entries needed tabs, dooh You are right, the first line in my exaple won't remove those, hmm... At least w2k has no prob with that, there are no tabs in its txtsetup. Another interesting thing is that I don't see how the code in 70130c can remove it. That won't do this scenario too. Hmm.. this does: FOR /F "TOKENS=1 DELIMS== " %%I IN ('FINDSTR ",,," TXTSETUP.SIF') DO ECHO>>SRC_LIST.TXT %%I NOTE1: It's not visible, but there IS a tab AND a space after DELIMS== NOTE2: For some reason tab must not be the last, or it messes up everything. Short and full

I agree. It does not effect anything. I wanted to color it red... now I changed it by the way /R is not in that sample because it's the original, not the corrected one. coloring supposed to indicate the place where it should have been. I don't understand what do you mean by that. It works for me on w2k, both during HFSLIP process, and if I just run this command from commandline. I attached FULLSRC_TXTonly.TXT. Seems like it does the job correctly to me. Sorry I mistyped it: FINDSTR /I /B /R "[^=]*\." SOURCE\I386\DRVINDEX.INF>>WORK\FULLSRC.TXT (red is the color) NOTE: also attached the file to prove that it works for me at least on 2000. with the above script of course Sorry for that too. I removed the multicab feature so I didn't recognise the dependency. A question: a few lines below there is a line of code like this: FINDSTR/IR "\.AX \.ACM \.OCX msxml..dll" WORK\NSFALL1.TXT>>WORK\NSFREG0.TXT My question is that msxml..dll is what you intended to write? I during HFSLIP process I recognised that there are msxml3.dll and msxml3r.dll in as new binaries. This way only msxml3.dll is processed. Shouldn't msxml3r.dll be included too? If so, then it's needed to write: FINDSTR/IR "\.AX \.ACM \.OCX msxml.*.dll" WORK\NSFALL1.TXT>>WORK\NSFREG0.TXT at least. What's your oppinion? FULLSRC_DRVonly.TXT FULLSRC_TXTonly.TXT