tomasz86

In the end I've managed to prepare this primitive script: SETLOCAL ENABLEDELAYEDEXPANSION SET SOURCEDIR= SET DESTINATIONDIR= FOR /F %%I IN ('DIR/A-D/B "%SOURCEDIR%"') DO ( IF EXIST "%DESTINATIONDIR%\%%I" ( FOR /F "tokens=5" %%J IN ('FILEVER "%SOURCEDIR%\%%I"') DO IF NOT "%%J"=="-" ( FOR /F "tokens=5" %%J IN ('FILEVER "%SOURCEDIR%\%%I"') DO SET SOURCEVER=%%J FOR /F "tokens=5" %%J IN ('FILEVER "%DESTINATIONDIR%\%%I"') DO SET DESTINATIONVER=%%J FOR /F "tokens=1 delims=." %%I IN ("!SOURCEVER!") DO SET SOURCEVER1=%%I FOR /F "tokens=2 delims=." %%I IN ("!SOURCEVER!") DO SET SOURCEVER2=%%I FOR /F "tokens=3 delims=." %%I IN ("!SOURCEVER!") DO SET SOURCEVER3=%%I FOR /F "tokens=4 delims=." %%I IN ("!SOURCEVER!") DO SET SOURCEVER4=%%I FOR /F "tokens=1 delims=." %%I IN ("!DESTINATIONVER!") DO SET DESTINATIONVER1=%%I FOR /F "tokens=2 delims=." %%I IN ("!DESTINATIONVER!") DO SET DESTINATIONVER2=%%I FOR /F "tokens=3 delims=." %%I IN ("!DESTINATIONVER!") DO SET DESTINATIONVER3=%%I FOR /F "tokens=4 delims=." %%I IN ("!DESTINATIONVER!") DO SET DESTINATIONVER4=%%I IF !SOURCEVER1! GTR !DESTINATIONVER1! MOVE "%SOURCEDIR%\%%I" "%DESTINATIONDIR%" IF EXIST "%DESTINATIONDIR%\%%I" IF !SOURCEVER2! GTR !DESTINATIONVER2! MOVE "%SOURCEDIR%\%%I" "%DESTINATIONDIR%" IF EXIST "%DESTINATIONDIR%\%%I" IF !SOURCEVER3! GTR !DESTINATIONVER3! MOVE "%SOURCEDIR%\%%I" "%DESTINATIONDIR%" IF EXIST "%DESTINATIONDIR%\%%I" IF !SOURCEVER4! GTR !DESTINATIONVER4! MOVE "%SOURCEDIR%\%%I" "%DESTINATIONDIR%" ) ELSE ( XCOPY/DY "%SOURCEDIR%\%%I" "%DESTINATIONDIR%" ) ) ) PAUSE You just need to set the two variables - SOURCEDIR & DESTINATIONDIR. You will also need Filever.exe. The one from Windows Server 2003 Service Pack 2 32-bit Support Tools works fine. Edit: Even simpler: SETLOCAL ENABLEDELAYEDEXPANSION SET SOURCEDIR= SET DESTINATIONDIR= FOR /F %%I IN ('DIR/A-D/B "%SOURCEDIR%"') DO ( IF EXIST "%DESTINATIONDIR%\%%I" ( FOR /F "tokens=5" %%J IN ('FILEVER "%SOURCEDIR%\%%I"') DO IF NOT "%%J"=="-" ( FOR /F "tokens=5" %%J IN ('FILEVER "%SOURCEDIR%\%%I"') DO SET SOURCEVER=%%J FOR /F "tokens=5" %%J IN ('FILEVER "%DESTINATIONDIR%\%%I"') DO SET DESTINATIONVER=%%J FOR /F "tokens=1-4 delims=." %%I IN ("!SOURCEVER!") DO ( SET SOURCEVER1=%%I SET SOURCEVER2=%%J SET SOURCEVER3=%%K SET SOURCEVER4=%%L ) FOR /F "tokens=1-4 delims=." %%I IN ("!DESTINATIONVER!") DO ( SET DESTINATIONVER1=%%I SET DESTINATIONVER2=%%J SET DESTINATIONVER3=%%K SET DESTINATIONVER4=%%L ) IF !SOURCEVER1! GTR !DESTINATIONVER1! COPY/Y "%SOURCEDIR%\%%I" "%DESTINATIONDIR%" IF EXIST "%DESTINATIONDIR%\%%I" IF !SOURCEVER2! GTR !DESTINATIONVER2! COPY/Y "%SOURCEDIR%\%%I" "%DESTINATIONDIR%" IF EXIST "%DESTINATIONDIR%\%%I" IF !SOURCEVER3! GTR !DESTINATIONVER3! COPY/Y "%SOURCEDIR%\%%I" "%DESTINATIONDIR%" IF EXIST "%DESTINATIONDIR%\%%I" IF !SOURCEVER4! GTR !DESTINATIONVER4! COPY/Y "%SOURCEDIR%\%%I" "%DESTINATIONDIR%" ) ELSE ( XCOPY/DY "%SOURCEDIR%\%%I" "%DESTINATIONDIR%" ) ) ) PAUSE And a little bit more explanation: If you don't split the file version into 4 values then doing something like this: IF 5.2.3790.620 GTR 5.2.3790.4110 COPY/Y "%SOURCEDIR%\%%I" "%DESTINATIONDIR%" will actually result in the first file being copied over the second one, i.e. it will think that "5.2.3790.620" is greater than "5.2.3790.4110". On the other hand, if you split the values and do IF 620 GTR 4110 COPY/Y "%SOURCEDIR%\%%I" "%DESTINATIONDIR%" then it will not be copied because 4110 > 620. This is a real life example I've just tested here (the file being hhctrl.ocx).

