Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 

tommyp

Windows Updates

Recommended Posts

Parseus    0

mim0, MuppetHunter, or anybody ho knows it..

I found another mismatch in those lists you maintain.

The Cumulative Time Zone Update KB979306 have to be placed in HFSVCPACK_SW1\ folder according to list at vorck.com, and into HF\ folder according to mim0's list.

Which destination folder is correct?

Look at this post.

Share this post


Link to post
Share on other sites
Mim0    1

mim0, MuppetHunter, or anybody ho knows it..

I found another mismatch in those lists you maintain.

The Cumulative Time Zone Update KB979306 have to be placed in HFSVCPACK_SW1\ folder according to list at vorck.com, and into HF\ folder according to mim0's list.

Which destination folder is correct?

Tomalak gave the hint that it works also in HF.

So I think both folders are correct.

But for me, HF is the preferred place (when possible) because files are slipstreamed. At HFSVCPACK_SW1 the software is "just" installed at T13.

Edited by Mim0

Share this post


Link to post
Share on other sites
klenot    0

Thank you fellas for all your replies.

I found that selfextracting directx_feb2010_redist.exe contains .cab files for both x86 and for x64 platform. Slipstreaming such a package into 32bit Windows installation CD makes little sense.

I plan to extract this redist.exe, then delete *x64* files and repack it (by 7zip) into new selfextracting archive. It will be roughly half the size of the multiplatform redist.exe. Of course, I will include the rest of the files besides the *x86* (setup.exe, dsetup.dll, dsetup32.dll) into the new selfextracting archive.

Will such a x86-only stripped down version work?

Share this post


Link to post
Share on other sites
klenot    0

Shortly after posting my previuos post, I noticed the remark in mim0's list:

When you extract it manually to HFCABS, use all files MonthYear_*_x86.cab, except for *mdx* (see here).

Well, so extracting the MonthYear_*_x86.cab files (and no one other) into HFCABS\ folder is the working solution? Or besides MonthYear_*_x86.cab some others are also required in the HFCABS ?

Share this post


Link to post
Share on other sites
Parseus    0

Well, so extracting the MonthYear_*_x86.cab files (and no one other) into HFCABS\ folder is the working solution? Or besides MonthYear_*_x86.cab some others are also required in the HFCABS ?

For Windows XP you have to include only MonthYear_*_x86.cab in HFCABS. For Windows 2000 you have to include also BDANT.cab and dxnt.cab.

Share this post


Link to post
Share on other sites

I asked Windows Messenger 5.1 Portuguese (Portugal) PTG in Windows XP Newsgroups...

Keep the good work HFSleepers :)

Courtesy of the lovely Menthix:

http://tinyurl.com/3xw8qc7

--

Jonathan Kay

Microsoft MVP - Windows Live Messenger

MSN Messenger/Windows Messenger

MessengerGeek Blog: http://www.messengergeek.com

Messenger Resources: http://messenger.jonathankay.com

© 2010 Jonathan Kay - If redistributing, you must include this signature or citation

4 days to go!

Share this post


Link to post
Share on other sites
Mim0    1

I asked Windows Messenger 5.1 Portuguese (Portugal) PTG in Windows XP Newsgroups...

Keep the good work HFSleepers :)

Courtesy of the lovely Menthix:

http://tinyurl.com/3xw8qc7

--

Jonathan Kay

Microsoft MVP - Windows Live Messenger

MSN Messenger/Windows Messenger

MessengerGeek Blog: http://www.messengergeek.com

Messenger Resources: http://messenger.jonathankay.com

© 2010 Jonathan Kay - If redistributing, you must include this signature or citation

4 days to go!

Thx!! I appreciate it :)

Share this post


Link to post
Share on other sites
Guest   
Guest

I would remove KB979332. It's not part of a stock XP. Some encoder needs to be installed for that update to be relevant.

2qk54yq.jpg

Share this post


Link to post
Share on other sites
Mim0    1

I would remove KB979332. It's not part of a stock XP. Some encoder needs to be installed for that update to be relevant.

You're right. Custdll.dll and Wmenceng.dll are not on my system. I change the list. THX for checking the current changes!!! :)

Share this post


Link to post
Share on other sites
klenot    0

Guys,

I have the vanilla XP SP3 install media and want to make it up-to-date. Do I need to slipstream both of these patches:

- msxml6-KB973686-XXX-x86.exe (MSXML 6.0 Service Pack 2)

- WindowsXP-KB973687-x86-XXX.exe (Update for Windows XP (MSXML3 & MSXML6))

M$'s KB article states, that KB973686 is only for Win XP SP2.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Recently Browsing   0 members

    No registered users viewing this page.

×