Gurgelmeyer

Well, I'm trying to figure out how to stay compatible with WU without installing .NET 1.1+2.0 from the MSI/MSP. I might not succeed, but at least I'm having fun /G B)

The Codec drivers is a really good idea. /G B)

Good news: I got the real files now. Funny - because literally every bit of them match the XPSP2 ones. It's in the latest USP's, which I've just uploaded (they will probably be available for dl very soon). Best regards Gurgelmeyer B)

msvcp60.dll is included in USP 5.1. Best regards Gurgelmeyer B)

Any news?? Please tell me some good news soon. I've been trying to get it from MS PSS myself but they wont let me have it unless I pay. I think this LAST USP 5.1 release somehow deserves a little extra attention, so I'm adding the 4 security updates from this week in the meanwhile. Hope noone minds /G B) (ps - by LAST USP 5.1 I mean that NEXT USP will be 5.2 - so this one has to last a few months)

@-I- - nope - these errors occur only in real mode DOS and in the text mode part of Setup, so WFP isn't installed yet. /G B)

Fixed. Add/remove Components also works like it should now. Thanks again for pointing it out /G B)

I could give it a try I guess /G B)

@-I- - Thanks - please do

Hi I hardly believe my eyes - you are the first person to find out about a hotfix which is NOT included in the USP. Thank you Well - I need some help here.... does anyone have it? Please?? /G B)

Thank you for writing this FAQ - it is much appreciated. /G B)

@NotVeryNice - You cannot - I'm fixing the DOS setup problem at the moment (the "WINNT.EXE" problem mentioned in the other threads). I'd rather not release anything with any known bugs And the solution is unfortunately not as simple as suggested. I'll release my personal December edition of the ancient USP 5.0 too - it's especially good for servers - and completely "unsupported" btw /G B)

USP 5.1 introduces msvcp60.dll 6.0.8972.0 because one of the updated IE6SP1 components will not register without it. This dependency was introduced in a security update. /G B)

Hi everyone Since this seems to be the "main thread" I better post this here: I've decided to rebuild and release USP 5.1 build 19 (Service Release 1). It contains about 30 more non-public hotfixes, and all security fixes. I also have such a thing as my USP 5.02 BUILD 15 PERSONAL EDITION. I've REMOVED Automatic Updates and Set Program Access and Defaults entirely from this edition (because these were not originally part of W2K). It was built in December, and this is what I use myself on my workstation. Would anyone want it? Best regards, Gurgelmeyer B)

Yeah - it's not always as easy as one would imagine Anyway - I got to the bottom of the problem - it has a lot of time, but I needed to know myself: 1 - There is in fact a syntax error in DOSNET.INF - the line "d1.nntpfs.dll" should of course be "d1,nntpfs.dll". This is the error that WINNT.EXE reports. This bug is mine, and it will be fixed now. 2 - WINNT.EXE (16-bit) sometimes has problems with VFAT it seems - although VFAT entries ("long file names") are not supposed to be accessible in pure DOS mode, their presence seems to confuse WINNT.EXE. I have no idea why (best bet is that this is a bug in DOS), but it's best to keep all filenames in upper case. Silly, really. There's nothing I can do about this. 3 - In TXTSETUP.SIF I refer to the disk label file "disk1", but it's not listed in the [Files] section of DOSNET.INF. This is mine, and it will be fixed now. 4 - In case WINNT.EXE decides to prepare a Local Source ($WIN_NT$.~LS), it gets confused because some files have multiple destinations in TXTSETUP.SIF. This is a limitation of WINNT.EXE, and it generates a lot of warnings. MS never need to have multiple destinations for any file in TXTSETUP.SIF - but this is only because they can sign their own catalogs. But I won't even try to explain this, because it's painfully complicated. It's possible to create a DOSNET.INF/TXTSETUP.INF that does work perfectly with WINNT.EXE - only problem is, that this breaks the Add/Remove Windows Components feature once Windows is installed. 5 - If any hotfixes are integrated into a W2K SP4 the documented way, WINNT.EXE won't work either. Best regards, Gurgelmeyer B)

Nope. But 6920 is rather old - latest version I have is 7050 /G B) PS - KB article reviews usually dont mean that the hotfixes are rebuilt - usually there is no way of knowing that.

I'v reproduced the problem. It might be related to DOSNET.INF somehow. I'm looking into it. Sorry for the inconvenience. /G B)

It's done "USP 5.1 19 2006-03-06" (without the quotes) now shows up in System Properties just below the PID. Btw this is the new USP 5.1 SR-1 that I did yesterday - I might release this, or wait a week longer and have next tuesdays updates included. Generally - to verify if a particular update is included, check the file versions - WUv6 does just that, because it's the only reliable way. A few updates are flagged as installed in the registry - these are pre-MSURP1 security updates. MSURP1 flags these as installed too. Best regards, /G B) PS - About listing hotfixes included - it's much more complicated than you guys might imaginge, because they overlap eachother. But if we stick with security updates and other updates available from WU it's very simple - would it be of any use? /G B)

