Gurgelmeyer

@pene - Oh... v6 finally hit us - well if it's anything like v4 it's all in the registry. Anyway, I'm making a real effort to keep WU happy, flagging the right things in the registry etc. It's tough - maybe I need to redo some stuff with v6 - definately needs testing. Thanx for pointing it out

Hi About the memory-thing, a "hotfix" which replaces the memory manager with a low-fragmention one is already part of the SP5. I don't remember it's number, and I don't feel like reading >300 KB-articles once more to find out - but it's there - trust me! There might be a seperate forum for this project, but it does require a few things from me, which I haven't fulfilled yet. A lot of you guys - especially those who've tested the /integrate'able SP5 - have been asking about this too, and it probably will happen. There's definately gonna be some info and stuff on Will's homepage I might mention. Anyway, I'm working on integrating a few updated fixes too before the final RC of "Unofficial SP5". I just recovered from a major hardware crash, but it's not as big a deal as it sounds, because I've backed up everything every day before powering down my PC Best regards, Gurgelmeyer B)

@slippykillsticks - I didn't do that test myself - a friend of mine did. I'll ask him @hoak - WISH YOU WERE MY BOSS - I'm not releasing anything until it's done. And I don't even take my own word for it - some really cool guys are helping me with the testing. If anything whatsoever seems wrong I'll postpone the release for as long as it takes to get it 100% right - because less just won't do. Anyway, I'll put on my favourite CD, sit back with a nice cup of coffee and do something completely different for the rest of the day. I do need to unwind a bit. @Aegis - they might have officially discontinued "Powered;" but SP4 and every hotfix I've seen (which is quite a lot) support "Powered." So I imagine it might still be out there somewhere - then again I do have quite a vivid imagination at times ...

MS URP doesn't "really" integrate like a SP. I guess the wms folder is some sort of substitute for replacing wms4.cab. This is where the files belong (part of a SP5 build log): i386\NSCM.EXE -> I386\nscm.exe i386\NSCM.EXE -> I386\wms4.cab\nscm.exe i386\NSIISLOG.DLL -> I386\nsiislog.dll i386\NSIISLOG.DLL -> I386\wms4.cab\nsiislog.dll i386\NSISAPI.EXE -> I386\wms4.cab\nsisapi.exe i386\NSPMON.EXE -> I386\wms4.cab\nspmon.exe Usually NSISAPI.EXE and NSPMON.EXE only exists inside the cab.

Update: Unofficial SP 5 works perfectly with nLite SP5 is not yet perfect however. I'm going through a few hundred registry settings with a toothcomb to make sure everything is at least 100.7% correct. Maybe I should look into slipstreaming the IC package (IE6) as the first thing when SP5 is done... "Stay tuned" - FINAL RELEASE BEFORE MONDAY (ouch -- my ears....)

Hi, Hmm - I've been giving it some thought. Releasing the full cumulative Service Pack 5 might not be such a bad idea - mostly because that's what everybody wanted in the first place, right? I'll have a chat with Will. Making localized versions will probably be a walk in the park; but - like SP4 - the english SP5 will not install/integrate into a non-english W2K. Finally it would make me really happy if anyone could test SP5 on Windows 2000 Datacenter and Windows Powered (the fifth and really rare edition of 2k) before it's released. It is already being tested on Windows 2000 Server and Advanced Server by one of the really cool guys in here. Best regards, Gurgelmeyer

