tomasz86

I've been updating the Download Archive at my website. I've added several XP and 2003 updates, and I'm going to remove the obsolete updates from the Windows 2000 folder and add the new ones released in the last few months. Please let me know if you find any errors.

That's right Feel free to change the lines according to #17. After that you shall be able to integrate it, no matter what the host OS is.

Give the SFCFILES.DLL you can extract from this package a try. Thanks! I'll have a look at it but first I'm going to try disabling SFC through the registry using this method:

By the way, I've been always wondering what's the reason for this: IF "%HostOS%"=="XP" IF EXIST HF\WindowsXP-KB942288-*-x86.exe CALL :MSI45 XP sp3qfe IF "%HostOS%"=="2003" IF EXIST HF\WindowsServer2003-KB942288-*-x86.exe CALL :MSI45 Server2003 sp2qfe I can't really see any reason why you shouldn't be able to integrate MSI 4.5 into XP source when running HFSLIP under Windows 2000 or 2003 (and otherwise). This is still experimental but I'd suggest trying to change the two lines to: IF "%VERSION%"=="XP" IF EXIST HF\WindowsXP-KB942288-*-x86.exe CALL :MSI45 XP sp3qfe IF "%VERSION%"=="2003" IF EXIST HF\WindowsServer2003-KB942288-*-x86.exe CALL :MSI45 Server2003 sp2qfe Edit: Fixed the modified code.

Does anyone know about a Windows 8 theme which looks similar to the Windows Classic theme from Windows 7? The high contrast themes are out of question since they change colours not only in Windows Explorer but also in IE which makes it unusable... I'm thinking about something close to the Classic AE theme for Windows 7: Does there exist anything similar for Windows 8?

It's a known problem - Google for "uurollup sfc". In one word, SFC.DLL is responsible for Windows File Protection and UURollup disables it by patching the file. Avast thinks the modified file is malicious. At the moment you should just ignore the warning. I'm working on a different solution to disable WFP without patching the DLL (more about SFC.DLL here). As for Avast and problems on a clean Windows 2000 installation... Avast requires Windows 2000 SP4 + IE6 + Update Rollup 1. SP4 + UR1 is not enough. You need to install IE6 too as Avast won't work with IE5.5.

Why do you think that "/n" stands for "/norestart"? This is Microsoft "/n" stands for "/nobackup" while it's "/z" to mean "/norestart". http://support.microsoft.com/kb/262841 These short switches are actually better because they work both for new and even very old updates.

I've just uploaded a new daily release of UURollup-v11. As said before, the newest BWC kernel is included in it. I've also added some fonts.

You can use: Avast 8 - the newest version works in Windows 2000. Just make sure to do a custom installation and disable the Software Updater (details here) Malware Defender - you can download it from my website. It's probably the most recent software firewall working in Windows 2000. It scored decent in the tests.

blackwingcat has released an updated version of his kernel so you can expect a new release of UURollup-v11 soon. I'm also working on a new merged .NET Framework installer. This time I want to make sure that it works correctly both in 2000, XP and 2003, and also that Windows Update doesn't ask for the updates which have been already integrated there.

The fix which I mentioned above is the only significant difference between my version of the script and the one from Mim0. Once the fix has been implemented, there's no need to have a separate 2K branch.

Thanks Have you tested the script with Windows 2000 and 2003 too, just to be sure that everything works all right? If possible I'd like to ask for implementing also this fix.

Hey everyone I'm sorry for being absent for some time. I've been very busy and things have been a little bit difficult for me recently so at the moment I've got very little time for Windows 2000 and MSFN. I hope to be able to fully come back in the near future. @Tommy There're some issues with UURollup uninstallation. I worked on it already two months ago and I'm going to improve the situation later on. The problem occurs when you've installed several versions of UURollup without uninstalling the previous one, and then try to uninstall it. Simply speaking, the uninstaller unregisters several system files and doesn't register them again. @marcdw I can't really help you the SQL problem at the moment. I'd need to install and test it myself. I'll remember about the issue and try to do something in the future. @Svyatpro They can be registered as long as you've installed UURollup-v11.

Just in case you still need it: Guide to Installing and Updating Windows 2000 Professional

Firefox 13+ in Windows 2000 Alternatively you can just install the newest daily version of UURollup-v11 and then everything should work out of the box.