Thanx Almost finished USP 5.1 SR-1 (build 19) - had to do something easy to get back on track after two computer crashes and a month or two of illness... just need to look into the DOS setup. This build seems to speed up windows a bit compared to SP4 - but I might be imagening things - anyway public RC available soon. Best regards, Gurgelmeyer B) Thanx Almost finished USP 5.1 SR-1 (build 19) - had to do something easy to get back on track after two computer crashes and a month or two of illness... just need to look into the DOS setup. This build seems to speed up windows a bit compared to SP4 - but I might be imagening things - anyway public RC available soon. Best regards, Gurgelmeyer B)

Hi I'll consider a USP Release ID in future releases. I just don't know if you guys want it to show up in the System Properties or not? I ran regmon the other day and found a long forgotten feature which actually allows two further lines of text to appear below the product id. Those entries are leftovers from Plus!/IE on NT4. Could be something like "USP 5.1.19 2006-01-11" Best regards, Gurgelmeyer B)

I'll look into this - it really ought to work. G B)

Thanks for your support, guys. I'm happy to be here I feel better at the moment. My heart has suffered permanent damage, and that's all I know and all I want to know. On the bright side, I have more time for doing the things I like, such as USP's, spending time with friends and relatives, and listening to music. Best regards, Gurgelmeyer B) PS - RyanVM - I'm still looking into the 300 .cat-files problem on XP from time to time. I'd like to get rid of the svcpack.inf in my own USP's too while I'm at it.

Thanks for caring, guys!! I feel much better at the moment - I even managed to fix this old wreck of a PC, which seems to have been in an even worse condition than me. So all the strippers and the nice ale is for real and not a hallucination caused by my medication - sweeeet - that explains some things - thanks to fdv and the rest of the HFSLIP crew

A fully patched and "hotfixed" Internet Explorer 6.0 Service Pack 1 with Outlook Express 6.0 Service Pack 1 and Windows Address Book 6 and Microsoft Script Engines 5.6 and Microsoft Installer 3.1 version 2 and Background Intelligent Transfers version 2.0 and all security patches including those from December 2005 are ALREADY IN THE EXISTING USP 5.1, WHICH IS FINAL AND AVAILABLE FOR PUBLIC DOWNLOAD So just hook up your modem and start the download - I know it takes almost 2 days, but trust me, if I didn't already have this USP and I was stuck with a 56k modem I would definately download it myself no matter how long it took And I would still prefer the full package rather than rollups. When I downloaded W2k SP1, SP2, SRP1, SP3, and SP4 I was in fact on a 56k modem myself - and I survived, although my girlfriend at the time was pretty annoyed because she couldn't call me three times a day on the phone to let me know how she was doing USP 5.2 - which was proviously referred to as the USP 5.1 Standard Edition project - will add MDAC 2.8 SP1, DX9c and WMP9 and - when I figure out how to - .NET 1.1 and .NET 2.0 and whatever is left on WU. It wont be ready for another month at least. USP 5.5 / USP Extreme will add all the extras which are not on WU, such as the Remote Desktop client, TweakUI 1.33, etc. Best regards, Gurgelmeyer B)

Yes, I'm afraid there's no way around this massive download. The irony in this is, that in order to make the slipstreamed w2k image as small as possible I need to include more files. For example I include a rebuilt and optimized DRIVER.CAB and a rebuilt and optimized SP4.CAB - only because I cannot change DRVINDEX.INF as Microsoft would have done, because this breaks the digital signature on the .INF. However, once you integrate USP 5 into your dsitribution share or CD image you will benefit from the fact that the integrated image is actually several megabytes _smaller_ than an integrated SP4 image, which is _because_ it now contains my optimized DRIVER.CAB and SP4.CAB. This leaves more space on the HD as well, even if you just make a regular install of USP5. But lately I've considered to release a Rollup too - however this will NOT integrate - and I'll block the /integrate option entirely if I choose to release this. USP 5.1 (formerly known as Basic Edition) is already done. You can dl it from Will's place (click my signature to get there) or from SoftPedia and soon from MajorGeeks as well I hope. USP 5.1 (formerly Basic) "only" integrates components from the 'Critical Updates' section on 'Microsoft Update' or 'Windows Update'. Also it includes some non-publicly available IE6 fixes. The advantages of downloading USP 5.1 - compared to installing USP 5.0 and then visiting 'Windows Update' to get the critical updates - are, that your total amount of downloaded bytes will be smaller (USP 5.0 + WU > USP 5.1), IE6 will effectively replace IE501 if you integrate USP 5.1 (and likewise will the other components included), and whether or not you do an integrated install you will save space on your HD and in the registry. Very few "new" files have been introduced in USP 5.x compared to SP4. To the best of my recollection all IIS updates and fixes resulted in never versions of files which were included in SP4 anyway. No extra IIS files will be installed, unless you install IIS from the Add/Remove Programs - USP's generally behave like ordinary MS SP's. For compatibility the service pack level is kept at SP4. I have even fixed the registry bugs that MS allowed in SP4. No problem