I have had the same issue this afternoon when I have tried the latest version of hfslip

Sorry, guys. I didn't check the output in TXTSETUP.SIF when releasing the previous test release. Should be fixed now...

Hmmm... I just don't see why...

FINDSTR/I "Time.Zones" supposed to find strings like:
TIME.zones
time.ZONES
TiMe.ZoNeS

But never ever will it find the string with a space, which was probably what it intended to:
Time Zones

I checked the inf file in concern manually, and at least if you want this command to find something you should not search for /I Time.Zone literally. The "." in regex means any character, including space, so it will return the line you need. Altough this works, there is absolutely no need to use RegEx here, by the way. It would be more efficent and convinient to simply write:

FINDSTR /I /C:"Time Zones"

Using regex searches is just a waste of cpu power, so I suggest only using it when neccessary.



EDIT : So it turned out that findstr takes dots as wildcards by default, and I used total commander's search when I said that I found no occurance of "Time.Zones".

This post has been edited by whitehorses: Feb 2 2007, 04:14 PM

Wow, Tomcat! You've introduced a number of errors in these here test releases! Gotta be more careful there...hehe.

@TC - I see you have changed it in the newest test release. Unfortunately it wasn't quite succesfull, at least to say



This code is a bit different in some aspects than what I suggested, AND... beside that minor formating difference, that you left the spaces in front of the [String] section entries, by not adding that FOR in front of the last FINDSTR, ... which is not an error...
... there is one indicated with red: a missing /R. Though it's much smaller problem than it was before, since this one only just results in four additional entries in the strings section, which is harmless. But if you don't care about it, just ignore the whole line


EDIT: Sorry I will be really annoying I know, but I'm even a bit angry, because I was turned down when I said my installs are not behaving as they should. There are a LOT of such mistypings,as the above, even more serious. Call it bug or ERROR does not matter. Explain this for example:



Yes this is at the end of :CLOSURE, ("New binaries" it says) Should I be surprised if there a no "new binaries" processed when I install my shiny new Windows? I don't clearly see what's the exact results of this code, but I think it can be serious. Hasn't ever anyone noticed something strange about this?

EDIT 2: Ok here is another subject guys: EFFICENCY. Not as important as correctness and validity, but important too.

why would you write SRC1.TXT line by line to FULLSRC.TXT without making any processing on the text, instead of:

FOR /F "TOKENS=1 DELIMS== " %%I IN (WORK\SRC0.TXT) DO ECHO>>WORK\FULLSRC.TXT %%I

Have you tested what's the difference? Well I did! On my 1,4GHz PentiumM the second for cycle on a w2k txtsetup.sif takes 30 seconds!!!! THAT'S A LOT

EDIT 3: I did not want to offend anyone, I just want a clean install, and maybe help others to have so.

EDIT 4: here's the ... more efficent, less... script:


EDIT: the * is needed, sorry for omitting it first

This post has been edited by whitehorses: Feb 1 2007, 01:14 AM

That's right. I thanked you for the IDEAS in the changelog.

It's intentional. I thought you wanted things to go quicker.

I don't see the /R in your code sample. I only see a /VI and it's orange.

The first line is useless because it doesn't strip the tabs. If I try your code on an XPSP2 source, the following files are considered "new" if they appear in a hotfix:
wuau.chm
noise.chs
noise.cht
The only thing I can (and will) do is merge the first two lines of the existing code. I normally even do that, but I was using the temporary file at some time and forgot to update the code when it was no longer necessary.

The second line in your code is garbage: the resulting file is empty (0KB). I tried various alterations but nothing worked except the existing code. Also, I need the temporary file DRV.TXT for the processing of SPX.CAB and DRIVER.CAB.

This post has been edited by Tomcat76: Jan 31 2007, 06:17 AM

Hi Tomcat, I've tested the latest version of the script, but there is one bug (maybe, I hope it's a bug or I'll become crazy ). I have slipstreamed Net packages version 1.1 and 2.0 in HFSVCPACK, and 3.0 in HFGUIRUNONCE.
When Windows installation comes to T-13, it installs all the net packages, instead of installing version 3.0 at first logon. Is it only a my problem or someone else has this issue?

This issue isn't present in version hfslip-70129b

This post has been edited by S3pHiroTh: Jan 31 2007, 09:48 AM

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?

This post has been edited by whitehorses: Jan 31 2007, 12:27 PM

I don't get 4 extra entries without the /R. I'll check out the Italian version of the timezone update -- maybe I'm missing something.

That's nice, but the TXTSETUP.SIF of my XPSP2 has a tab right after the three file names I mentioned (between the file name and the = sign). Your code does not remove that extra tab so I also get it in FULLSRC.TXT. A list of the new and updated files is made after that, and then existing file names are stripped out (so they don't get referenced again in TXTSETUP.SIF and DOSNET.INF) by comparing the two lists. If a hotfix updates those three files, those extra tabs in FULLSRC.TXT will cause DOS to think those files are completely new and as a consequence add duplicate entries into TXTSETUP.SIF and DOSNET.INF.

Alright. I'll test this in a bit.

The msxml*r.dll files aren't supposed to be registered to my knowledge. At least, they produce errors when registered.

@ 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

This post has been edited by whitehorses: Feb 1 2007, 01:21 AM