You're right but in Opera you can still open a different website in that tab by typing an address while it doesn't seem to be possible in Chrome.

Is this directed at me? I'm still alive just a little bit busy

What happens if you install MS RDP 5.2 in XP SP2 first and then update to SP3? Does SP3 still install the newer version then?

I see. I suppose that there's no easy fix for this, right? The JavaScript bug does not exist in the new Opera Next 15 (which is based on Chromium).

KB956744 is part of MS09-044. KB2481109 is part of MS11-017. M$ says that MS11-017 does replace MS09-044 but only in case of MS RDP 5.2.

That's what I've been doing... As for GDR/QFE, the script uses only QFE files. The main difference between an update rollup and a service pack is that service packs are cumulative meaning that all previous service packs are included in the newest one, and also that service packs support the "/integrate" switch so you can slipstream them directly without using any 3rd party tools. As a person who prepares such a service pack you've got full control of the whole process. There's also a structural difference between them - if you unpack a service pack you'll see that everything is located in the "i386" folder and that some some files are packed to CAB (*.*_) and the others aren't (same as on Windows CD). Update rollups are just compilations of updates and their structure is same as single updates.

The test file had more than one spaces together I'm sorry As long a there are only single spaces together in filenames then the scripts seem to work fine. Thank you for help anyway. As for the end goal, it's to have a script which can: 1) Merge updates / files into an update rollup. 2) Add updates / files to a service pack. The point 1) is finished in the most part. The point 2) not yet. At this moment I'm probably able to finish it completely by myself but many of my own scripts are very inefficient so I've been working on performance improvements recently. That's why I've been asking those specific questions.

@Yzöwl Unfortunately your script from #230 also doesn't work with filenames with spaces Only the fist token is displayed. I've come back to my original concept: @ECHO OFF SETLOCAL ENABLEDELAYEDEXPANSION FOR /R test1 %%A IN (*.*_) DO CALL :Cabarc "%%A" :Cabarc SET File= FOR /F "skip=9 tokens=*" %%A IN ('cabarc l %1') DO SET Line=%%A SET tokens1=1 :loop FOR /F "tokens=%tokens1%" %%A IN ("%Line%") DO ( SET Line=!Line:%%A=%%A/! SET/A tokens1+=1 GOTO :loop ) SET/A tokens1-=3 SET tokens2=1 :loop2 FOR /F "tokens=%tokens2%-%tokens1% delims=/" %%A IN ("%Line%") DO ( SET File=%File%%%A SET/A tokens2+=1 GOTO :loop2 ) ECHO "%File%" GOTO :EOF :EOF The script is still unpolished but seems to work regardless of how many spaces are in the filename. It took 1m 16s to process the same set of files so for me it's acceptable.

It took 0m 56s Actually the speed does matter since such a list is going to be created each time I run the script. I don't want to create any lists in advance since it would have to be done for all language versions of each Service Pack. Also such a list would be invalid in case you want to update a service pack which has already been updated in the past. 100% true. I don't know what approach to choose yet. Maybe I should just assume that there are no spaces in filenames inside CABs and run "cabarc -L" without any subroutines... Hmm but then the problem is that you'll have to repack all of them again after the files have been updated. This was actually the method which I originally tried to use but it got kind of complicated since it was necessary to store information of both the original cabbed filename and the unpacked version of it. It also required a lot of disk space. Anyway, thank you for all the ideas. I need some time to think about it and test the different scripts.

I know that it's only about reading the contents, not the actual extraction. Still, "expand.exe -D" is still very slow. To process 2674 cabbed files from XP SP3 it takes: Expand.exe 6.1.7600.16385 FOR /R test1 %%A IN (*.*_) DO ( FOR /F "skip=2 tokens=3* delims=:" %%B IN ('EXPAND -D "%%A"') DO ( ECHO %%B ) ) Time: 6m 17s Cabarc.exe 6.2.9200.16438 FOR /R test1 %%A IN (*.*_) DO ( FOR /F "skip=9" %%B IN ('cabarc l "%%A"') DO ( ECHO %%B ) ) Time: 0m 51s "Cabarc L" is more than 7 times faster than "Expand -D". I want to list all files from a Service Pack in order to update them later. At first I thought about just extracting all of them but the problem is that there many files which share same filenames (once extracted).