@the_guy...

The HfNetChk message for dxtmsft.dll on Win2K appears to be gone with the QFE files.

Acknowledge. Over.

Ok. I couldn't reproduce it.

the_guy

EDIT: The band-aid fix for the *.hp.* files only works on .sys files. Maybe redo it so it goes *.hp.*

There are only two hotfixes ATM which have these *.hp.* files and they're all *.hp.sys files. I'm a bit afraid of making generic fixes *too* generic so I wanna hold off changing that to *.hp.* until there are more file types involved....

MS05-039 is one of those updates.

SP1GDR: umpnpmgr.dll, umpnpmgr.hp.dll

SP1QFE: umpnpmgr.dll

the_guy

That one slipped right past me. OK... I changed HFSLIP so it checks for *.hp.* instead of *.hp.sys.

Everything appears to be OK with WinXP SP2.

Does anyone know how XPSP1 is doing?

After I hear back from TommyP, I'll make it a final.

yup ... all's fine with XP from my end (except for testing it with the latest HFCLEANUP ... can't seem to get it to work for me ... although i'll be following some suggestions by TP
yey ... a new final (60712) for us to finalize some builds XP was the 1st 1 to be cleared

quick Q --- was test release 60712a technically the final 60712?

I was telling myself "another patch tuesday next week". I just realized July's patch tuesday is past. :/
Thank you for the new release.

@Kiki Burgh:
Technically, yes. The background color is different, though...

@Camarade_Tux:
No problem. I wish I had you in here earlier to see if XPSP1 is OK...
BTW... I searched around the Internet a few days ago for "HFSLIP" in different languages and found a couple of forum posts from you. So thanks to you too...

It reminds me I have some propaganda to do on hardware.fr.

And, "my" computer has been sent back but I manage to borrow another one from time to time (my drug ), and the one I use to test is not the same, it's a much more powerful one so I should be able to test next releases.

A bit late but I can at last confirm XP SP1a is working perfectly.

That's good to hear.

BTW... There's a new one...

Tomcat: I know HFSLIP_60716exp2 is an experimental test release, but color 48 is very hard to read.

You like 47 better?

Actually, now I'm thinking it was just my computer screen. On this computer, 48 looks good.

However, I would prefer 47, or maybe one of these: 17, 27, 57

I changed it to 47. The blue one is OK but I think the red is important to show that it's experimental.

BTW... The next update is going to be even more experimental, so that one will have to burn. What about yellow text on a red background?

Just kidding...

How about using C7 (grey on red) or FC (red on white)?

i know this is a dumb q ... but what is the difference of an experimental test rel? is it something like a candidate for test release? he! he!

You could call it like that, yes.

Testing right now.

My first impression ?
Flashy colors.

Installation can not continue:
Maybe (probably) because nlite has an option to recompress ASMS files; I had one bug with that option and this is only an option because it has been reported to sometimes cause bugs

-Error:
SXS.DLL : syntax error in the manifest file or strategy file "D:\I386\asms\10\msft\windows\gdiplus\GDIPLUS.CA_ at line 0 (file non-empty)
-Error:
Installation failed : D:\I386\ASMS. Error message : Analysis error of the manifest file : invalid character has been found in the text content.
-Fatal Error:
One of the component Windows needs to continue installation program could not be installed.

(of course this is translated, and btw I'm a bit tired, it's so hot here nobody can sleep)

I'm going to try to try (not a mistake ) again, without nlite's ASMS RECOMPRESSION.




Btw, I have two new folders in i386 : ic (contains NETIP6.IN_) and pconfig (contains \10\msft\windows\gdiplus which contains GDIPLUS.CA_ and GDIPLUS.MA_)

Nope, changed nothing.

I attached my HFSLIP.LOG.

I'll probably try tomorrow without nlite.
(I always use nlite because it makes the installation really much faster)


Also, I have a question about Q832483.EXE.
This updates annoys me because it takes 2MB on the CD and mostly contains files I will never need (for 2K, winME...). What should I use to recraft this package ?

Comrade - Do you remove mdac using nlite? If you remove mdac, then why bother with adding an mdac update? For my home machine, I find zero use for mdac.

I don't remove MDAC.
I don't find any use for MDAC but I keep it for compatibility.
Maybe I'll remove it but I have my µACD to finish first (application installs)

@Camarade

Those two folders (and any other irrelevant tag folders) should be removed now when using 718exp1. I'm not sure if this will fix your problem, though. I find it quite a coincidence that Windows setup trips over the exact same file that's also in pconfig. Earlier versions of HFSLIP always removed pconfig so that's what 718exp1 is doing now too. If you still get the installation error, I'll copy pconfig into ASMS.

Camarade Tux, i also encoutner errors (&/or my installation halted) if ASMS compression is enabled. Leaving it by default does not give the error.

Another new version... or actually not. It was made yesterday but I did extensive testing with Windows 2000 first. Windows 2000 (if IE6 is included) will namely benefit from the move to QFE binaries too.