Hi everyone, Thanks a lot for your many kind words I better do a summary (for those who have joined this thread recently). I'm doing two projects: - Project 1 is the unofficial Service Pack 5 for Windows 2000 - or just SP5. SP5 is cumulative in the sense that it does not require SP4. Furthermore it fully supports slipstreaming. SP5 contains everything in SP4 and the latest versions of every single hotfix ever made for Windows 2000 with SP4 (I think) and its built-in components (such as COM+ 1.0, IIS 5, IE 5.01, etc, etc) including the "MS URP1", which is really just another hotfix. SP5 contains hundreds (!) of bugfixes which are not in the "MS URP1" and not available from Windows Update. I started out by making a non-cumulative "Update Pack" for Windows 2000 SP4. I had several reasons: /integrate is not supported by all hotfix executables, a fully updated Windows 2000 would no longer fit on a CD if the hotfixes were integrated manually, it would take forever to install because several hundred hotfix executables would run during setup, it would be unreliable for the very same reason, the registry would grow significantly, and finally the distribution share would be a complete mess. So the first step was to put all the hotfixes into one hotfix - the "Update Pack". This way all the hotfixes could at least be safely and conveniently installed and removed. Second step was to implement automatic slipstreaming. But the only thing that didn't seem possible with the Unofficial Rollup 1 way of doing things was slipstreaming! At least not with the built-in /integrate switch. So I finally pulled myself together and made a "Service Pack" version instead, because this way it's possible to support the /integrate switch. So now I got a SP5 (have to add five more reg-entries, but otherwise it's done). The "Update Pack" was later renamed to "Unofficial Rollup 1" btw - or just URP1. This rename has caused much confusion. Wonder why... Anyway, the "Unofficial Rollup 1" from last month is available for public download. Many more hotfixes have been added since then, but I've chosen not to release any new build which doesn't support the /integrate switch. Back on topic: why don't I release SP5 then? The answer is simple: it's HUGE (almost 200MB when compressed) and the reason for this is, that it's cumulative! So I'm going to make a non-cumulative version which will require SP4. I don't expect it to be complicated at all compared to what I've already been through. OK - enough about the SP5 project - Project 2 is the unofficial Option Pack 1 for Windows 2000. The Option Pack is the one that will only require SP3. It will contain all the usual components available for Windows 2000 SP3-SP4, such as IE6, MDAC27, MSI31, WMP9, NET11, DX9, etc etc, including all hotfixes for those. And it will support the /integrate switch! I've not worked on this project some time now, but I'm looking forward to get back to it. The packages available for download are simple repacked versions of a few of the Option Pack components. The final Option Pack will contain all these components in one, with the possible exception of IE6. Hope this clarifies things just a little bit B) Btw I love the idea of doing a driver pack. Best regards, Gurgelmeyer

Thought they'd never release it I finally have a chance to finish my Unofficial Rollup - so that's exactly what I'm gonna do.

Thanx Well, it ought to work perfectly with nLite - but I haven't tested how nLite reacts to the new integrated image (yet), so I can't say for sure. My SP5 will hide many installed hotfixes, but they'll show up in ARP again if the SP5 is removed. (Just like the MS URP). I still have some reg settings to update - nothing fancy, but it does take a little time to get it perfect. Best regards Gurgelmeyer

Hi Thanks for all your support, guys - I really appreciate it. I'll make a new test build as soon as I've tied up a few lose ends - I'll keep you posted I cannot make it public before I've reduced it from a cumulative SP5 to a non-cumulative URP, because it's huge - but if anyone wants to test the whole cumulative SP5 drop me a PM. It will be ready in a day or two. Best regards Grugelmeyer

Update: /integrate now works, all editions of w2k are covered, integrated files remain compressed. Need to add a few files which are not part of the original w2k setup, such as msxml3/msxml3r.dll and some .cat's. Best regards, Gurgelmeyer B)

Thanks for your input About Messenger - I'll not add it to the Option Pack, but it will a bit unfair to those who want it to prevent it from ever installing. One reg setting that I might include would be the one that "detaches" Messenger from OE. I don't know about others - but personally I find it very annoying that OE starts Messenger automatically. I can probably do a nice "repack" of Messenger as a standalone Type1 package though. Hmmm....BITS2.... I've never experienced any problems with it myself, but one of the many sysadmins I know experienced some odd behaviour after deploying it (connectivity issues I think). But I'll have another chat with him, because it's so long ago that I no longer remember. If I can't reproduce any of the problems myself (or if they are too obscure), I'll include it. About the /integrate option, I'm almost done. No real problems so far, just lots of work (to keep the process fully automated so human error may be avoided entirely) and lots and lots of testing and .INF reading and writing. Actually it would be easier for me to make a "real" cumulative SP5 with /integrate and updated support and deployment tools - but the download would become rather huge then (~150 MB). And WU doesn't know what SP5 is - it's hard to keep WU happy I guess I could write an entire book about this once I'm done - but then again, I'm no Merilyn French. Also Gape's 98SE SP2 needs an /integrate, and I might offer my assistance later this year - not to mention the many exciting new projects all you cool MSFN guys have suggested. Hope to be able to try out my FIRST "real SP5" later today Gurgelmeyer B)

Some hotfixes from WU will be in the MS URP1. The MS URP supports /integrate. I'm working on /integrate support for my own URP. IE60SP1, DX9C, WMP9, MSI31, MSXML*, MDAC*, NETFX11, etc etc (there's a more comprehensive list some pages back) including latest SPs and QFEs from WU (and a few extra ones for IE6) for those are exactly the components which I intend to join in the Option Pack. The Option Pack will support /integrate too - that's why I'm repacking everything as Type1 fixes. At the moment they are separate components, but they will be joined later on. I might keep IE6 available as a separate component too. -Gurgelmeyer PS - I'm not sure what to do with BITS20 (it will definately not be in my URP). Also Messenger is just about the only thing I haven't planned for the Option Pack. Should I include it?

