[bphlpt]

Sorry. My misunderstanding. I thought you were looking for a home for the files. Never mind.

Cheers and Regards

[Parseus]

Mim0, on 25 April 2010 - 04:30 AM, said:

- I make an OS-detection of the SOURCE-folder to take the correct update-list automatically.

I extended your SP detection to simple OS and SP detection few minutes ago:

REM --------------------------------------------------------------------
REM Detection of operating system and Service Pack already included in SOURCE 
REM --------------------------------------------------------------------
FOR /l %%i in (1,1,4) DO (
  IF EXIST SOURCE\cdromsp%%i.tst (
    SET sp=SP%%i
    SET OS=2K
  )
  ELSE IF EXIST SOURCE\WIN51IP.SP%%i (
    SET sp=SP%%i
    SET OS=XP
  )
)

I'm not exactly sure how to do that for automatic updates, though.

Mim0, on 26 April 2010 - 03:59 AM, said:

My files are on a "normal" web-server, probably Parseus can find also a way for the W2K-list...

I was thinking about my own site with updates, but also with hotfixes. I'm still thinking, though

This post has been edited by Parseus: 26 April 2010 - 08:34 AM

[Mim0]

Parseus, on 26 April 2010 - 08:30 AM, said:

REM --------------------------------------------------------------------
REM Detection of operating system and Service Pack already included in SOURCE 
REM --------------------------------------------------------------------
FOR /l %%i in (1,1,4) DO (
  IF EXIST SOURCE\cdromsp%%i.tst (
    SET sp=SP%%i
    SET OS=2K
  )
  ELSE IF EXIST SOURCE\WIN51IP.SP%%i (
    SET sp=SP%%i
    SET OS=XP
  )
)

Same idea!

Some questions for the w2k-version:
For MSXML: Why you can define in the INI the installation (integration) of MSXML2? MSXML2 is part of W2K (I thought). You should add MSXML3 instead...

For DX9: Do you know the reason two have the options for Dx9-Standard and Dx9-Gaming?

Another for DX9: You have two sections calling DX9X. "My" DX9X is a list of CABs for DX9 (DX9-eXtracted)...

[Parseus]

Mim0, on 26 April 2010 - 01:05 PM, said:

Some questions for the w2k-version:
For MSXML: Why you can define in the INI the installation (integration) of MSXML2? MSXML2 is part of W2K (I thought). You should add MSXML3 instead...

For DX9: Do you know the reason two have the options for Dx9-Standard and Dx9-Gaming?

Another for DX9: You have two sections calling DX9X. "My" DX9X is a list of CABs for DX9 (DX9-eXtracted)...

MSXML: I based my HFSLIPFC 2K on bristols list, but according to this, MSXML2 (like MSXML3) is already included. Could anyone give me versions of msxml2.dll, msxml2a.dll and msxml2r.dll from Windows 2000 (if they exist on CD)? I need to check these updates from bristols list, but I haven't got 2000 disc now.

DX9: I had a small discussion with bristols and in fact it's up to user - he can use DX9 standard (I call it "lite") or DX9 gaming ("full" - DX9 standard + additional binaries mainly for gaming).

Sections with DX9X:

REM --------------------------------------------------------------------
REM Check if DX9 is already extracted
REM --------------------------------------------------------------------
IF EXIST !xdx9File! (
SET dx=DX9X
) ELSE IF EXIST !dx9File! (
SET dx=DX9X
) ELSE IF EXIST !d9File! (
SET dx=DX9
) ELSE (
SET dx=DX7
)

That code checks if exists:
1) extracted DX9 for gaming
2) unextracted DX9 for gaming
3) DX9 standard (unextracted)
4) no DX9 redistributables

DX9 gaming don't supersedes DX9 standard. I think I'll change that code a bit.

This post has been edited by Parseus: 27 April 2010 - 10:34 AM

[Mim0]

Parseus, on 26 April 2010 - 01:55 PM, said:

Mim0, on 26 April 2010 - 01:05 PM, said:

For MSXML: Why you can define in the INI the installation (integration) of MSXML2? MSXML2 is part of W2K (I thought). You should add MSXML3 instead...

MSXML: I based my HFSLIPFC 2K on bristols list, but according to this, MSXML2 (like MSXML3) is already included. Could anyone give me versions of msxml2.dll, msxml2a.dll and msxml2r.dll from Windows 2000 (if they exist on CD)? I need to check these updates from bristolslist, but I haven't got 2000 disc now.

I think my thoughts yesterday are not correct. MSXML3 was shipped with W2K, not MSXML2.

Parseus, on 26 April 2010 - 01:55 PM, said:

