bphlpt, on 30 July 2011 - 07:43 PM, said:
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.ne...opic.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