Jump to content

Where's WMP10?


Yzöwl

Recommended Posts

Ran my first hfslip and installed, but wmp is still at version 9

Any Ideas!

Names of the files in your HF folder: 
KB873333.exe
KB873339.exe
KB885250.exe
KB885626.exe
KB885835.exe
KB885836.exe
KB886185.exe
KB887472.exe
KB887742.exe
KB888113.exe
KB888302.exe
KB890046.exe
KB890859.exe
KB891781.exe
KB893066.exe
KB893086.exe
KB893756.exe
KB893803.exe
KB894391.exe
KB896358.exe
KB896422.exe
KB896423.exe
KB896428.exe
KB896727.exe
KB898461.exe
KB899587.exe
KB899588.exe
KB899591.exe
KB901214.exe
MP10Setup.exe
WindowsUpdateAgent20-x86.exe
WM9Codecs.exe

<Edit>

incidentally, I'm using HFSLIP_51006.cmd

</Edit>

Edited by Yzöwl
Link to comment
Share on other sites


Of course it didn't work. The solution is really easy. You didn't follow the directions :) , especially the part on "which file goes where". There is a subtopic in this forum. http://www.msfn.org/board/index.php?showtopic=57603 and it appears you are using HFSLIP for XP so you may want to look here:

http://www.vorck.com/hfslip.html#11

Bottom line, you have to rename the files back to the way you downloaded them from Microsoft. Once you rename them correctly, then HFSLIP will work. Post back if you run into probs.

Link to comment
Share on other sites

From the instructions page

  • Windows Media Player 10
    Media Player 10 can go into HF folder if you want it slipstreamed.

From the link you gave

  • Names of the files in your HF folder:
    MP10Setup.exe <---Optional Windows Media Player 10

From my list

  • Names of the files in your HF folder:
    MP10Setup.exe

Link to comment
Share on other sites

If you want hotfixes slipstreamed, please rename your KB file names BACK to the way you originally got them from Microsoft. Apparantly you downloaded the hotfixes from a source other than microsoft or you renamed them. If on the other hand you only want XP with WMP10 slipstreamed, delete the wrongly named hotfixes from the HF folder and leave MP10setup there. FYI, HFSLIP doesn't work if you rename files (the instructions on FDV's site say this too).

Link to comment
Share on other sites

I haven't searched the whole file enough yet to disagree with you, but your site documentation only says

  • Do not rename the files. (However, it is ok to put a prefix to the filename in case you want to segregate some hotfixes.)

It doesn't say that if you have any renamed files the whole process will break regardless of any correctly named files. If you can change the prefix, then it suggests to me that the cmd file must be looking at the suffixes. However there is no consistency in the suffixes, most contain a language code, but not all. In the cmd file I cannot see any use of %LNG% variable at all and the %LG% variable is used only with WUA20, which is also named correctly. Other than that I only see findstr references to 'KB??????' which all of my files contain within their names.

Could you please explain!

Link to comment
Share on other sites

@Yzöwl - I kind of assumed that if a file prefix is changed, it was the addition of a few characters and not rename the entire file. For your XP installation, here is what your HF folder should be. If you use this fileset, then you are good to go.

msxmlcab.exe
WindowsInstaller-KB893803-v2-x86.exe
WindowsXP-KB873333-x86-ENU.exe
WindowsXP-KB873339-x86-ENU.exe
WindowsXP-KB884020-x86-enu.exe
WindowsXP-KB885222-v2-x86-ENU.exe
WindowsXP-KB885250-x86-ENU.exe
WindowsXP-KB885626-v2-x86-enu.exe
WindowsXP-KB885835-x86-ENU.exe
WindowsXP-KB885836-x86-ENU.exe
WindowsXP-KB886185-x86-enu.exe
WindowsXP-KB886677-x86-enu.exe
WindowsXP-KB887742-x86-ENU.exe
WindowsXP-KB887797-x86-enu.exe
WindowsXP-KB888113-x86-ENU.exe
WindowsXP-KB888240-x86-ENU.exe
WindowsXP-KB888302-x86-ENU.exe
WindowsXP-KB890046-x86-ENU.exe
WindowsXP-KB890175-x86-ENU.exe
WindowsXP-KB890859-x86-ENU.exe
WindowsXP-KB891781-x86-ENU.exe
WindowsXP-KB893066-v2-x86-ENU.exe
WindowsXP-KB893086-x86-ENU.exe
WindowsXP-KB893756-x86-ENU.exe
WindowsXP-KB896358-x86-ENU.exe
WindowsXP-KB896422-x86-ENU.exe
WindowsXP-KB896423-x86-ENU.exe
WindowsXP-KB896428-x86-ENU.exe
WindowsXP-KB896727-x86-ENU.exe
WindowsXP-KB898461-x86-ENU.exe
WindowsXP-KB899587-x86-ENU.exe
WindowsXP-KB899588-x86-ENU.exe
WindowsXP-KB899591-x86-ENU.exe
WindowsXP-KB901214-x86-ENU.exe
WindowsXP-KB903235-x86-ENU.exe
wmfdist95.exe