REM --------------------------------------------------------------------
REM Check if DX9 is already extracted
REM --------------------------------------------------------------------
IF EXIST !xdx9File! (
  SET dx=DX9X     <<<============================== !!!
) ELSE IF EXIST !dx9File! (
  SET dx=DX9X     <<<============================== !!!
) ELSE IF EXIST !d9File! (
SET dx=DX9
) ELSE (
SET dx=DX7
)

In both cases you are using DX9X as the section-name for DirecX-Updates.

In general: The behaviour of the fc is the following: All sections (of the files containing in the fileset) with the same name are taken!

In your case: You have two DX9X-sections in your fc. Both are taken if you set dx to DX9X.

This post has been edited by Mim0: 26 April 2010 - 10:49 PM

[Parseus]

Mim0, on 26 April 2010 - 10:47 PM, said:

I think my thoughts yesterday are not correct. MSXML3 was shipped with W2K, not MSXML2.

MSXML2 was shipped with IE 5.01, which is by default included in Windows 2000 SP4.

Mim0, on 26 April 2010 - 10:47 PM, said:

In both cases you are using DX9X as the section-name for DirecX-Updates.

In general: The behaviour of the fc is the following: All sections (of the files containing in the fileset) with the same name are taken!

In your case: You have two DX9X-sections in your fc. Both are taken if you set dx to DX9X.

Fixed. New version will be released after I clear the situation about MSXML.

EDIT: I am working on merged HFSLIP FC now and I shortened the main configuration file (it's attached to that post).

 hfslipfc.ini (5.33K)
Number of downloads: 9

I need to ask if I am modifying script correctly, though:

REM --------------------------------------------------------------------
REM Check if DX9 is already extracted
REM --------------------------------------------------------------------
IF !OS!== 2K (
IF EXIST !xdx9File! (
SET dx=DX9X
) ELSE IF EXIST !d9File! (
SET dx=DX9
) ELSE (
SET dx=DX7
)
) ELSE IF !OS!==XP (
IF EXIST !xdx9File! (
 SET dx=DX9X
) ELSE (
 SET dx=DX9
)
)

Is that code correct?

This post has been edited by Parseus: 27 April 2010 - 10:37 AM

[Parseus]

New version released. I decided to move MSXML2 to Windows updates, because it's shipped with IE 5.01, which is by default included in Windows 2000.

[Mim0]

For supporting different windows-versions from one file-checker I've made from your current version an extension for the new file-checker.
Extract it in the same folder where the file-checker is.

Two things I saw:
- "Server" seems for me not working
- dx-recognition not correct.
Case: You WANT have Dx9 and don't have it already. Your script decides to take DX7 instead!

I don't fixed it when making an extension from hfslipfc2k.cmd. It was too late yesterday...

It would be nice if you use the new file-checker and the extension-mechanism. It's easier/better to maintain for us both. The same code-base with different update-lists.

Regards, Mimo

Attached File(s)

•  hfslipfc-2k.rar (8.55K)
  Number of downloads: 21

This post has been edited by Mim0: 29 April 2010 - 10:48 PM

[tommyp]

This is a cool tool. Thanks guys. I have a little prob with it though. It seems as if I'm getting everything is missing from my hf and hfcabs folders (probably others too). I know that their not up to snuff, but the 2k update rollup and ie6 cabs should have been detected. I'm not sure how I can help. I used the current fileset as of apr 30th.

[Mim0]

tommyp, on 30 April 2010 - 06:06 AM, said:

I have a little prob with it though. It seems as if I'm getting everything is missing from my hf and hfcabs folders (probably others too). I know that their not up to snuff, but the 2k update rollup and ie6 cabs should have been detected. I'm not sure how I can help. I used the current fileset as of apr 30th.

Hmmm... I'm not sure if I can help at this moment because I think first the list should be checked. When I would be Parseus I would ask you for a log-file and the file-checker-INI

This post has been edited by Mim0: 30 April 2010 - 04:04 PM

[Parseus]

tommyp, on 30 April 2010 - 06:06 AM, said:

This is a cool tool. Thanks guys. I have a little prob with it though. It seems as if I'm getting everything is missing from my hf and hfcabs folders (probably others too). I know that their not up to snuff, but the 2k update rollup and ie6 cabs should have been detected. I'm not sure how I can help. I used the current fileset as of apr 30th.

Thanks for report. It seems that Mim0 made a few errors during creating that extension. I've already fixed that, but I'll release new version after I'll fix problems with Server updates and DirectX (I haven't got any ideas BTW).

EDIT: Could anybody give me an info about this update?

This post has been edited by Parseus: 02 May 2010 - 08:31 AM

[tommyp]

The activex killbits is typically an update that has a bunch of registry edits. Typically no binaries are added to the OS. The killbits updates do not come out every month, but the latest update should be the only killbit update you will need. I think the latest one is KB978262 which was released earlier this year.