@dziubek - hi 1) I'll make a list when my Unofficial Rollup 1 (update pack) is final. At the moment I'm waiting for the MS URP to be released. 2) Maybe. But I only have the English versions of the >260 non-public post-sp4 hotfixes. If anyone can get the non-public hotfixes in other languages, I'll be happy to assemble a localized Unofficial Rollup 1. I hope to find the time to make localized versions of the Option Pack however. But I haven't even finished the beta yet. 3) Public previews are right here: http://www.willsdownloads.com/hotstream/hotstream.php Take care, Gurgelmeyer B)

I just deleted this post -- don't want to get political - it won't do anyone any good anyway B)

This is just strange - why doesn't MS release their URP? But it's good for me, because it buys me more time to finish the /integrate option.

Don't be confused - allow me to explain: Windows2000-URP1-x86-enu.exe is the "Update Pack". It contains (1) all non-public Post-SP4 hotfixes and (2) the MS URP1 (which contains all the security fixes) for Windows (and the built-in components). The security fixes that were released this month are not included yet. But they will be - even if they are not in the final MS URP1 they will be in mine. The "BITS 2.0" update is deliberately excluded, because I've heard some very bad things about it - and it's not (!) really a critical update, nor a security update. MSI 3.1 belongs in the Option Pack, because it's a component upgrade like IE6, WMP9 etc. The IC.EXE includes KB887797 (December 2004 OE security rollup) and KB890923 (May 2005 IE security rollup). KB890923 has just been replaced by Microsoft. So the answer to your question is yes - but both packages are from last month. B)

Hi Exactly - I can't really finish the Update Pack (aka "Unofficial Rollup 1") before the MS URP is out. I'm working like crazy on /integrate to make sure I get everything right - but it will take me a few more days (and nights). If, however, the MS URP gets out tomorrow, I'll do a rebuild anyway, but with the old layout/update script that does not support /integrate. But I'll re-release it with /integrate support in a few days. @Ephemeral2 - Thanks! And yes, the IC.EXE will be part of the Option Pack, but not as a standalone component. The Option Pack will be a package with all the usual updates in one. Btw, a while ago I did a new IC.EXE that doesn't need to register all the COM objects after a reboot (like the MS IE6 installer and my existing version does). All the components are registered by the .inf script, which is much faster. Did the same thing with DA.EXE. But I haven't prepared them for release just yet - I think the /integrate option deserves my full attention at the moment. Best regards, Gurgelmeyer B)

"W2K IE6SP1 Total Slipstream-topic" is a great thread - you really ought to read through it once more I was very tired when I wrote the above - sry (had been working for 20 hours straight on my own project) - so I forgot to mention the most important thing: wrap up all components in IExpress packages. That's how I made it work a year ago or so - I remember now. IExpress is part of ieak6. OR: you could download my DX9 / IE6 repacks - they don't need further repacking to run from svcpack.inf. Generally this place has so many cool guides and info on integrating - there's a nice way to do the registry trick too I remember - check out the guides I better keep quiet for now and get back to my "hotstream" project Best regards, Gurgelmeyer

Hi! 1. Copy the files to "i386\svcpack" 2. Add "svcpack" (no quotes) to [OptinalSrcDirs] in "i386\dosnet.inf" 3. Delete the "i386\svcpack.in_" file 4. Create a "i386\svcpack.inf" file: [Version] BuildNumber=2195 MinorVersion=0 MajorVersion=5 Signature="$WINDOWS NT$" [SetupData] CatalogSubDir="\I386\svcpack" [SetupHotfixesToRun] IE6THING.EXE /Q otherstuff.exe /quiet morestuff.exe /veryquiet [ProductCatalogsToInstall] Usually works for me

Phew - got myself another week to work on /integrate. I might change the Update Pack to install as a supplemental service pack rather than a hotfix - there are too many errors in UPDATE.EXE when it runs in "hotfix mode", but it behaves perfectly when running in "service pack mode". If I added SP4 I could even make a real SP5 - but I won't

Hi No localized version of my work is yet available. However building Central European or Western European "hotstream" packages is technically not much of a problem. Here is how it could work: 1) You team up with some other French users, and aquire as many non-publicly available w2k post-sp4/post-urp1 hotfixes from Microsoft as possible. 2) I download them from you, and do a French build for you. I already promised to make localized versions of my Option Pack (not the Update Pack) - but I haven't even found the time to finish the english version yet... Best regards, Gurgelmeyer

Thanks hoak B) - it's probably too late for them to do anything about it anyway. MS URP - well it might be available in 20 minutes from now, or it might be available next week.

OK - I'll make sure someone tells them.

Thanks, hoak - I appreciate all the support from you folks in here Just stumbled over some bugs in the MS URP. The /integrate option does work properly - some files are not replaced. I can do better then whoever wrote that update.inf at Microsoft (I hope ) Best regards, Gurgelmeyer PS - the errors are _only_ in the MS URP - should I tell them?? Would they care???