tomasz86 Posted July 23, 2011 Author Posted July 23, 2011 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.
tomasz86 Posted July 30, 2011 Author Posted July 30, 2011 (edited) I added a poll to the topic. The more people vote, the better Edited July 30, 2011 by tomasz86
bphlpt Posted July 30, 2011 Posted July 30, 2011 (edited) 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 dateMinimum - strip it lean and mean for speed using fdv's files etcUltimate - 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 etcI 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 July 30, 2011 by bphlpt
tomasz86 Posted July 30, 2011 Author Posted July 30, 2011 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. Byout of the box, just up to datedo 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
PROBLEMCHYLD Posted July 30, 2011 Posted July 30, 2011 (edited) 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 July 30, 2011 by PROBLEMCHYLD
bphlpt Posted July 31, 2011 Posted July 31, 2011 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
tomasz86 Posted July 31, 2011 Author Posted July 31, 2011 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
tomasz86 Posted September 27, 2011 Author Posted September 27, 2011 (edited) 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 September 27, 2011 by tomasz86
tomasz86 Posted February 25, 2012 Author Posted February 25, 2012 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...).
PROBLEMCHYLD Posted February 25, 2012 Posted February 25, 2012 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 packagesthan to just have on big package. Thats what I have done with Win98 SP3. Its at 52mb, which is not bad compared tosome other packs.
tomasz86 Posted March 16, 2012 Author Posted March 16, 2012 (edited) 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 March 16, 2012 by tomasz86
Lucius Posted March 16, 2012 Posted March 16, 2012 (edited) 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 March 16, 2012 by Lucius
tomasz86 Posted March 16, 2012 Author Posted March 16, 2012 It's always good to know that there's someone interested in these packages 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.EXEWindows2000-KB839228-x86-ENU.EXEWindows2000-KB893756-x86-ENU.EXEWindows2000-KB894395-x86-Global.exeWindows2000-KB896358-x86-ENU.EXEWindows2000-KB896423-x86-ENU.EXEWindows2000-KB899587-x86-ENU.EXEWindows2000-KB899589-x86-ENU.EXEWindows2000-KB900725-x86-ENU.EXEWindows2000-KB901017-x86-ENU.EXEWindows2000-KB901214-x86-ENU.EXEWindows2000-KB905414-x86-ENU.EXEWindows2000-KB905749-x86-ENU.EXEWindows2000-KB913580-x86-ENU.EXEWindows2000-KB914388-x86-ENU.EXEWindows2000-KB917537-x86-ENU.EXEWindows2000-KB918118-x86-ENU.EXEWindows2000-KB920213-x86-ENU.EXEWindows2000-KB920670-x86-ENU.EXEWindows2000-KB920683-x86-ENU.EXEWindows2000-KB922582-x86-ENU.EXEWindows2000-KB923191-x86-ENU.EXEWindows2000-KB923561-x86-ENU.EXEWindows2000-KB923810-x86-ENU.EXEWindows2000-KB923980-x86-ENU.EXEWindows2000-KB924270-x86-ENU.EXEWindows2000-KB924432-x86-ENU.EXEWindows2000-KB924667-x86-ENU.EXEWindows2000-KB925902-x86-ENU.EXEWindows2000-KB926247-x86-ENU.EXEWindows2000-KB926436-x86-ENU.EXEWindows2000-KB927891-x86-ENU.EXEWindows2000-KB928843-x86-ENU.EXEWindows2000-KB935839-x86-ENU.EXEWindows2000-KB938827-x86-ENU.EXEWindows2000-KB942831-x86-ENU.EXEWindows2000-KB943055-x86-ENU.EXEWindows2000-KB943485-x86-ENU.EXEWindows2000-KB950749-x86-ENU.EXEWindows2000-KB950974-x86-ENU.EXEWindows2000-KB951748-V2-x86-ENU.EXEWindows2000-KB952004-x86-ENU.EXEWindows2000-KB952954-x86-ENU.EXEWindows2000-KB953155-x86-ENU.EXEWindows2000-KB955069-x86-ENU.EXEWindows2000-KB955417-x86-ENU.EXEWindows2000-KB955759-x86-ENU.EXEWindows2000-KB956802-x86-ENU.EXEWindows2000-KB956844-x86-ENU.EXEWindows2000-KB958644-x86-ENU.EXEWindows2000-KB959426-x86-ENU.EXEWindows2000-KB960225-x86-ENU.EXEWindows2000-KB960803-x86-ENU.EXEWindows2000-KB960859-x86-ENU.EXEWindows2000-KB961501-x86-ENU.EXEWindows2000-KB967715-x86-ENU.EXEWindows2000-KB969059-x86-ENU.EXEWindows2000-KB970238-x86-ENU.EXEWindows2000-KB970483-x86-ENU.EXEWindows2000-KB971032-x86-ENU.EXEWindows2000-KB971468-x86-ENU.EXEWindows2000-KB972270-x86-ENU.EXEWindows2000-KB973037-x86-ENU.EXEWindows2000-KB973507-x86-ENU.EXEWindows2000-KB973869-x86-ENU.EXEWindows2000-KB974318-x86-ENU.EXEWindows2000-KB974392-x86-ENU.EXEWindows2000-KB974571-x86-ENU.EXEWindows2000-KB974783-x86-ENU.EXEWindows2000-KB975254-x86-ENU.EXEWindows2000-KB975713-x86-ENU.EXEWindows2000-KB977290-x86-ENU.EXEWindows2000-KB977914-x86-ENU.EXEWindows2000-KB978037-x86-ENU.EXEWindows2000-KB978601-x86-ENU.EXEWindows2000-KB978706-x86-ENU.EXEWindows2000-KB979309-x86-ENU.EXEWindows2000-KB979482-x86-ENU.EXEWindows2000-KB979559-x86-ENU.EXEWindows2000-KB979683-x86-ENU.EXEWindows2000-KB980218-x86-ENU.EXEWindows2000-KB980232-x86-ENU.EXEWindowsXP-KB2647518-x86-ENU.exeKB832414_MSXML2.5_x86.exeocsasnfix.exesct10en.exeWebfldrs-KB892211-ENU.exeReplaced updates:Windows2000-KB980195-x86-ENU.EXEIncluded Files:aclayers.dll 5.0.2195.7358afd.sys 5.0.2195.7204agentdp2.dll 2.0.0.3424agentdpv.dll 2.0.0.3426agentsvr.exe 2.0.0.3424apcompat.infasp.dll 5.0.2195.7084asycfilt.dll 2.40.4534.0atl.dll 3.0.9794.0atmfd.dll 5.0.2.227avifil32.dll 5.0.2195.7359cabview.dll 5.0.3900.7369catsrv.dll 2000.2.3529.0catsrvut.dll 2000.2.3529.0cdosys.dll 6.1.3940.42clbcatex.dll 2000.2.3529.0clbcatq.dll 2000.2.3529.0colbact.dll 2000.2.3529.0comadmin.dll 2000.2.3529.0comctl32.dll 5.81.3900.7109comrepl.dll 2000.2.3529.0comsetup.dll 2000.2.3421.3529comsvcs.dll 2000.2.3529.0comuid.dll 2000.2.3529.0crypt32.dll 5.131.2195.6926cryptnet.dll 5.131.2195.6926cryptsvc.dll 5.0.2195.7039csrsrv.dll 5.0.2195.7366dao360.dll 3.60.9512.0dhcpcsvc.dll 5.0.2195.7085dhtmled.ocx 6.1.0.9234dnsapi.dll 5.0.2195.7280dnsrslvr.dll 5.0.2195.7280dtcsetup.catdtcsetup.exe 2000.2.3549.0es.dll 2000.2.3550.0faxui.dll 0.2.0.2fltmgr.sys 5.0.2195.7108fontsub.dll 5.0.2195.7348ftpsvc2.dll 5.0.2195.7336gdi32.dll 5.0.2195.7205hh.exe 5.2.3790.309hhctrl.ocx 5.2.3790.620hhsetup.dll 5.2.3790.309hidclass.sys 5.0.2195.6882hlink.dll 5.2.3790.2748httpext.dll 5.0.2195.7290icm32.dll 5.0.0.3imejp.ime 7.0.1.9006infocomm.dll 5.0.2195.7147iphlpapi.dll 5.0.2195.7097ipsec.sys 5.0.2195.6883ipsecmon.exe 5.0.2195.6882itircl.dll 5.2.3790.309itss.dll 5.2.3790.309jpeg2x32.dll 5.0.2195.7134kdcsvc.dll 5.0.2195.7361kerberos.dll 5.0.2195.7053kernel32.dll 5.0.2195.7135kodakimg.exe 5.0.2195.7136kodakprv.exe 5.0.2195.7136linkinfo.dll 5.0.2195.7069llscustom.dll 5.0.2195.7337llssrv.exe 5.0.2195.7337localspl.dll 5.0.2195.7296lsasrv.dll 5.0.2195.7147mciavi32.dll 5.0.2195.7359mf3216.dll 5.0.2195.7133mfc40u.dll 4.1.0.6141mfc42u.dll 6.0.9792.0mpr.dll 5.0.2195.7134mq1repl.dll 5.0.0.808mq1sync.exe 5.0.0.808mqac.sys 5.0.0.808mqads.dll 5.0.0.808mqbkup.exe 5.0.0.808mqcertui.dll 5.0.0.808mqclus.dll 5.0.0.808mqdbodbc.dll 5.0.0.805mqdscli.dll 5.0.0.808mqdssrv.dll 5.0.0.808mqlogmgr.dll 2000.2.3516.0mqmig.exe 5.0.0.808mqmigrat.dll 5.0.0.808mqoa.dll 5.0.0.808mqperf.dll 5.0.0.808mqqm.dll 5.0.0.808mqrperf.dll 5.0.0.805mqrt.dll 5.0.0.808mqsec.dll 5.0.0.808mqsnap.dll 5.0.0.808mqsvc.exe 5.0.0.808mqupgrd.dll 5.0.0.808mqutil.dll 5.0.0.808mrxsmb.sys 5.0.2195.7379msafd.dll 5.0.2195.7158msasn1.dll 5.0.2195.7334mscms.dll 5.0.2195.7162msdtclog.dll 2000.2.3549.0msdtcprx.dll 2000.2.3549.0msdtctm.dll 2000.2.3549.0msdtcui.dll 2000.2.3549.0msexch40.dll 4.0.9502.0msexcl40.dll 4.0.9502.0msi.dll 3.1.4000.4033msjet40.dll 4.0.9511.0msjetol1.dll 4.0.9502.0msjint40.dll 4.0.9502.0msjter40.dll 4.0.9502.0msjtes40.dll 4.0.9502.0msltus40.dll 4.0.9502.0msmq.cpl 5.0.0.801msmqocm.dll 5.0.0.805mspaint.exe 5.0.2195.7368mspbde40.dll 4.0.9502.0msrd2x40.dll 4.0.9502.0msrd3x40.dll 4.0.9502.0msrepl40.dll 4.0.9502.0msrle32.dll 5.0.2195.7359mstext40.dll 4.0.9502.0msv1_0.dll 5.0.2195.6926msvidc32.dll 5.0.2195.7359msw3prt.dll 5.0.2195.7165mswdat10.dll 4.0.9502.0mswrd6.wpc 10.0.803.10mswrd8.wpc 10.0.803.10mswsock.dll 5.0.2195.7158mswstr10.dll 4.0.9502.0msxbde40.dll 4.0.9502.0msxml3.dll 8.100.1048.0mtstocom.exe 2000.2.3529.0mtxclu.dll 2000.2.3549.0mtxdm.dll 2000.2.3529.0mtxlegih.dll 2000.2.3529.0mtxoci.dll 2000.2.3549.0mup.sys 5.0.2195.7006netapi32.dll 5.0.2195.7203netdiag.exe 5.0.2195.6824netlogon.dll 5.0.2195.7011netman.dll 5.0.2195.7061ntdsa.dll 5.0.2195.7313ntkrnlmp.exe 5.0.2195.7376ntkrnlpa.exe 5.0.2195.7376ntkrpamp.exe 5.0.2195.7376ntoskrnl.exe 5.0.2195.7376nwapi32.dll 5.0.2195.7109nwprovau.dll 5.0.2195.7110nwrdr.sys 5.0.2195.7110nwwks.dll 5.0.2195.7065oakley.dll 5.0.2195.7343oieng400.dll 5.0.2195.7144ole32.dll 5.0.2195.7103oleaut32.dll 2.40.4532.0olecli32.dll 5.0.2195.7009olecnv32.dll 5.0.2195.7059oledlg.dll 5.0.2195.7114openhci.sys 5.0.2195.6882polagent.dll 5.0.2195.6882polstore.dll 5.0.2195.6882printers.httpsbase.dll 5.0.2195.7164query.dll 5.0.2195.7320rasadhlp.dll 5.0.2195.7098raschap.dll 5.0.2195.7344rasmans.dll 5.0.2195.7099rastls.dll 5.0.2195.7344rdbss.sys 5.0.2195.7376remotesp.tsp 5.0.2195.7002riched20.dll 5.30.23.1227rpcrt4.dll 5.0.2195.7281rpcss.dll 5.0.2195.7116schannel.dll 5.1.2195.7213secur32.dll 5.0.2195.7244shell32.dll 5.0.3900.7155shlwapi.dll 5.0.3900.7349snmp.exe 5.0.2195.7112sp3res.dll 5.0.2195.7295spoolss.dll 5.0.2195.7054spoolsv.exe 5.0.2195.7059srv.sys 5.0.2195.7365stclient.dll 2000.2.3529.0sysmain.sdbt2embed.dll 5.0.2195.7348tapisrv.dll 5.0.2195.7057tcpip.sys 5.0.2195.7162telnet.exe 5.0.33670.4tifflt.dll 5.0.3900.7134triedit.dll 6.1.0.9235tsbyuv.dll 5.0.2195.7359txfaux.dll 2000.2.3529.0uhcd.sys 5.0.2195.6882umpnpmgr.dll 5.0.2195.7069usb.infusbd.sys 5.0.2195.6935usbehci.sys 5.0.2195.6882usbhub20.sys 5.0.2195.6891usbport.sys 5.0.2195.6926user32.dll 5.0.2195.7133userenv.dll 5.0.2195.7134webvw.dll 5.0.3900.7069win32k.sys 5.0.2195.7397win32spl.dll 5.0.2195.7266winhttp.dll 5.1.2600.3490winsrv.dll 5.0.2195.7135wintrust.dll 5.131.2195.7375wkssvc.dll 5.0.2195.7108wordpad.exe 5.0.2195.7155write.wpc 10.0.803.10xolehlp.dll 2000.2.3549.0
tomasz86 Posted March 17, 2012 Author Posted March 17, 2012 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.
Lucius Posted March 19, 2012 Posted March 19, 2012 (edited) 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 March 19, 2012 by Lucius
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now