For the record... I did this mainly for myself. There are a few hotfixes for which the QFE files *have* to be used, but I sometimes forget to update HFSLIP when a newer version of that hotfix arrives (eg, the IE Cumulative updates). By using QFE files for *every* hotfix I no longer need to worry about this.

By now, there should be no issues with Windows Update or HfNetChk anymore and no more installation errors either. But please report back if you encounter problems *using* Windows or its programs. I don't foresee any problems but you can never be sure.

I thought of an idea! If Aserone's switchless .net 2 installer is detected in HFSVCPACK, why not copy reg.exe from support.cab to i386, makecab it, and have it copy over to system32 in setup, with adding the entries to dosnet and txtsetup. Of course, this would only be on 2000 as xp and 2003 already have reg.exe in i386.

Opinion?

the_guy

My opinion? It's easy to do it; there's even two ways: I can have it extracted while HFSLIP is running, or have it extracted during Windows setup at T-13 (before .NET 2.0 would be installed).

But I don't know if it would be that useful...

1) HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PCHealth doesn't exist on a Win2K box, and I believe no Win2K user experienced problems installing .NET 2.0 so the other reg key isn't important.

2) Windows 2000 has problems executing many programs from a batch file at T-13 if no full path is provided, as is the case with REG.EXE in the batch file inside Aserone's .NET 2.0 installer. One example of a file that will fail is REGEDIT.EXE.

3) What about people who don't want it? Do I make this configurable via HFANSWER.INI?

Ok. I don't know. Maybe edit the installer so it doesn't do that at all?

the_guy

That involves 7-zip or similar program. I've tried this by the way with my MultiCompiler program and it failed. I still didn't have time to figure out why. All I did was do the same as Aserone except that I used an INF for the registry edits (so REG.EXE wouldn't be required).

hi TC! i think i'd go for the 1st 1: "while HFSLIP is running" for the ff reasons: (1) some apps require that .NET 2.0' already present before they get installed (?) ... & (2) this is nothing serious but the wait time at T-13 makes it appear (for the uninitiated ) that sys has locked-up
indeed HFANSWER.INI is very helpful!

Hi Kiki...

This is about extracting REG.EXE into WINNT\SYSTEM32 on Windows 2000, which only takes a second.

OK. REG.EXE added for Win2K.

Does that require hfanswer.ini? If it does, can you make it an option in the cmd file itself?

Also, is there a way to get the 911562 hotfix for MDAC 2.8 SP1 integrated into the install?

the_guy

he! he! i thought 'twas .net2 ...

Yes. I thought there might be people who don't want/need it.

Not really sure what you mean. But if you prefer to set variables inside the main HFSLIP script directly, that's always been possible. Anything that's inside HFANSWER.INI can be set in the main HFSLIP script directly, but the lines need to be preceded by "SET ".

Depends on what you mean by "install". Since version 60624 (and some of the test releases before that), HFSLIP integrates the hotfix into the Windows source, meaning that it's going to be installed during the first GUI logon, right after MDAC 2.8 SP1 is installed.

Some time ago, I tried to integrate the hotfix into the MDAC 2.8 SP1 installer directly but it didn't work. The installer silently refused to copy over the binaries that came from the hotfix (even after running modifyPE on them), and the silent installation was always interrupted by an informational dialog message telling me that "some component" was about to be installed. That dialog had two buttons: "OK" and "More info". I abandoned this testing after a few days.

I mean integrate the hotfix files into the mdac executable, so the install takes less time.

What I mean by a prompt is have something like the driver compression screen, but it gets bypassed if xp or 2003 is detected as the source. Like, type reg if you want reg.exe put into your source. press enter if you don't.

the_guy

Something like in 60721c?
I'm gonna have to run this by TommyP, though...

That's what I mean.

the_guy

Removed again. Sorry...

Hello,

did an install of my Win XP SP2 today, with test release 60722a. I noticed two little bugs:

1. KB898461 (new version of the package installer, 'update.exe') was not integrated successfully. IE complained about that missing update when trying to access WU. After I installed it manually, everything worked fine, and WU did not find any other missing updates - they were all slipstreamed without problems.
2. Not sure about that one, but I also tried to integrate the optional update KB914440 v6 (for diagnosing network problems). It seems to be a regular hotfix, but was not slipstreamed, too. Don't put too much effort into it, it's only a minor problem and not really an important update.
Greets,

Tomalak

New version of KB898461? I just downloaded it again and it's still the one from June 2005...

OK... I found it. Sorry...

Is it just an HFSLIP problem?

can someone post a link to the new version please?

the_guy

KB914440 isn't really a "regular" hotfix because it creates a new folder containing three new files. If you want, you can add support for it yourself...

Open the HFSLIP script in Notepad (make sure word wrap is disabled) and find "POST HFX HANDLING". It's the title of a section. Scroll down until you're at the end of that section (above the "MSXML FILES" section).
Insert a blank line right above the words "GOTO EOF", and paste the following code into the blank line:


It *was* just an HFSLIP problem. It's no longer a problem.

It's in the main post, as always...

I mean the new version of 898461. I can't find it anywhere.

Me neither. The German version is a year old too. I think Tomalak was referring to something else.