hi! i'm so glad i was able to do create some build over the past couple of days ... using 70129a (although it shows here that 70130c is already out) ... here were some of the issues i encountered:
(1) as posted in a different thread: Trouble with slipstream Dell OEM Win XP, i encountered activation issues making use of Dell OEM XP Pro SP2 cd in a clone machine ... have also tried this this no wga but still the same
(2) given the above concern, naturally i had problems with wmp11 & ie7 installation too ... both were not there even if IE7SVCPACK=1 was specified in HFANSWER.ini ... even with rebootting upon finishing of OS installation ...
(3) please correct me if i'm mistaken, i do not need earlier wmp HFs if i were to slipstream wmp11, right? or are the following still required: KB911564 & KB894871 ... would there be any other specific HFs that are required?
(4) i encountered common errors as i hit the desktop: framedyn.dll not found & error loading srclient & only a few addons were installed (& still without wmp11 & ie7) ... i think these were caused by some add-ons ... (any of these could be the culprit: Kels_FGCBA_Handler_addon_v0.897.CAB --- for this 1 there was an error while still running the cmd during the integration of addons, NR_VistaUAP_Addon_1.1.cab, or Ricks_RTMSidebar_AddOn_v2.rar ... taking these out from HFAAO did not produce the aforementioned error ...
(5) likewise encountered at T-13 was this: [b]Installer initialization failed due to following error: Undefined error: Invalid command line argument "Q:A".[/b] ... although i realized later that some installers were incorrectly placed in HFSVCPACK_SW rather than in HFSVCPACK ... this has been rectified by transferring the installers
(6) these 2 .msis even if placed in HFSVCPACK_SW were not installed: TimeZoneSetup.msi & UFDSetupWizard.msi
(7) checking setuperr.log also presented a number of errors ...

i've attached some files that might be of help ...
really nice to be able to run create some builds again
thanks in advance

This post has been edited by Kiki Burgh: Feb 1 2007, 05:34 AM

@whitehorses
It's intentional. The "FirstEntry" and "LastEntry" lines are supposed to be included in HFSLPHIV.INF.

@Kiki
1) HFSLIP supports the OEMBIOS addons -- at least, if I interpret them correctly. I personally doubt it you can use these on a self-assembled PC.
3) Important things to know
4) I'll check out those three addons
5) EXEs in HFSVCPACK_SW are installed with the /Q:A /R:N switches

ey TC ... nice to hear from you again!
(1) yup you granted my request on these previously ... the only thing that i noticed though is these files were only copied to an OEM directory ... created parallel to i386 & the rest ... OEMBIOS.* files already exist in i386 ... i do not know though if something is executed by the Siginet's addon ... i'll read further ...
(2) how about this?
(3) already read about this ... (been always recommending this link to the others who post related issues ... he! he!) ... KB894871 is a by-request only HF (would you have this HF TC ... could you kindly share it with me for download so i could test it too) while KB911564 if i recall it correctly is still needed for wmp11 as per S-M
(4) thanks!
(5) yup this screenshot is what i got (pls see screenshot ... oops i can't find it sorry) ... but i have th text copy attached
(6) how about this too?
(7) any comment on this?

really wish i could do more tests so i could participate more here ... he! he!
thanks!

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

hi! i'm just wondering since 7-zip has already been supported: Extended changelog for HFSLIP 1.0, would by any chance .rar be supported thanks!

This post has been edited by Kiki Burgh: Feb 1 2007, 07:04 AM

@TC

Could you add support for reg files in HFGUIRUNONCE?

thanks

You can put them in HFSVCPACK directory... the results is the same.

@Kiki
1) I only have HFSLIP do what the information files in Siginet's addons tell it to do. As far as I can see, the result should be that a CMD is executed during Windows setup that takes care of everything.
2) WMP11 is slipstreamed. You don't get WMP11 when clicking on "Windows Media Player"?
3) KB911564 is not related to any version of WMP in particular so you still need it when slipstreaming WMP11.
4) There's something fishy about the Sidebar addon. When I include it (RAR will be supported in next version), I get an error message at every login saying that Sidebar couldn't start because some file could not be found. The strange thing is: this file is not part of Windows, it's not included with the addon, and the forum post you linked to doesn't say anything about it either. Crazy stuff. I also tested the other two addons you mentioned and they are OK as far as I can see.
5) Do a proper run with the version I'll upload later and then see if you still get that error message.
6) Do they require a specific version of .NET? I see in your log that you are installing .NET 1.1 and .NET 2.0 in one go; this will cause other programs to think .NET 2.0 isn't installed yet before rebooting. If that's the case, either put those MSIs in HFGUIRUNONCE, or remove .NET 1.1 (or put .NET 1.1 in HFGUIRUNONCE).
7) Same as 5).

Removing "Dynamic.DST...2" from the search string will cause those lines which contain "FirstEntry" and "LastEntry" to be stripped as well. They should not be stripped.

Not really. "HKEY_CURRENT_USER" doesn't exist at T-13; any such entries will be converted to "HKEY_USERS" by Windows setup. And if you add entries at T-13 they may get overwritten again by applications that are installed later on.

New version underway.

This post has been edited by Tomcat76: Feb 1 2007, 01:29 PM

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

This post has been edited by whitehorses: Feb 1 2007, 08:08 PM

@whitehorses
I added your proposed changes except the /R switch. Is it really necessary? A dot is a wildcard and it's working fine without that switch for me.