If you want HFSLIP to work, put those files in the HF folder. Please visit FDV's site for details on the wmfdist95.exe file.

Link to comment
Share on other sites

Well I read the batch and noticed the problem, it was performing its first set of search criteria against 'Windows'. Seeing as the only files I had which would have fitted that criteria properly named also had 'KB' in the name, I decided to go the easy route and changed the batch file!

  • I replaced

:HF
REM GET LIST OF THE HOTFIXES
DIR HF\*.EXE /A-D /OGN /B /ON >HF.TXT
FINDSTR /L /I /C:WINDOWS HF.TXT >HFT1.TXT
FINDSTR /V /I "KB891861 KB890830 WindowsUpdateAgent20 LegitCheckControl MDAC MSXML" HFT1.TXT >HF1.TXT
FINDSTR /v /b /i /G:HF1.TXT HF.TXT >HFT2.TXT
FINDSTR /V /I "KB891861 KB890830 WindowsUpdateAgent20 LegitCheckControl MDAC MSXML" HFT2.TXT >HF2.TXT
DEL /F /Q HF.TXT
DEL /F /Q HFT1.TXT
DEL /F /Q HFT2.TXT

  • with

:HF
REM GET LIST OF THE HOTFIXES
DIR HF\*.EXE /A-D/OGN/B/ON | FINDSTR/IB KB | FINDSTR/IV "KB891861 KB890830 WindowsUpdateAgent20 LegitCheckControl MDAC MSXML" >HF1.TXT
DIR HF\*.EXE /A-D/OGN/B/ON | FINDSTR/IVG:HF1.TXT | FINDSTR/IV "KB891861 KB890830 WindowsUpdateAgent20 LegitCheckControl MDAC MSXML" >HF2.TXT

It is now working fine and installing WMP10 etc.

Edited by Yzöwl
Link to comment
Share on other sites

Just a little problem now with Codec Installation Package WM9Codecs.exe, I figured that I'd try these instead of wmfdist95, and duly placed them into my HF folder. I guessed that this would be the correct folder, and after seeing it mentioned here thought I'd go for it.

During the slipstreaming I get

Expanding WM9Codecs.exe
Could Not Find F:\hfslip\TEMP\*INST.EXE
0 File(s) copied
0 File(s) copied
1 file(s) copied.
Processing Windows Update
1 file(s) copied.
Processing Windows Update
Integrating WM9Codecs.exe
0 File(s) copied
Completed WM9Codecs.exe

Anyone else use this file!

Link to comment
Share on other sites

Dumb question, but why are you trying to slipstream wm9 codecs when WMP10 has them already? Also, I gave the fileset needed to have the latest and greatest in the above post, but you continiously want to do something else? I don't mean to be a ball buster, but you are confusing me by asking for help and not listening.

Link to comment
Share on other sites

Yzöwl

Tommyp is right: if WMP10 has wm9 codecs already why don't use it? If you want to install just a few codecs and don't need others maybe you can use Tommyp's codecs slipstreaming guide :D

And please don't understand that the list of hot-fixes Tommyp gave here is mandatory - you don't have to install all hot-fixes if you don't like some.

But when it turns to integrating things like IE, DirectX, WUA, codecs, I suppose Tommyp tweaked his batch for certain files. If you want integrating these things you should use the files he specifies.

By the way Tommyp asked in Codecs thread about integrating codecs in groups. That maybe interesting for you?

PS May I ask you a question about a batch file in PM? I want to try modifying one batch for removing files.

Edited by Oleg_II
Link to comment
Share on other sites

Oleg_II - ask away.

Update - The two files copied were the two infs, so I guess that the error messages were not important.

The file I was adding is for all versions, upto and including WMP10. It is four times smaller than the one you've mentioned and is newer however than XP SP2. My guess is that the main difference between the two is DRM, which isn't needed and isn't fully slipstreamed from your selection (ref: your site).

That aside I am installing more than one OS, with many scenarios of updates /installs, and am only asking questions in order to get a proper feel for the way the program is operating. This is a forum tommyp, the questions are not directed solely at yourself, if you don't want to answer or don't know the answer, then leave it to someone else, it wont upset me.

Link to comment
Share on other sites

Yzöwl

Sorry, I'm careless again :blushing: Have not noticed there was a link for it in your post.

tommyp

Can you have a look at it? It is really much smaller that one we have at the moment.

Edited by Oleg_II
Link to comment
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.
×
×
  • Create New...