[Parseus]

tommyp, on 02 May 2010 - 07:58 AM, said:

The activex killbits is typically an update that has a bunch of registry edits. Typically no binaries are added to the OS. The killbits updates do not come out every month, but the latest update should be the only killbit update you will need. I think the latest one is KB978262 which was released earlier this year.

I see. Thanks for the info

[Parseus]

New version released.

[tommyp]

I have my dx9 extracted in hfcabs. Is there a switch to show that?

[Parseus]

tommyp, on 12 May 2010 - 04:23 PM, said:

I have my dx9 extracted in hfcabs. Is there a switch to show that?

If you extracted DX9 (gaming) from Feb 2010, it should be visible as in XP version. If you extracted old DX9 (standard) - it won't be. I think I have to extend detecting DX9 version.

EDIT: There was an error in detecting DX9. I fixed that and added also detecting of extracted DX9 (standard).

This post has been edited by Parseus: 14 May 2010 - 11:23 AM

[Parseus]

New version released.

[stephan_bauer]

Hello Parseus,

I configured HFSLIPFC-2K to use Mediaplayer 9 updates but after installing Windows Update wants to install Mediaplayer 6 updates also.

These are the updates:
WindowsMedia6-KB925398-v2-x86-DEU.exe
WindowsMedia64-KB954600-x86-DEU.exe
WindowsMedia64-KB974112-x86-DEU.exe

Regards

Stephan

[My2GirlsDad]

Greeting Parseus,

I have run the latest version of your script and found the following issues:


I have SP0 in source and received the following “error”:

