Jump to content

Win2000 Hotfix Lists


jsposato

Recommended Posts

My 2000 source CD is at base level (no SPs). When I run XPCREATE, it doesn't detect that there is an SP4. It looks like it only downloaded IE6. I blanked my XPCREATE directory and started again, but same result. I have attached my log files.

Is this a known issue that I missed? I know the hotfix lists were in a state of flux for awhile and I hadn't heard whether or not they were back up.

Also GM-

I'd be happy to help you test the new version.

LOGFILES.CAB

Link to comment
Share on other sites


You can manually download all hotfixes and put them in the right folders

Up-to-date lists for both Windows 2000 Server & Pro (English & French) available here :

http://www.msfn.org/board/index.php?showtopic=22266#

As mentionned by GM, if you use the regular XPCreate (not the 17 SEP 2004 test version), you should replace DX9C download

ADD SVC-DX9\directx_9c_redist.exe http://download.microsoft.com/download/8/1/e/81ed90eb-dd87-4a23-aedc-298a9603b4e4/directx_9c_redist.exe 33F2968C32FFF8C34F7EF110133C24C7

by

DX9NTOPK + KB839643 update Microsoft DirectX 9.0, 9.0a, 9.0b when installed on Windows 2000, Windows XP, or Windows Server 2003 .

ADD SVC-PRE\DX9NTopk.exe http://members.austarmetro.com.au/~mcsw2/MSFN/DX9NTopk.exe ba99b564dbbb764955862395d20208c9
ADD SVC-HF1\DirectX90-KB839643-x86-ENU.EXE http://download.microsoft.com/download/5/8/4/584e3b1c-37ed-4845-8c04-232858b468e9/DirectX90-KB839643-x86-ENU.EXE c3ff4c5570fb73f568dd3b8960e50d64

EDIT : wrong MD5 modified in DirectX90-KB839643-x86-ENU.EXE with the good one c3ff4c5570fb73f568dd3b8960e50d64

Edited by Bilou_Gateux
Link to comment
Share on other sites

Using the win2k hotlists from this thread

http://www.msfn.org/board/index.php?showtopic=22266

I get a file conflict error with one of the ie6 updates.

Basically during the merging hotfixes stage, it prompts me to overwrite a file.

I'll try and dig up the log again, but basically it is because at some point in the process the full name of the file gets "shortened" to something like ie6~1.exe.

I beleive these are the offending files that end being truncated and ultimately conflicting in some way

SVC-POS\IE6.0sp1-KB823353-x86-ENU.exe

SVC-HF2\IE6.0sp1-KB833989-x86-ENU.exe

SVC-HF2\IE6.0sp1-KB867801-x86-ENU.exe

One thought I had to fixing the problem is renaming the beginning characters of the offending file...Would that work?

I'm trying changing the files to this:

SVC-HF2\IE6.1sp1-KB833989-x86-ENU.exe

SVC-HF2\IE6.2sp1-KB867801-x86-ENU.exe

Anyone have any ideas?

NotVeryNice

Link to comment
Share on other sites

basically it is because at some point in the process the full name of the file gets "shortened" to something like ie6~1.exe.
If that is the reason, you can as well rename the files to 8-dot-3 format:
KB833989.exe

KB867801.exe

Although, I suppose the file names in conflict would be the files extracted from these updates. But still, if there's a chance of the above, go ahead and try renaming.

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...