[Camarade_Tux]

I took a look at the changelog,

Quote

KB840374 for WinXP SP1 is installed from SVCPACK now; report any installation issues...

Why ?

On my side, I had no bug.
With my latest iso, it installed without complaining. (but I have to check to be sure)

[Tomcat76]

The helpctr.exe and hscupd.exe files were properly updated but there's a lot more to that hotfix...

[Camarade_Tux]

Ok, thanks for your quick answer.
Do you think I can remove the files that get installed without problem (since I remove Help Center with nlite) ?

[Camarade_Tux]

And a quick request. I just slipstreamed an *ENU* hotfix. IMO HFSlip should display a warning about that.
I think before processing hfslip should search for ENU in filenames and if ENU is present and the language is not english, then it asks what to do : continue/abort.

Also, a cosmetical thing : if sfcfiles.dll is present in FIX, the cat removal screen appears but only says sfc.dll/sfc_os.dll is present and doesn't speak of sfcfiles.dll


btw, 10 minutes to complete. ^^

[Tomcat76]

You mean after installation of Windows? I don't know, simply because I don't know which files (other than the two mentioned above) are being updated. I don't fully understand what's going on inside that hotfix (especially after reading the installation INF file) which is why I just let the hotfix install itself through SVCPACK now.

But if you're removing Help Center with nLite you shouldn't be including this hotfix in the first place...

Camarade_Tux, on May 6 2006, 06:08 PM, said:

And a quick request. I just slipstreamed an *ENU* hotfix. IMO HFSlip should display a warning about that.

I don't think that's feasible. Some hotfixes with "ENU" in their name are OK to have and HFSLIP would have to be updated every time a new hotfix like that is released.

This post has been edited by Tomcat76: 06 May 2006 - 10:22 AM

[Camarade_Tux]

Understood, thanks.

I know I could avoid integrating this HF but I love the reg key saying it was installed. And I also keep it because staying up-to-date with all these fixes is hard so if I add one more difficulty, I'm going to get mad.
Also it seemed to me some hotfixes are doing more than simply updating one or two files.

Tomcat76, on May 6 2006, 05:21 PM, said:

Camarade_Tux, on May 6 2006, 06:08 PM, said:

And a quick request. I just slipstreamed an *ENU* hotfix. IMO HFSlip should display a warning about that.

I don't think that's feasible. Some hotfixes with "ENU" in their name are OK to have and HFSLIP would have to be updated every time a new hotfix like that is released.

