tomasz86

Windows 2000 unofficial updates

   60 members have voted

  1. 1. Do you want SP6?

    • Yes.
    • No.
      0
    • UR2 is enough.
      0

Please sign in or register to vote in this poll.

99 posts in this topic

I think I found a solution to add Server-only updates to UR2.

The problem here is not the Rollup itself but HFSLIP which slipstreams all files even though some of them may be only for Server. I'm thinking about some kind of bypassing, i.e. Sever-only files would be removed after slipstreaming if the OS is Win2k Pro.

0

Share this post


Link to post
Share on other sites

I added a poll to the topic. The more people vote, the better :whistle:

Edited by tomasz86
0

Share this post


Link to post
Share on other sites

For people to be willing to continue to use Win2K it needs to be stable and to run as much of today's software as possible so people can run their favorite apps and do what they need to do with the minimum amount of trouble, and to be stable. Did I mention that it should be stable? LOL This implies that it needs to be up to date, both from a capability and a safety standpoint. That being said, people will always want different things in their OS. To most easily provide that, and not get into a situation where people are asking you to add this or that, or remove this or that, I think it would be ideal if there could be 3 different levels of builds easily accomplished:

Standard - out of the box, just up to date

Minimum - strip it lean and mean for speed using fdv's files etc

Ultimate - add/update anything and everything MS related to the latest version that can run on Win2K and be stable - latest versions of IE, MP, ,NET, VB & VC runtimes, MDAC, Silverlight etc

I hope logic can be added so that server related options are only applied if appropriate, so separate packs are not required.

Whether your tools themselves provide these options directly, or you just give a How-To tutorial of how to do it, or you work with someone else who puts those together using your tools is obviously up to you. This would not only provide flexibility and ease of use for the user, which should help promote its use, but by testing the work you do under those three situations I would think that it would help ferret out potential bugs more rapidly. I've always liked HFSLIP and it's ability to integrate updates to speed up the installation process and make the build smaller, but if, as you've lately implied, you are reaching the limits of what it can do, since it's no longer being updated, I guess the choices would be to update it, since the source is available, or move over to either nLite (also not being updated any more) or RyanVM's Integrator which IS still being worked on, at least sporadically.

No matter what you decide, a very big THANK YOU! for all the work you've done regarding Win2K lately. It really is appreciated, even if those feelings are not expressed as often as they should.

Cheers and Regards

Edited by bphlpt
0

Share this post


Link to post
Share on other sites

bphlpt,

Thank you for the input. The three options you mention seem interesting. I am however a little dubious about the Minimum option. Including FDV would make using nLite impossible which I want to avoid. Standard and Ultimate seem interesting. By

out of the box, just up to date

do you mean that unofficial updates should also be included in the standard installation? I'm asking regarding the "up to date" thing as without UUs (unofficial updates) W2K stopped in July 2010. I do agree that including all the other components (WMP, .NET, etc.) should be avoided in the basic installation as not everyone needs them (especially if it's an older computer). I disagree in case of IE - if safety is a priority then IE6 is a much better choice than IE5.

HFSLIP is nice but as I already said before it has too many limitations. I managed to work out how the /integrate switch works and I believe it will be the best way to slipstream everything to the W2K source without using any other tools. /integrate when used in the update mode doesn't slipstream any files - it just sets the update to be installed at T-13. However, there is also the other mode for it - called SP mode. When run in SP mode /integrate slipstreams files directly into the source. It has many advantages:

- no need for 3rd party tools (HFSLIP, nLite, etc.)

- Professional and Server files are added accordingly to the edition of W2K which is used

- full control of the process of slipstreaming

- simplicity (easy to use for other people)

This is what I am aiming at - use /integrate to slipstream everything directly. No HFSLIP, no nLite, no other programs. The only problem is that preparing a Service Pack is much more time consuming and difficult than an update rollup. I haven't decided yet - that's why I opened this poll :)

0

Share this post


Link to post
Share on other sites

This is what I am aiming at - use /integrate to slipstream everything directly. No HFSLIP, no nLite, no other programs. The only problem is that preparing a Service Pack is much more time consuming and difficult than an update rollup. I haven't decided yet - that's why I opened this poll :)