@blackwingcat Some time ago you prepared Windows2000-KB954434-INTL.exe. The files included in it are: HAL.DLL 5.0.2195.6692 halaacpi.dll 5.0.2195.6692 halacpi.dll 5.0.2195.6692 halapic.dll 5.0.2195.6692 halborg.dll 5.0.2195.6692 halmacpi.dll 5.0.2195.7007 halmps.dll 5.0.2195.7007 halsp.dll 5.0.2195.6692 There are newer version of the three files available in KB835730: Halaacpi.dll 5.0.2195.6988 Halacpi.dll 5.0.2195.6988 Halmacpi.dll 5.0.2195.6988 Would it be possible to update the three files in KB954434?

@Elvi Of course the script wont work! You need to modify it accordingly to the structure of the USP3 which is very different from UURollup.

@Elvi You may want to have a look at my conversation with Hackeronte about translating UURollup. It starts from here. I don't know if filever.exe works in Win98 though. It would be much faster to check files with a script instead of analysing them one by one manually.

@ I strongly recommend installing the final version. A lot of bugs were fixed and many updates were added in between. The alpha3 was created for testing purposes and shouldn't be used anymore. Moreover, if I remember correctly, KB888111 was actually not included in the alpha3

I think you should try with a fully updated Win2k source. I suspect that you're using an Italian system so the only "proper" way would be to download and slipstream all ITA/Global version of updates listed on bristols site. On the other hand, it will take a lot of time to prepare everything and you still don't know whether it's successful. Just for testing purposes I'd suggest following the "basic method" described on my website. What you should do is to integrate the English packages into your Italian Win2k source. Don't worry, everything will be fine except for the fact that most of the system will be English. By doing so you'll be able to check whether the problem lies in the source (you're using Win2k SP4... which dates back to 2003). Here's a detailed instruction:

You can safely add SATA drivers. The only problem would be if you had already other version of the same drivers (=same filenames) already integrated. Just don't select any other option in nLite except for driver integration and/or ISO creation.

@ You said in the other topic that you had Update Rollup 2 installed, didn't you. KB888111 is included in it

@WildBill There seem to be some problems with the newest version of ntdll.dll. Please have a look at this topic. I used ntdll.dll 5.0.2195.7084 in UURollup-v10 which caused all the issues which are now gone in UURollup-v11 where the older version of ntdll.dll (5.0.2195.7083) is used.

@ So I can confirm that it works with the .NET 4.0 installed but please wait for the final version Edit: It was too good to be true. The program indeed can be started and you can even start creating something but then it crashes when trying to either save your project or open an another one. There is something wrong with .NET 4.0 and Win2k which prevents it from running. At the moment only a very limited usability is provided. Probably only a very simple .NET 4.0 applications will run while all of the more complicated ones will crash at some moment.

@ Do you mean this one?

Could you tell me names of the applications concerned? I'd like to check if they work with .NET 4.0 installed. @acus Thanks. Everything as expected. The uninstaller is not complete yet.

Just a short update: I'm still fighting with .NET 4.0. I've managed to fix a lot of errors but there are still some issues left. I've just uploaded the first experimental version to the SkyDrive archive. It doesn't require any other Framework but UURollup (ENU) is necessary.

Probably the driver itself is not compatible with Win2k and must be modified to work... so you should probably ask BlackWingCat to have a look at it You may also ask about it on Windows 2000 Gaming forum.

Frankly speaking, it seems to be too much of a hassle to make it work in a stock Win2k. Have you tried out the portable version?

The problem here is not about KDW. I used KDW only to allow the installer to work in Win2k. The problem is about Visual Studio 2010 which was used to compile to the package. You need an unofficial kernel to make the program start. That's why I mentioned UURollup. If you want to find the last version working on a stock Win2k then you should search for the last one compiled in older Visual Studio.

The software itself without the driver is useless You may try to download the drivers, unpack it, go to "Drivers", unpack "LWS_Driver_Installer_x86.exe" and try to install the driver present in "$_OUTDIR\PRO5" using Device Manager.

Thanks again, acus! As expected, no errors this time too. And as expected, the service cannot be started but I don't think I can really do anything about it. I fixed all dependencies but there must be some other problem with it. The service doesn't start in BlackWingCat's version of .NET Framework 3.5 too so I'm sure it's not something caused by this particular package.

This project has been discontinued. Please check the Unofficial SP 5.2 for Windows 2000 thread for more information.

I've uploaded a new version of netfx1011203035. I found a way to install two services which can't be installed normally (there are some incompatibilities between the installer and Win2k). I'd also like to ask you to change the test procedure a little bit: 1. Install UURollup (ENU). SP4+UR1 or USP5.1 is required before doing it. 2. Install .NET Framework. 3. Uninstall .NET Framework. 4. Reinstall .NET Framework. 5. Use .NET Framework Setup Verification Tool to check whether everything is installed correctly. 6. Open Services ("services.msc") and try to run the two services - "Net.Tcp Port Sharing Service" (you need to enable it first) and "Windows CardSpace". 7. Uninstall .NET Framework. I hope you don't mind the additional steps. UURollup is always required because .NET 3.0-3.5 need it to fix the dependencies and .NET Setup Verification Tool also won't work without it. The two services are normally added during .NET 3.0 installation but here I'm using "sc.exe" to add them manually. There's a problem with "Windows Cardspace" though. It can't be started and I guess there must be some incompatibilities with it too. I've also begun to work on .NET 4.0 but it will probably take significantly longer as there are a lot of issues to be fixed.

The file is same but M$ always puts it in uniproc too. And it's required for slipstreaming...

Uhm, not exactly Windows2000-UURollup-v10-x86-ENU.exe and Windows2000-UpdateRollup2-x86-ENU.exe can be installed manually or slipstreamed with HFSLIP. OnePiece_Windows_2000_Post-SP4_UpdatePack_v5.0.2_FINAL_ENU.7z can be integrated with nLite but do NOT unpack it. You just integrate it as it is. nLite checks for file versions to determine which files is newer. The content of the update pack and Update Rollup 2 is similar but not the same. There are more updates / hotfixes integrated in Update Rollup 2 than in the update pack. On the other hand the Update Pack covers not only system updates but also IE, MDAC, WMP and other components. That's why I included all of them in the "basic method" because they are complementary.

@Hackeronte I don't really know why the script didn't work but at least you managed to get it done At the moment you've got a list of files which are not present in your %systemroot%\system32 directory. However, some of them are present in other directories like %systemroot% or %programfiles%, etc. Could you now check the files in your system (just search for them in your %systemdrive%) and compare language of yours and the ones from UURollup? I'm talking only about these files: You can check languages in each file's properties. After that you can prepare two additional lists - one with files with the same language version and one for files with different language version. @acus, My2GirlsDad Thanks a lot for testing the .NET installer. No errors this time KB968006 is fine. I removed it from my website because bristols added it to the updates list. I probably need to state it less obliviously but the updates listed on my website are only those which are not included on the bristols' list. Some of them are not listed by bristols at all and others are available there only in English while I keep other language versions. In one word, the list is not supposed to be a replacement of the bristols' list. They are complementary. On the other hand, the complete method uses packages from many different places so that you don't need to look for them separately.

Unfortunately nLite is not capable of integrating updates that add new files to the source which means that it cannot integrate UURollup and/or Update Rollup 2. You really can't avoid using HFSLIP but if you look at the basic method described on my site you can see that you only need three (four in case of Server) files to download. It's really simple: 1. You only need to download HFSLIP together will all other tools listed in the Table 6 (except the ones for XP). 2. Download the newest version of UURollup (ENU) and Update Rollup 2 and place them in HFSLIP\HF directory. 3. Copy your Windows' source to HFSLIP\SOURCE. 4. Run HFSLIP (with default settings). 5. After it's finished run nLite on HFSLIP\SOURCESS and integrate Onepiece's Windows 2000 postSP4 Update Pack. At this point you can also integrate drivers and do all other changes in nLite. 6. Create ISO. This is basically it. You're not integrating ALL available components this way but this is the price for simplicity. Still your Windows will ~95% up to date. The only important components which are excluded are .NET Framework 3.0, 3.5 and 4.0 but you can always install them later if necessary. This is what I've been preparing but it's still a long way to go. The OnePiece's Update Pack is this kind of package but only for official components.

Actually there are way more KBs missing from Gurgelmeyer's USP 5.1 whose last version was released around summer 2006, especially if you include patches for WMP, MDAC, DX, etc. Here is a more or less accurate list of updates/HBRs included in the USP 5.1 which are still valid. You don't need to integrate them again if you use USP 5.1 but there still will be a lot of other packages to integrate/install (I'm not sure how many but probably around ~150?). The complete method described on my website is probably the simplest way to slipstream everything and it utilises USP 5.1 too. Or you can follow the "Basic method" if you want a really super easy one. The bristols' updates list (already mentioned by submix8c) is also very good but you can easily get lost in the mass of updates.