Unofficial SP 5.2 for Microsoft Windows 2000 in preparation
Posted 16 May 2012 - 01:42 AM
I've been still analyzing the .NET Framework related stuff. I need to make sure there are no compatibility problems, etc. I'm going to make .NET 1.0 & 1.1 optional and 2.0, 3.0, 3.5 & 4.0 always installed. There are three scenarios regarding .NET 1.0 & 1.1:
1) .NET 1.0 (1.1) is already installed -> USP 5.2 will install .NET 1.0 (1.1), i.e. the existing installation will be updated.
2) .NET 1.0 (1.1) is not installed -> USP 5.2 will not install them but they will be available to install from Control Panel on user's request later.
3) In case of integration (/integrate) it's the same situation as in 2).
I've also updated M$ hotfix installer to the newest version, i.e. 22.214.171.124. It's required in order to be able to set some more advanced conditional sections in the update.inf.
This post has been edited by tomasz86: 16 May 2012 - 02:17 AM
Posted 17 May 2012 - 04:41 PM
I've been still fighting with the .NET related content. These .NET Frameworks install directly from CABs so installation & uninstallation process is very different from the normal M$ hotfix style. I need to make sure there are no issues, ex.
1) You've got .NET Framework 2.0 installed in your system before installing USP 5.2.
2) You install USP 5.2 so .NET Framework 2.0 is updated too.
3 You decide to uninstall USP 5.2... so what should happen to .NET 2.0? In this case it should be left untouched because it had been already present in the system before installing the USP.
It shall be different when:
1) You've got no .NET 2.0 in your system.
2) You install USP 5.2 so .NET 2.0 is installed with it.
3) You uninstall USP5.2... and in this case .NET 2.0 should also be uninstalled because there had been no .NET 2.0 in the system before installing the USP.
Everything is repeated for all the other Frameworks, i.e. 1.0, 1.1, 2.0, 3.0, 3.5 and 4.0. In case of .NET 1.0 and 1.1 the situation is different though. They are not installed with USP 5.2 by default but rather available to install on user's request from the Control Panel. There's one exception - if you've already got them in your system then they will be installed (and not uninstalled if you remove the USP).
I hope everything is clear. This is some crazy stuff actually because there's absolutely NO documentation about all these functions I'm using. That's why I've been analysing the update.inf file from SP2 for Windows Server 2003 because it's much much more advanced than the one from W2K's SP4/USP5 and most of the things needed are there. Still, due to the fact that nothing is documented, it's a trial and error game.
For example, this is what I managed to do for .NET Framework 1.1 and 2.0.
and all of this is only to make installation and uninstallation of these two Framework work and I'm still not sure if everything works correctly.
Posted 04 June 2012 - 12:43 AM
It was used by Gurgelmeyer in his signature linking to "http://www.willsdown...og/win2ksp5.php" which is not online anymore. The icon itself seems to be made originally by a person called Aegis. He was banned here long time ago so unfortunately it's not possible to ask for his opinion on it.
Do you think it would be (in)appropriate to use it for USP 5.2?
Posted 15 June 2012 - 04:25 PM
I want to store there all information, details and links related to USP 5.2 and other packages. Of course I'll update this topic too
Any comments or critique is welcomed. Please tell me if there is something missing, something more to add or if there are any errors. I've added the URL together with the icon (thanks bphlpt!) to my signature.
Posted 18 June 2012 - 04:06 AM
SETUPUSP.EXE /Q /N /Z
This post has been edited by tomasz86: 18 June 2012 - 04:07 AM
Posted 18 June 2012 - 04:55 AM
This post has been edited by xpclient: 19 June 2012 - 03:44 AM
Posted 21 June 2012 - 08:32 AM
First of all, I think the current testing process must be simplified. At the moment HFSLIP must be used to slipstream UURollup in order to have the USP integrate and install properly. I'd like to avoid this as it just takes too much time to process the package through HFSLIP. Starting from the next test version I'll make it possible to slipstream the USP using the "/integrate" switch and prepare an ISO directly from it without using other tools (HFSLIP, nLite, etc.). I've already prepared a script which will automatically create the ISO after slipstreaming. Maybe later Qemu could be also used so the whole procedure will be simplified as much as possible.
As soon as possible I'll provide an URL where all test versions of USP will be located. Everyone will be able to download and test them. I'm going to upload new versions very often (being realistic it'll be probably one version every few days). All changes done in each build will be also described in details.
What's your opinion about it?
Posted 21 June 2012 - 06:24 PM