-----------------------------------------------------------
Running HFSLIPFC v.2010/05/14 at Thu 05/14/2010 21:11:05.71
-----------------------------------------------------------
wrong (S): HF\W2KSP4_EN.exe (Service Pack 4 for Windows 2000, it's for SP4)


I want to update VBScript to v5.7. I put KB981349 in HF and received the following “errors”:

-----------------------------------------------------------
Running HFSLIPFC v.2010/05/14 at Thu 05/14/2010 21:11:05.71
-----------------------------------------------------------
obsolete: HF\Windows2000-KB981349-x86-ENU.EXE (MS10-022: VBScript update from 5.1 to 5.7, VBScript update applicable for Windows Script 5.7)
missing (S): HF\Windows2000-KB981349-x86-ENU.EXE (MS10-022: VBScript update from 5.1 to 5.7)
missing (S): HF\Windows2000-KB981350-x86-ENU.EXE (MS10-022: VBScript (update from 5.1 to 5.6 version))


You have marked the following for server but it is for both. It should not be marked as Server only. It is needed to keep MU from asking for KB926122.

-----------------------------------------------------------
Running HFSLIPFC v.2010/05/14 at Thu 05/14/2010 21:11:05.71
-----------------------------------------------------------
wrong (S): HF\Windows2000-KB973037-x86-ENU.EXE (MS09-066: Active Directory, it's for SERVER)


The following updates are for WMP6. Even though I am slipstreaming WMP9, WMP6 is not replaced. I have not found a way to successfully stop WMP6 from installing using HFSLIP. It breaks the install. Since this is the case, these updates would be needed whether you slipstream WMP9 or not. As stephan_bauer reported MU and WU says there are needed.

-----------------------------------------------------------
Running HFSLIPFC v.2010/05/14 at Thu 05/14/2010 21:11:05.71
-----------------------------------------------------------
wrong (S): HF\WindowsMedia6-KB925398-v2-x86-ENU.exe (MS06-078: Windows Media Formats, it's for WMP6)
wrong (S): HF\WindowsMedia64-KB954600-x86-ENU.exe (MS08-076: Windows Media Components, it's for WMP6)
wrong (S): HF\WindowsMedia64-KB974112-x86-ENU.exe (MS09-052: ASF files, it's for WMP6)


The following update is for Server only and you have it marked as both.

-----------------------------------------------------------
Running HFSLIPFC v.2010/05/14 at Thu 05/14/2010 21:11:05.71
-----------------------------------------------------------
missing (S): HF\Windows2000-KB926121-x86-ENU.EXE (MS06-077: Remote Installation Services


The following update is an advisory that is required to keep MU happy. It is for Enhancements for the Indeo Codec.

-----------------------------------------------------------
Running HFSLIPFC v.2010/05/14 at Thu 05/14/2010 21:11:05.71
-----------------------------------------------------------
unknown: HF\windows2000-kb955759-x86-enu.exe


This is an update for both WMP6.4 and WMP9. It should be placed in HFSVCPACK as the WMP9 part installs correctly in HF but not the WMP6.4 part. See my explanation above.

-----------------------------------------------------------
Running HFSLIPFC v.2010/05/14 at Thu 05/14/2010 21:11:05.71
-----------------------------------------------------------
missing (S): HF\Windows2000-WindowsMedia-KB977816-x86-ENU.EXE (MS10-026: MPEG Layer-3 Codecs)


I hope this information helps to make an already great tool even better. Thanks for all your hard work and expertise.

My2GirlsDad

[Parseus]

My2GirlsDad, on 16 May 2010 - 08:07 PM, said:

I have SP0 in source and received the following “error”:

-----------------------------------------------------------
Running HFSLIPFC v.2010/05/14 at Thu 05/14/2010 21:11:05.71
-----------------------------------------------------------
wrong (S): HF\W2KSP4_EN.exe (Service Pack 4 for Windows 2000, it's for SP4)

This issue is connected with problem which I described here.

My2GirlsDad, on 16 May 2010 - 08:07 PM, said:

I want to update VBScript to v5.7. I put KB981349 in HF and received the following “errors”:

-----------------------------------------------------------
Running HFSLIPFC v.2010/05/14 at Thu 05/14/2010 21:11:05.71
-----------------------------------------------------------
obsolete: HF\Windows2000-KB981349-x86-ENU.EXE (MS10-022: VBScript update from 5.1 to 5.7, VBScript update applicable for Windows Script 5.7)
missing (S): HF\Windows2000-KB981349-x86-ENU.EXE (MS10-022: VBScript update from 5.1 to 5.7)
missing (S): HF\Windows2000-KB981350-x86-ENU.EXE (MS10-022: VBScript (update from 5.1 to 5.6 version))

Fixed. It was caused by wrong detection of scripten.exe.

My2GirlsDad, on 16 May 2010 - 08:07 PM, said:

You have marked the following for server but it is for both. It should not be marked as Server only. It is needed to keep MU from asking for KB926122.

-----------------------------------------------------------
Running HFSLIPFC v.2010/05/14 at Thu 05/14/2010 21:11:05.71
-----------------------------------------------------------
wrong (S): HF\Windows2000-KB973037-x86-ENU.EXE (MS09-066: Active Directory, it's for SERVER)

Fixed.

My2GirlsDad, on 16 May 2010 - 08:07 PM, said:

The following updates are for WMP6. Even though I am slipstreaming WMP9, WMP6 is not replaced. I have not found a way to successfully stop WMP6 from installing using HFSLIP. It breaks the install. Since this is the case, these updates would be needed whether you slipstream WMP9 or not. As stephan_bauer reported MU and WU says there are needed.

-----------------------------------------------------------
Running HFSLIPFC v.2010/05/14 at Thu 05/14/2010 21:11:05.71
-----------------------------------------------------------
wrong (S): HF\WindowsMedia6-KB925398-v2-x86-ENU.exe (MS06-078: Windows Media Formats, it's for WMP6)
wrong (S): HF\WindowsMedia64-KB954600-x86-ENU.exe (MS08-076: Windows Media Components, it's for WMP6)
wrong (S): HF\WindowsMedia64-KB974112-x86-ENU.exe (MS09-052: ASF files, it's for WMP6)

Fixed.

My2GirlsDad, on 16 May 2010 - 08:07 PM, said:

The following update is for Server only and you have it marked as both.

-----------------------------------------------------------
Running HFSLIPFC v.2010/05/14 at Thu 05/14/2010 21:11:05.71
-----------------------------------------------------------
missing (S): HF\Windows2000-KB926121-x86-ENU.EXE (MS06-077: Remote Installation Services

Fixed.

My2GirlsDad, on 16 May 2010 - 08:07 PM, said:

The following update is an advisory that is required to keep MU happy. It is for Enhancements for the Indeo Codec.

-----------------------------------------------------------
Running HFSLIPFC v.2010/05/14 at Thu 05/14/2010 21:11:05.71
-----------------------------------------------------------
unknown: HF\windows2000-kb955759-x86-enu.exe

Fixed. However, the problem is that currently downloading this update via KB article is currently available only for Server 2003 x64 and ia64 (at least for Polish update, I don't know about other languages, but English works fine).

My2GirlsDad, on 16 May 2010 - 08:07 PM, said:

This is an update for both WMP6.4 and WMP9. It should be placed in HFSVCPACK as the WMP9 part installs correctly in HF but not the WMP6.4 part. See my explanation above.

-----------------------------------------------------------
Running HFSLIPFC v.2010/05/14 at Thu 05/14/2010 21:11:05.71
-----------------------------------------------------------
missing (S): HF\Windows2000-WindowsMedia-KB977816-x86-ENU.EXE (MS10-026: MPEG Layer-3 Codecs)

Added.

Thanks for report, guys