[whitehorses]

@TP

Hohoho Some test would be appropriate to see how many things were filtered by it. In the gfinder.zip I added some strings manually but mostly arbitary to see how big the difference can be, but I'm just curious what are the results in the "real life".

I had an issue when I run hfcleanup, that hfslipwu.inf doesn't processed during install, so none of the runonce entries where added, so WINDOWS\HFSLIP folder had all the infs unprocessed and undeleted. This for example has not occured last time with /L, but i did not run all the removers (ZZZZs mostly. Then I tried another with all, but that install stopped. maybe because ZZZ_Englishonly, which I accidentally left in, despite the fact in WINNT.SIF I enabled Hungarian)

This post has been edited by whitehorses: 04 February 2007 - 10:32 AM

[whitehorses]

@TC

Quote

At the current rate of interest it won't make it into the final

It obfuscates the code too much, makes it f* hard to maintain or read, take that in account too.

This post has been edited by whitehorses: 04 February 2007 - 10:38 AM

[Tomcat76]

whitehorses, on Feb 4 2007, 05:37 PM, said:

It obfuscates the code too much, makes it f* hard to maintain or read, take that in account too.

If that were the case that would be my problem but I think it's not the case so it's not a problem

[tommyp]

Bug report with hfslip-70203b. In hfslip.cmd in svcpack, there is bad commandline
START/WAIT rundll32.exe setupapi.dll,InstallHinfSection DefaultInstall 128 ....

Version hfslip-1.2.2 does not have this problem. The correct commandline is:
rundll32.exe setupapi.dll,InstallHinfSection DefaultInstall 128 ....

[Super-Magician]

@tommyp, could that have something to do with the bug I reported on page 71, which seems to have gone unnoticed?

[tommyp]

I don't think those are the same INF files. The INF files I was talking about are the ones in the svcpack folder. These are launched via hfslip.cmd, also in svcpack. All of my hfslip###.inf files are working correctly. Open your hfslipwu.inf and see if something looks like this:

[ROROE]
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx\ZZA","200",0,"RunDll32.exe %11%\AdvPack.Dll,LaunchINFSection %10%\HFSLIP\HFSLP200.INF,DefaultInstall"

...

all of that was supposed to be one line

[Super-Magician]

The [ROROE] section is fine. Everything is as it's supposed to be there.

[Tomcat76]

@TommyP

I did that intentionally because I noticed that the CMD file that runs at first GUI logon (HFSLPGUI.CMD) would quit too soon if I didn't use START/WAIT for every line. I assumed that the same problem might occur with HFSLIP.CMD at T-13. Does this break installation of INF files?

Another thing...

The syntax
rundll32.exe setupapi.dll,InstallHinfSection DefaultInstall 128 filename.inf
seems to produce an error message at first GUI logon. I'm forced to do it like this:
rundll32.exe advpack.dll,LaunchINFSection filename.inf,DefaultInstall
Shouldn't it be done like this in HFSLIP.CMD as well?

[tommyp]

TC - The hfslip.cmd inf processing doesn't work in the test release, but it works fine in the latest final. In the beta, the INF doesn't process, the only thing I get is an error window (and an INF that doesn't process).

I never really understood why sometimes it's setupapi and sometimes advpack. But, if it ain't broke.....

This post has been edited by tommyp: 04 February 2007 - 05:10 PM

[Super-Magician]

In my second test using 70203b, I've just encountered the same problem denoted above.

 errors.jpg (44.56K)
Number of downloads: 15

This post has been edited by Super-Magician: 04 February 2007 - 07:12 PM

[Tomcat76]

Is it the same problem? I don't think TommyP uses HFSLPGUI.INF.

BTW... You are the second person for whom the GUI stuff runs at T-13. I don't get it... This NEVER happened to me.

I'm aware of some problems and they'll be fixed.

[Super-Magician]

I'll see if 70202b creates the same problem.

This post has been edited by Super-Magician: 04 February 2007 - 08:43 PM

[Tomcat76]

Hope the new version is better...

[Super-Magician]

Same exact error message with 70205a.

[tommyp]

Sorry, I can't test out the fix. I'm out of town for a week.

[Tomcat76]

@Super-Magician
1) Do you have any files in HFGUIRUNONCE?
2) Is HFSLPGUI.INF present in SOURCESS\I386?
3) Do you see any references to HFSLPGUI.INF in SOURCESS\I386\TXTSETUP.SIF?
4) Is "1200 = HFSLPGUI" defined in SOURCESS\I386\TXTSETUP.SIF?

I just finished a test with a fully updated XPSP2 source including .NET1/2/3, Adobe Reader 8.0, JRE 6.0, four addons (Sidebar, FGCBA Handler, VistaUAP and VAIOXP-b2) and some dummy INF and CMD files... Works as intended...

This post has been edited by Tomcat76: 05 February 2007 - 07:50 PM

[Super-Magician]

(1) Yes; a previous version worked with these files.
(2) Yes.
(3) Yes, once.
(4) Yes.

Everything seems to be OK, except for that one error. When I take a look inside C:\WINDOWS\HFSLPGUI, I discover that there's only four files (see my HFSLIP.LOG file below), none of which are HFSLPGUI.INF.


P.S. The driver files should not affect it in anyway because I have not changed them since my last successful run a few days ago.

This post has been edited by Super-Magician: 05 February 2007 - 09:07 PM

[Tomcat76]

You should be seeing four files, but it should be these:
HFGUI1.EXE
HFGUI2.EXE
HFSLPGUI.CMD
HFSLPGUI.INF

[daddydave]

Tomcat76, on Feb 4 2007, 08:58 AM, said:

At this point I'm more interested in comments on the "alternate input folders" feature. At the current rate of interest it won't make it into the final...

Perhaps if I understood their intended purpose...

[S3pHiroTh]

Hi Tomcat I've a question for you, you have written this:

Quote

[not XPSP1]new HFANSWER.INI variable (INCALLSKINS=1) to include all abandoned WMP skins that still exist in the source (overrides INCWMPCSKIN=1)

This means that, if I use Windows XP SP2, I should remove the old variable INCWMPCSKIN and replace it with the new INCALLSKINS?
Or INCALLSKINS has an highest priority than INCWMPCSKIN?