Probably the best solution. HFSLIP with not be updated any more, I'm sure the bugs it has won't be fixed so why waste anytime on it. It was a great project but its time to move on.

Edited by PROBLEMCHYLD
0

Share this post


Link to post
Share on other sites

By "out of the box, just up to date" my thought was that unofficial updates SHOULD be included, since they are the kind of updates that WOULD probably have been included if support had not stopped. Just don't add extra components that would not have been included in a basic, standard, run of the mill type install. Kind of like the difference between a home and a professional type of install. I know that there are many people who are not like me. They don't want to be at the cutting edge, they're just going to surf the web, do email, maybe office type stuff, and mild games like Solitare. The systems that you would set up for your mom, grandmother, aunt Sue, etc. They would want the standard setup.

I'm afraid I'm not the guy who can tell you what that is like since I've always been the guy who wants it all with all the options and nothing removed - ie the ultimate approach. I want to always be prepared so that I'm more likely to be able to run, play, install anything I run across that my hardware will support. The addon from Onepiece - http://www.ryanvm.net/forum/viewtopic.php?t=5326 could be an example of the Ultimate type of content. Why he didn't include support to enable the LBA 48bit fix, I'm not sure. Could be a technical reason why he left it separate? With the sizes of todays disc drives I would have thought that feature would would be even more important now. If I remember right Gurgelmeyer included it in his pack? Kurt_Aust's guide could also be considered as an example of a build that includes it all, and then some.

The third group is those that would have used fdv's fileset. You're right - I had forgotten that Fred said that you shouldn't try to use nlite with his fileset. Good catch. Using two tools at the same time that do the same job, just in different ways, can cause problems. Like running two different real-time anti-virus programs at the same time. But that is a group that might still have an interest in what you do. The fdv threads still get the occasional post. So if you can meet their needs, whether you use the fdv fileset or not, that would get you another potential audience. They want things stripped dowm for speed and simplicity - all the garbage they're not going to use taken out - mostly IE. Again though, that's not me - maybe someone else can advise you on their needs.

I love the idea of the SP approach. That should speed things up and keep things cleaner. Both will be appreciated. Keep up the great work.

Cheers and Regards

0

Share this post


Link to post
Share on other sites

By "out of the box, just up to date" my thought was that unofficial updates SHOULD be included, since they are the kind of updates that WOULD probably have been included if support had not stopped. Just don't add extra components that would not have been included in a basic, standard, run of the mill type install.

I agree with you as for UUs but I know that there are people too who want to stick to the official updates only. I personally believe that at this moment (2011) it's been already a year since 2K went EOL and UUs are just a must if you keep using 2K today.

I'm afraid I'm not the guy who can tell you what that is like since I've always been the guy who wants it all with all the options and nothing removed - ie the ultimate approach. I want to always be prepared so that I'm more likely to be able to run, play, install anything I run across that my hardware will support.

Your approach is similar to mine ;) the solution may be to make two editions of USP6 -> basic & ultimate. Basic would be just an updated 2K with updated default components such as IE or MDAC. I wouldn't include WMP9 or DX9 in it as they are not really necessary in office environment. The ultimate one could include everything starting from DX9, WMP9, MSXMLs, .NET Framework, MS VC++ and several other small tools like msconfig, Profile Hive Cleanup, etc.

By the way, what do you think about Roots Updates? Should they be included in both versions of USP6? I'm asking because they are frequently updated and including them would require releasing an updated version of both USP's quite often.

The other way could be to make three editions - standard, enhanced and ultimate. The standard one would include ONLY official updates - like UR2 at this moment. Once finished, it would not be updated anymore. The enhanced one would have IE6, MDAC, DX, WMP9, etc. updated and unofficial updates would be included. The ultimate one would be Enhanced + other non-default components like .NET Framework, MSVC++, etc. The big disadvantage of such an approach is that a lot of work is required and it may be too much for a one person.

Sticking to just two editions of USP6 is probably the best solution.