I thought of something like :
dir /B >> hftemp.txt
findstr /C:ENU /F:hftemp.txt
Or maybe using the /D switch for findstr. (never used findstr so i don't really know)
Just a supposition.

This post has been edited by Camarade_Tux: 06 May 2006 - 10:26 AM

[Tomcat76]

This is what the hotfix is adding; you can just copy and paste it into HFSLIPWU.INF after running HFSLIP without that hotfix:

HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\KB840374","Installed",0x10001,1
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\KB840374","Comments",0,"Windows XP Hotfix - KB840374"
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\KB840374","Backup Dir",0,""
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\KB840374","Fix Description",0,"Windows XP Hotfix - KB840374"
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\KB840374","Installed By",0,""
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\KB840374","Installed On",0,""
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\KB840374","Service Pack",0x10001,2
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\KB840374","Valid",0x10001,1
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\KB840374\File 1","Flags",0,""
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\KB840374\File 1","New File",0,""
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\KB840374\File 1","New Link Date",0,""
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\KB840374\File 1","Old Link Date",0,""

There are hotfixes with "ENU" in their name which are OK to be slipstreamed in a non-English source, like the MSXML4 update if MSXML4 doesn't exist in the source language. Also, all Malicious Software downloads are identical so I'm just copying over the "ENU" version to the Dutch, French and German HFSLIP folders. To do what you want, HFSLIP would have to search for every hotfix with "ENU" in their name and then filter out a few like MSXML and Malicious Software. This "filter list" will have to be updated all the time.

I'm in the process of making a general HFSLIP answer file. Maybe something similar can be incorporated then.

[Camarade_Tux]

Thanks for these entries.

As for the ENU thing, OK. It was just a quick idea.

[Camarade_Tux]

I noticed a problem when using nlite and hfslip. While installing, XP complains about "OLEDB32R.DLL". Nothing appears in Evevntvwr and nothing in setuperr.log.

I'm doing more tests right now (especially : does this error appear without HFSlip ?).

edit:

This was without nLite. If I only use nLite, I have no problem. I had no problem two weeks ago so I'll try an older release and see how it performs (two weeks ago, I used an older release of KB908531).


Also, with only XP SP1 and HFSlip (no nLite!), I have a few missing updates (attached no_nlite.7z).

Attached File(s)

•  no_nlite.7z (1.98K)
  Number of downloads: 21

This post has been edited by Camarade_Tux: 07 May 2006 - 03:01 AM

[Tomcat76]

Q892944 - Fixed

Q899589 - Fixed

Q833989 - vgx.dll is not part of this hotfix.

Q911565 - wmpui.dll is part of WMP8 but not of WMP9 or 10. When you upgrade to WMP9 or 10, WMPUI.DLL is not updated; it isn't even used.

Q911562 - dbnetlib.dll is not part of this MDAC hotfix.


Try again with 60507a. Maybe it'll solve your OLEDB32R.DLL problem.

[Camarade_Tux]

Trying right now.

I just completed an install with the latest "final" release (late April). That time, I had no problem with OLEDB32R.dll.

[Camarade_Tux]

60507a did not fix the problem.

[Tomcat76]

This could be the old MDAC update. What's confusing is that the error description mentions OLEDB32R.DLL while its title speaks of OLEDB32.DLL. The latter comes with that MDAC update but the former does not.

This post has been edited by Tomcat76: 07 May 2006 - 04:21 AM

[Tomcat76]

OK. 60507b installs Q832483 via SVCPACK again like before.

[Kiki Burgh]

hi again sirs (Tomcat & tommyp)!
as always, many thanks for your feedback!

i just want to share what i've accomplished over the weekend (i was still using 503c though to make isos) ...
here's what i've found out:

(1) here are the added folders to the i386 dir + their contents:
041b
D:\SOURCESS\I386\041b\wmpshell.dll.mu_
D:\SOURCESS\I386\041b\xpsp2res.dl_
D:\SOURCESS\I386\041b\mlang.dll.mu_
D:\SOURCESS\I386\041b\wmm2res2.dll.mu_
D:\SOURCESS\I386\041b\wmploc.dll.mu_

041e
D:\SOURCESS\I386\041e\wmpshell.dll.mu_
D:\SOURCESS\I386\041e\xpsp1res.dl_
D:\SOURCESS\I386\041e\xpsp2res.dl_
D:\SOURCESS\I386\041e\browselc.dl_
D:\SOURCESS\I386\041e\inetres.dl_
D:\SOURCESS\I386\041e\mlang.dll.mu_
D:\SOURCESS\I386\041e\mshtmler.dl_
D:\SOURCESS\I386\041e\msoeres.dl_
D:\SOURCESS\I386\041e\shdoclc.dl_
D:\SOURCESS\I386\041e\wab32res.dl_
D:\SOURCESS\I386\041e\wmm2res2.dll.mu_
D:\SOURCESS\I386\041e\wmploc.dll.mu_

0402
D:\SOURCESS\I386\0402\wmploc.dll.mu_
D:\SOURCESS\I386\0402\wmpshell.dll.mu_
D:\SOURCESS\I386\0402\xpsp2res.dl_
D:\SOURCESS\I386\0402\mlang.dll.mu_
D:\SOURCESS\I386\0402\msi.dll.mu_
D:\SOURCESS\I386\0402\shdoclc.dl_
D:\SOURCESS\I386\0402\wmm2res2.dll.mu_
D:\SOURCESS\I386\0402\wmm2res.dll.mu_

0418
D:\SOURCESS\I386\0418\xpsp2res.dl_
D:\SOURCESS\I386\0418\mlang.dll.mu_
D:\SOURCESS\I386\0418\shdoclc.dl_
D:\SOURCESS\I386\0418\wmm2res2.dll.mu_
D:\SOURCESS\I386\0418\wmm2res.dll.mu_
D:\SOURCESS\I386\0418\wmploc.dll.mu_
D:\SOURCESS\I386\0418\wmpshell.dll.mu_

0425
D:\SOURCESS\I386\0425\wmpshell.dll.mu_
D:\SOURCESS\I386\0425\xpsp2res.dl_
D:\SOURCESS\I386\0425\mlang.dll.mu_
D:\SOURCESS\I386\0425\shdoclc.dl_
D:\SOURCESS\I386\0425\wmm2res2.dll.mu_
D:\SOURCESS\I386\0425\wmm2res.dll.mu_
D:\SOURCESS\I386\0425\wmploc.dll.mu_

0426
D:\SOURCESS\I386\0426\wmpshell.dll.mu_
D:\SOURCESS\I386\0426\xpsp2res.dl_
D:\SOURCESS\I386\0426\mlang.dll.mu_
D:\SOURCESS\I386\0426\shdoclc.dl_
D:\SOURCESS\I386\0426\wmm2res2.dll.mu_
D:\SOURCESS\I386\0426\wmm2res.dll.mu_
D:\SOURCESS\I386\0426\wmploc.dll.mu_

0427
D:\SOURCESS\I386\0427\xpsp2res.dl_
D:\SOURCESS\I386\0427\mlang.dll.mu_
D:\SOURCESS\I386\0427\shdoclc.dl_
D:\SOURCESS\I386\0427\wmm2res2.dll.mu_
D:\SOURCESS\I386\0427\wmm2res.dll.mu_
D:\SOURCESS\I386\0427\wmploc.dll.mu_
D:\SOURCESS\I386\0427\wmpshell.dll.mu_

(2) on the early stages of slipstreaming, HFSLIP reported that a particular KB added some folders; i tried taking it out though but the same additional folders (above) still showed up in SOURCESS

(3) i think i already resolved my XPize issue ... it was totally my bad ... ... i was using an XPized SP2 SOURCESS (as XPize has a feature to create a bootable XPized ISO) ... when i just used SOURCESS from HFSLIP, T-13 didn't show anymore the installation prompts of XPize ... oh well, a lesson learned!

(4) would RyanVM's Windows XP Post-SP2 Update Pack work hand in hand with HFSLIP? you see, in 1 of my experimental builds, i checked the contents of the package & removed from the HF directories those files that are in the cab file ... now when i ran qfecheck, it only shows those that were in the addon pack ... & not those in the HF folders ... i've attached a text file for your reference

(5) these 2 don't seem to do anything for the system: Themes_rytukz_VistaCG_addon_v1.0.cab Themes_rytukz_VistaCG_addon_v1.1.cab ... i tried each 1 at a time & i tried even having both ... to no avail (no theme added for me to use) ... checking both files though do not seem to show any pic file ... btw, 1.0 has a bigger size compared to 1.1 due to the difference in compression

(6) would it be possible to replace snap ons like dfrg.msc via HFEXPERT\APPREPLACEMENT?

(7) would the reference (or update at least) for slisptreaming CODECS be applicable to XP too? apparently, the discussion in a different thread is for 2K

(8) is there a difference between letting HFSLIP integrate SP than doing it manually?

(9) just a follow up, i know it might be too much to ask but could the entire process (from start to finish) be generated as a separate report too (so that we can see all the messages/errors/processes that have transpired during the run of HFSLIP)

(10) lastly, about timing the slipstreaming process, would it be alright to request for the start & end times be included in the log as well?

cheers!

Attached File(s)

•  hotfixes.txt (1.82K)
  Number of downloads: 27
•  HFSLIP.txt (5.49K)
  Number of downloads: 28

This post has been edited by Kiki Burgh: 08 May 2006 - 10:58 PM

[Super-Magician]

(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 !

This post has been edited by Super-Magician: 08 May 2006 - 07:39 AM

[tommyp]

6. Tread these waters carefully if you do. There are registry hives that get installed for these. Your best bet would be leave that alone (or rip them out). I guess you could always try it out. I never have.

7. You can slipstream codecs on 2k/xp/2k3.

[Tomcat76]

@Kiki

(2) Which hotfix?

(4) I think not. I'll have to check again.

(5) I'll have to see the TXTSETUP.SIF and the SYSOC.INF from that run. If everything's fine there, the problem is with the addon.

This post has been edited by Tomcat76: 08 May 2006 - 03:13 PM

[Kiki Burgh]

hi sirs (Tomcat, tommyp, Super-Magician)!
thanks again for the immediate response ...

my apologies but i actually had the file sitting somewhere here ... I couldn't find it though when i posted earlier ... no i found it ...
it is KB883921 (http://support.micro...kb/883921/en-us)

cheers!

Attached File(s)

•  extra_folders.jpg (22.75K)
  Number of downloads: 51

[Tomcat76]

Kiki...

HFSLIP doesn't support MUI updates. I don't think anyone here knows where all those *.mui files should go and there are 8 of each in that hotfix. Do you have an MUI version of XP?

General: Is it actually possible to make a regular WinXP source an MUI-enabled one out of the box?