SoLoR, two more from that batch I sent can be eliminated: 2654347 is superseded by 2675469 (also in that batch) 2651992-v2 is superseded by 2667241-v3 (just released) This info courtesy of the latest KUC from komm. McRip, this also applies to your repo We just passed the one year anniversary of SP1 also.
Just a proposal. Add the ip's to the host file. Since I added those I don't have any issues with downloading hotfixes. 207.46.232.182 hotfixv4.microsoft.com 64.4.11.26 hotfixv4.microsoft.com
@RicaNeaka I am just preparing a new zipped file. And uploading takes time. Regarding the .txt file. Maybe RickSteele can do this for me? Because I'm fully immersed in work. Rick has access to the server.
This repo was not supposed to be a duplicate of Solor's Repo. It is supposed to be just a Repo with all hotfixes and updates which are currently up-to-date. We are trying to do our best to satisfy any wishes. But as I wrote before, not any wish can be satisfied. I guess you can not imagine how much work is involved behind the scenes. But I can assure one thing, this Repo will remain up-to-date. What do I need a folder with superseded updates for? I do not need it. I need updated files only. And files that can satisfy Windows Update. With the support of this forum all updates will be updated asap. With the next update, next week or so, I will put all the addons into an extra folder to satisfy one wish for now. There are many great tools spread around here for installing the the updates correctly. I'm gonna modify the install.cmd a bit to satisfy WU. As I said. This "not-Solor's Repo" will remain up-to-date.
To all; Many of us, myself included, are not as technilogically advanced or are programmers, either in training or graduated, as many posting in this thread. We do not scan M$ downloads as SoLoR did, or have his, Burf's, ricktendo's, Komm's etc. expertise, but, rely on posts here and elsewhere plus our own consistantly visited resources to stay "informed". That is all most of us are prepared to do. In that context, what would everyone think of opening a new thread along the lines of "Post Feb 17 Windows 7 updates" where all these new post Feb 17 updates could be posted. SoLoR's thread is too large and confusing now, it seems no one wants to try the few packs out there other than SoLoR's, so, his Feb. 17 submission appears to be the defacto base standard by which everyone compares new to old.
Having a centralised list with mirrors is better than having many lists that miss certain updates... SoLoR's list served as this 'centralised list' mainly because of how well he did it. I do agree a cumulative removed/updated etc list is very useful, its a lot easier to track which updates are new and which updates have been removed. I'm not a programmer nor have I been trained as a programmer, for me it was about conceptualising how the functions of the tools work then working towards that goal. I do have a reasonable understanding of the commands I used though, I wasn't going into it completely 'blind' as the saying goes. @Komm, how do you determine the updates needed to satisfy Windowsupdate? as you have many in your KUC that said is needed but isn't to satisfy my WU, and I have a couple installed to satisfy WU that KUC says to remove. Just curious, ithanks for providing a great utility
@McRip/RickSteele It's excellent if you intend to organize them in folders, like SoLoR does - IIs, Integrate to Installation Media, MSMQ, etc - at least that's what I understand from your posts. I really need a way to compare your pack to SoLoR's, either from how you organize your addons, either from a .txt changelog. My need and others's comes from ex. slipstreaming those updates into an untouched windows 7 SP1, utilities like KUC are made for a live system, so a changelog for post-17th-february-updates (and post future-releases, yours and/or SoLoR's) would also help me and others alot. Also, I don't think it would be a good idea to be very original on how to organize the updates, since SoLoR has done a great job so far. I've already found at least an addon in your pack I wasn't aware of to be needed for windows 7 (VC++5), so I'm already very happy with your work. I just want for your addon to be better / easier to cope with by people used to SoLoR's way of making packs, and the best way I can help for now is by making this suggestion. Once again, thank you for the hard work you've done so far