The addon from Onepiece - http://www.ryanvm.net/forum/viewtopic.php?t=5326 could be an example of the Ultimate type of content. Why he didn't include support to enable the LBA 48bit fix, I'm not sure. Could be a technical reason why he left it separate? With the sizes of todays disc drives I would have thought that feature would would be even more important now. If I remember right Gurgelmeyer included it in his pack? Kurt_Aust's guide could also be considered as an example of a build that includes it all, and then some.

The Onepiece addon is nice but it has one problem - HBRs are included which I don't want in USP6 as they may have negative impact on system stability. I probably know why the LBA fix is not inclujded in this addon and is included in Gurgelmeyer's USP5. The LBA fix is edition dependent - to enable 48-bit LBA support in text setup you must edit the setupreg.hiv file. This file is different in case of each 2K edition - Pro, Srv, AdvSrv, DataCtr, Embedded. 2K's SP4 has 5 versions of it for each edition respectively and Gurgelmeyer added the fix to each of them. It's impossible to do in an addon where you don't have such a controlling mechanism to distinguish between different editions of 2K.

Kurt Aust's guide is very good and I'm going to analyse it thoroughly when adding additional components to the USP6 in the future.

The third group is those that would have used fdv's fileset.

There is no reason why HFSLIP shouldn't be used after integrating (/integrate) the USP. The same thing was with Gurgelmeyer's USP5 - you could use HFSLIP/nLite with no problems after having it slipstreamed. People using FDV's fileset could just use it in the same way as they do now :)

0

Share this post


Link to post
Share on other sites

I haven't written anything in this topic for a while... but it doesn't mean that I've lost my interest in the topic ;)

I've been a little busy recently so I've been trying to focus more on the field of unofficial updates which require much less work than preparing a Service Pack. I also want to make a slipstreamable installation for .NET Framework (1.1-3.5) which could be put in HF folder. I also want to have a look at .NET 4.0 but I don't know yet if it's possible to make it work in 2K.

Before doing anything concerning SP6 I'd like to make a one more version (and it'd be the last one) of UR2 which would be slipstreamable using the /integrate switch. I'll probably have to remove IE6 updates from it to keep compatiblity with both IE5 and 6 as at this moment there are problems with catalog files (the ones from IE5 and IE6 overlap each other causes problems when using sfc /scannow). By using /integrate I could also avoid doing any manual date modifications to the system dll and still have only newer versions slipstreamed :)

I'm also looking forward to testing WildBill's new kernel patch which may fix a lot of compatiblity issues related with newer updates and applications.

Edited by tomasz86
0

Share this post


Link to post
Share on other sites

I'm considering stopping realisng single updates. I'd rather focus on a update rollup which would have all unofficial updates included. There are several benefits it:

1) Easy to manage and update.

2) Easy to test compatibility with different configurations of W2K (IE5, IE6, WB&BWC kernel, etc.).

3) Easy to install and slipstream (1 single package instead of tens/hundreds of single updates).

4) It's possible to add single files not belonging to any particular updates or files from XP SP3, etc.

5) Managing all these single updates is too time consuming.

Could anyone share his/her opinion on this idea?

Of course it'd be a temporary solution until I manage to finish the USP6 project (still LONG time to go...).

0

Share this post


Link to post
Share on other sites

I'm considering stopping realisng single updates. I'd rather focus on a update rollup which would have all unofficial updates included. There are several benefits it:

1) Easy to manage and update.

2) Easy to test compatibility with different configurations of W2K (IE5, IE6, WB&BWC kernel, etc.).

3) Easy to install and slipstream (1 single package instead of tens/hundreds of single updates).

4) It's possible to add single files not belonging to any particular updates or files from XP SP3, etc.

5) Managing all these single updates is too time consuming.

Could anyone share his/her opinion on this idea?

Of course it'd be a temporary solution until I manage to finish the USP6 project (still LONG time to go...).

Its probably the best solution. Its a headache to have to download a hundred small packages

than to just have on big package. Thats what I have done with Win98 SP3. Its at 52mb, which is not bad compared to

some other packs.

0

Share this post


Link to post
Share on other sites

It's time to revive this topic :)

I've prepared the Unofficial Updates Rollup (see #1 post). It's available for ENU & Global (non-ENU) systems. The difference between the two is that there are more (English-only) updates included in the ENU version. I managed to merged the two kernels - WB kernel & BWC kernel meaning that I chose compatible files from both of them and added them to the Rollup (ENU). Now it's no longer necessary to choose between the two. You can use the Rollup as long as you've got SP4 & UR1 installed. Because both unofficial kernels are included you don't need to install any other unofficial updates or other packages before installing the UU Rollup. Of course you can also slipstream it as it's 100% compatible with HFSLIP.

The next two big packages I'm focused on are a new version of the HBR Rollup & a new version of UR2. After that I can focus on USP6.

Please tell me if there are any problems with the UU Rollup.

Edited by tomasz86
0

Share this post


Link to post
Share on other sites

Thanks, windows 2K server is still good for my old hardware, and can do a lot of things XP and windows 7 cant. Thanks for keeping it alive.

Edited by Lucius
0

Share this post


Link to post
Share on other sites

It's always good to know that there's someone interested in these packages :w00t:

I've started working on a new version of Update Rollup 2. This is just a very first alpha. I'm sure there are some bugs in it. UR1 is not yet included.

Windows2000-UR2-ALPHA1-x86-ENU.exe (27 MB)

Details:

  • Integrated updates:
    Windows2000-KB838989-x86-ENU.EXE
    Windows2000-KB839228-x86-ENU.EXE
    Windows2000-KB893756-x86-ENU.EXE
    Windows2000-KB894395-x86-Global.exe
    Windows2000-KB896358-x86-ENU.EXE
    Windows2000-KB896423-x86-ENU.EXE
    Windows2000-KB899587-x86-ENU.EXE
    Windows2000-KB899589-x86-ENU.EXE
    Windows2000-KB900725-x86-ENU.EXE
    Windows2000-KB901017-x86-ENU.EXE
    Windows2000-KB901214-x86-ENU.EXE
    Windows2000-KB905414-x86-ENU.EXE
    Windows2000-KB905749-x86-ENU.EXE
    Windows2000-KB913580-x86-ENU.EXE
    Windows2000-KB914388-x86-ENU.EXE
    Windows2000-KB917537-x86-ENU.EXE
    Windows2000-KB918118-x86-ENU.EXE
    Windows2000-KB920213-x86-ENU.EXE
    Windows2000-KB920670-x86-ENU.EXE
    Windows2000-KB920683-x86-ENU.EXE
    Windows2000-KB922582-x86-ENU.EXE
    Windows2000-KB923191-x86-ENU.EXE
    Windows2000-KB923561-x86-ENU.EXE
    Windows2000-KB923810-x86-ENU.EXE
    Windows2000-KB923980-x86-ENU.EXE
    Windows2000-KB924270-x86-ENU.EXE
    Windows2000-KB924432-x86-ENU.EXE
    Windows2000-KB924667-x86-ENU.EXE
    Windows2000-KB925902-x86-ENU.EXE
    Windows2000-KB926247-x86-ENU.EXE
    Windows2000-KB926436-x86-ENU.EXE
    Windows2000-KB927891-x86-ENU.EXE
    Windows2000-KB928843-x86-ENU.EXE
    Windows2000-KB935839-x86-ENU.EXE
    Windows2000-KB938827-x86-ENU.EXE
    Windows2000-KB942831-x86-ENU.EXE
    Windows2000-KB943055-x86-ENU.EXE
    Windows2000-KB943485-x86-ENU.EXE
    Windows2000-KB950749-x86-ENU.EXE
    Windows2000-KB950974-x86-ENU.EXE
    Windows2000-KB951748-V2-x86-ENU.EXE
    Windows2000-KB952004-x86-ENU.EXE
    Windows2000-KB952954-x86-ENU.EXE
    Windows2000-KB953155-x86-ENU.EXE
    Windows2000-KB955069-x86-ENU.EXE
    Windows2000-KB955417-x86-ENU.EXE
    Windows2000-KB955759-x86-ENU.EXE
    Windows2000-KB956802-x86-ENU.EXE
    Windows2000-KB956844-x86-ENU.EXE
    Windows2000-KB958644-x86-ENU.EXE
    Windows2000-KB959426-x86-ENU.EXE
    Windows2000-KB960225-x86-ENU.EXE
    Windows2000-KB960803-x86-ENU.EXE
    Windows2000-KB960859-x86-ENU.EXE
    Windows2000-KB961501-x86-ENU.EXE
    Windows2000-KB967715-x86-ENU.EXE
    Windows2000-KB969059-x86-ENU.EXE
    Windows2000-KB970238-x86-ENU.EXE
    Windows2000-KB970483-x86-ENU.EXE
    Windows2000-KB971032-x86-ENU.EXE
    Windows2000-KB971468-x86-ENU.EXE
    Windows2000-KB972270-x86-ENU.EXE
    Windows2000-KB973037-x86-ENU.EXE
    Windows2000-KB973507-x86-ENU.EXE
    Windows2000-KB973869-x86-ENU.EXE
    Windows2000-KB974318-x86-ENU.EXE
    Windows2000-KB974392-x86-ENU.EXE
    Windows2000-KB974571-x86-ENU.EXE
    Windows2000-KB974783-x86-ENU.EXE
    Windows2000-KB975254-x86-ENU.EXE
    Windows2000-KB975713-x86-ENU.EXE
    Windows2000-KB977290-x86-ENU.EXE
    Windows2000-KB977914-x86-ENU.EXE
    Windows2000-KB978037-x86-ENU.EXE
    Windows2000-KB978601-x86-ENU.EXE
    Windows2000-KB978706-x86-ENU.EXE
    Windows2000-KB979309-x86-ENU.EXE
    Windows2000-KB979482-x86-ENU.EXE
    Windows2000-KB979559-x86-ENU.EXE
    Windows2000-KB979683-x86-ENU.EXE
    Windows2000-KB980218-x86-ENU.EXE
    Windows2000-KB980232-x86-ENU.EXE
    WindowsXP-KB2647518-x86-ENU.exe
    KB832414_MSXML2.5_x86.exe
    ocsasnfix.exe
    sct10en.exe
    Webfldrs-KB892211-ENU.exe
    Replaced updates:
    Windows2000-KB980195-x86-ENU.EXE
    Included Files:
    aclayers.dll 5.0.2195.7358
    afd.sys 5.0.2195.7204
    agentdp2.dll 2.0.0.3424
    agentdpv.dll 2.0.0.3426
    agentsvr.exe 2.0.0.3424
    apcompat.inf
    asp.dll 5.0.2195.7084
    asycfilt.dll 2.40.4534.0
    atl.dll 3.0.9794.0
    atmfd.dll 5.0.2.227
    avifil32.dll 5.0.2195.7359
    cabview.dll 5.0.3900.7369
    catsrv.dll 2000.2.3529.0
    catsrvut.dll 2000.2.3529.0
    cdosys.dll 6.1.3940.42
    clbcatex.dll 2000.2.3529.0
    clbcatq.dll 2000.2.3529.0
    colbact.dll 2000.2.3529.0
    comadmin.dll 2000.2.3529.0
    comctl32.dll 5.81.3900.7109
    comrepl.dll 2000.2.3529.0
    comsetup.dll 2000.2.3421.3529
    comsvcs.dll 2000.2.3529.0
    comuid.dll 2000.2.3529.0
    crypt32.dll 5.131.2195.6926
    cryptnet.dll 5.131.2195.6926
    cryptsvc.dll 5.0.2195.7039
    csrsrv.dll 5.0.2195.7366
    dao360.dll 3.60.9512.0
    dhcpcsvc.dll 5.0.2195.7085
    dhtmled.ocx 6.1.0.9234
    dnsapi.dll 5.0.2195.7280
    dnsrslvr.dll 5.0.2195.7280
    dtcsetup.cat
    dtcsetup.exe 2000.2.3549.0
    es.dll 2000.2.3550.0
    faxui.dll 0.2.0.2
    fltmgr.sys 5.0.2195.7108
    fontsub.dll 5.0.2195.7348
    ftpsvc2.dll 5.0.2195.7336
    gdi32.dll 5.0.2195.7205
    hh.exe 5.2.3790.309
    hhctrl.ocx 5.2.3790.620
    hhsetup.dll 5.2.3790.309
    hidclass.sys 5.0.2195.6882
    hlink.dll 5.2.3790.2748
    httpext.dll 5.0.2195.7290
    icm32.dll 5.0.0.3
    imejp.ime 7.0.1.9006
    infocomm.dll 5.0.2195.7147
    iphlpapi.dll 5.0.2195.7097
    ipsec.sys 5.0.2195.6883
    ipsecmon.exe 5.0.2195.6882
    itircl.dll 5.2.3790.309
    itss.dll 5.2.3790.309
    jpeg2x32.dll 5.0.2195.7134
    kdcsvc.dll 5.0.2195.7361
    kerberos.dll 5.0.2195.7053
    kernel32.dll 5.0.2195.7135
    kodakimg.exe 5.0.2195.7136
    kodakprv.exe 5.0.2195.7136
    linkinfo.dll 5.0.2195.7069
    llscustom.dll 5.0.2195.7337
    llssrv.exe 5.0.2195.7337
    localspl.dll 5.0.2195.7296
    lsasrv.dll 5.0.2195.7147
    mciavi32.dll 5.0.2195.7359
    mf3216.dll 5.0.2195.7133
    mfc40u.dll 4.1.0.6141
    mfc42u.dll 6.0.9792.0
    mpr.dll 5.0.2195.7134
    mq1repl.dll 5.0.0.808
    mq1sync.exe 5.0.0.808
    mqac.sys 5.0.0.808
    mqads.dll 5.0.0.808
    mqbkup.exe 5.0.0.808
    mqcertui.dll 5.0.0.808
    mqclus.dll 5.0.0.808
    mqdbodbc.dll 5.0.0.805
    mqdscli.dll 5.0.0.808
    mqdssrv.dll 5.0.0.808
    mqlogmgr.dll 2000.2.3516.0
    mqmig.exe 5.0.0.808
    mqmigrat.dll 5.0.0.808
    mqoa.dll 5.0.0.808
    mqperf.dll 5.0.0.808
    mqqm.dll 5.0.0.808
    mqrperf.dll 5.0.0.805
    mqrt.dll 5.0.0.808
    mqsec.dll 5.0.0.808
    mqsnap.dll 5.0.0.808
    mqsvc.exe 5.0.0.808
    mqupgrd.dll 5.0.0.808
    mqutil.dll 5.0.0.808
    mrxsmb.sys 5.0.2195.7379
    msafd.dll 5.0.2195.7158
    msasn1.dll 5.0.2195.7334
    mscms.dll 5.0.2195.7162
    msdtclog.dll 2000.2.3549.0
    msdtcprx.dll 2000.2.3549.0
    msdtctm.dll 2000.2.3549.0
    msdtcui.dll 2000.2.3549.0
    msexch40.dll 4.0.9502.0
    msexcl40.dll 4.0.9502.0
    msi.dll 3.1.4000.4033
    msjet40.dll 4.0.9511.0
    msjetol1.dll 4.0.9502.0
    msjint40.dll 4.0.9502.0
    msjter40.dll 4.0.9502.0
    msjtes40.dll 4.0.9502.0
    msltus40.dll 4.0.9502.0
    msmq.cpl 5.0.0.801
    msmqocm.dll 5.0.0.805
    mspaint.exe 5.0.2195.7368
    mspbde40.dll 4.0.9502.0
    msrd2x40.dll 4.0.9502.0
    msrd3x40.dll 4.0.9502.0
    msrepl40.dll 4.0.9502.0
    msrle32.dll 5.0.2195.7359
    mstext40.dll 4.0.9502.0
    msv1_0.dll 5.0.2195.6926
    msvidc32.dll 5.0.2195.7359
    msw3prt.dll 5.0.2195.7165
    mswdat10.dll 4.0.9502.0
    mswrd6.wpc 10.0.803.10
    mswrd8.wpc 10.0.803.10
    mswsock.dll 5.0.2195.7158
    mswstr10.dll 4.0.9502.0
    msxbde40.dll 4.0.9502.0
    msxml3.dll 8.100.1048.0
    mtstocom.exe 2000.2.3529.0
    mtxclu.dll 2000.2.3549.0
    mtxdm.dll 2000.2.3529.0
    mtxlegih.dll 2000.2.3529.0
    mtxoci.dll 2000.2.3549.0
    mup.sys 5.0.2195.7006
    netapi32.dll 5.0.2195.7203
    netdiag.exe 5.0.2195.6824
    netlogon.dll 5.0.2195.7011
    netman.dll 5.0.2195.7061
    ntdsa.dll 5.0.2195.7313
    ntkrnlmp.exe 5.0.2195.7376
    ntkrnlpa.exe 5.0.2195.7376
    ntkrpamp.exe 5.0.2195.7376
    ntoskrnl.exe 5.0.2195.7376
    nwapi32.dll 5.0.2195.7109
    nwprovau.dll 5.0.2195.7110
    nwrdr.sys 5.0.2195.7110
    nwwks.dll 5.0.2195.7065
    oakley.dll 5.0.2195.7343
    oieng400.dll 5.0.2195.7144
    ole32.dll 5.0.2195.7103
    oleaut32.dll 2.40.4532.0
    olecli32.dll 5.0.2195.7009
    olecnv32.dll 5.0.2195.7059
    oledlg.dll 5.0.2195.7114
    openhci.sys 5.0.2195.6882
    polagent.dll 5.0.2195.6882
    polstore.dll 5.0.2195.6882
    printers.htt
    psbase.dll 5.0.2195.7164
    query.dll 5.0.2195.7320
    rasadhlp.dll 5.0.2195.7098
    raschap.dll 5.0.2195.7344
    rasmans.dll 5.0.2195.7099
    rastls.dll 5.0.2195.7344
    rdbss.sys 5.0.2195.7376
    remotesp.tsp 5.0.2195.7002
    riched20.dll 5.30.23.1227
    rpcrt4.dll 5.0.2195.7281
    rpcss.dll 5.0.2195.7116
    schannel.dll 5.1.2195.7213
    secur32.dll 5.0.2195.7244
    shell32.dll 5.0.3900.7155
    shlwapi.dll 5.0.3900.7349
    snmp.exe 5.0.2195.7112
    sp3res.dll 5.0.2195.7295
    spoolss.dll 5.0.2195.7054
    spoolsv.exe 5.0.2195.7059
    srv.sys 5.0.2195.7365
    stclient.dll 2000.2.3529.0
    sysmain.sdb
    t2embed.dll 5.0.2195.7348
    tapisrv.dll 5.0.2195.7057
    tcpip.sys 5.0.2195.7162
    telnet.exe 5.0.33670.4
    tifflt.dll 5.0.3900.7134
    triedit.dll 6.1.0.9235
    tsbyuv.dll 5.0.2195.7359
    txfaux.dll 2000.2.3529.0
    uhcd.sys 5.0.2195.6882
    umpnpmgr.dll 5.0.2195.7069
    usb.inf
    usbd.sys 5.0.2195.6935
    usbehci.sys 5.0.2195.6882
    usbhub20.sys 5.0.2195.6891
    usbport.sys 5.0.2195.6926
    user32.dll 5.0.2195.7133
    userenv.dll 5.0.2195.7134
    webvw.dll 5.0.3900.7069
    win32k.sys 5.0.2195.7397
    win32spl.dll 5.0.2195.7266
    winhttp.dll 5.1.2600.3490
    winsrv.dll 5.0.2195.7135
    wintrust.dll 5.131.2195.7375
    wkssvc.dll 5.0.2195.7108
    wordpad.exe 5.0.2195.7155
    write.wpc 10.0.803.10
    xolehlp.dll 2000.2.3549.0

0

Share this post


Link to post
Share on other sites

I have uploaded UU Rollup v2. I've removed the custom update 2347290 because, after all, it's not a UU ;) I'll include it in the upcoming Unofficial Update Rollup 2.

0

Share this post


Link to post
Share on other sites

Do you know if the LNK exploit is mitigated by any of these patches. I recall 2k support was dropped weeks before MS patched this on all current versions except for 2k.

edit nvm i found out it is covered Windows2000-UU-KBz2479628-v10-x86-ENU.exe

Edited by Lucius
0

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.