tomasz86

Strange... Does it happen with ALL msi packages or only with that particular one (Windows Defender)? I don't have any problems with running .msi packages here. Could you check if you can start "Windows Installer" service manually (services.msc)? I checked this Windows Defender, and first of all if you try to run it on Windows 2000 you see this: and after editing the installer with Orca it seems to work OK: EDIT Indeed there seems to be something wrong. I need to do more tests.

piotrhn, Please check #288. Run "msiexec /regserver" to fix this problem (or install v2 of Windows Installer 4.5).

I have good news. The v1-early-c2 works perfectly. --- I also fixed a bug in Windows Installer 4.5 which prevented Windows Installer service from being started. In case you've already installed v1 you should run from command prompt "msiexec /regserver" to make it work properly. It's now available in two versions. Windows2000-WindowsInstaller45-v2-x86-Global.exe (This version cannot be slipstreamed!) Windows2000-WindowsInstaller45-v2-x86-Global-HFSLIP.exe (This version can be slipstreamed using HFSLIP from HFGUIRUNONCE folder.) The first one is just a standard MS update format which cannot be slipstreamed. The other one is a switchless installer version which must be run after Windows has started. It won't work when run in T-13.

I know I'm just complaining at MS for not using the standard format. Is it really that difficult? Well, my post was a kind of an informative one. .NET Framework updates can't be processed by HFSLIP directly (you need to use a switchless installer or an addon). I keep a full list of .NET Framework 1.1/2.0 updates (link in my signature).

That's the point. I've had this problem when patching directly and no problem on a VM with a slipstreamed CD (the same Win2k Advanced Server). It may be important that VirtualBox I'm running recognises only 1 core though. I'll try to do a test using different edition of 2K. I'll also try to install the patch on my laptop (P3-M 933MHz) to see if this issue is limited only to my desktop PC or not. Thanks for help anyway I'll try to post the results as soon as possible.

It's still the same No difference.

Today's update: - KB2416447 replaced by KB2572067 (.NET 1.1) - KB2572073 added (.NET 2.0)

I have an Athlon II X2 so 2 cores Today I'm going to try your patch on a different configuration (but using the same slipstreamed Windows CD) and see if there are any problems or not. By "cpu patch" do you mean the patch to enable more cores on Windows 2000 Professional system? Can it be a problem that I use Windows 2000 Advanced Server which by default can use up to 8 CPUs/cores? I'd be very happy to test the patch for you

What I did was to try installing your patch without bootvid (by disabling it in update.inf) but after doing so there's an error on boot. I don't remember exactly what it said but it was just something about being unable to boot because of the non-patched bootvid.dll. In order to boot again I had to replace bootvid.dll manually with your version and after doing so I could boot to Safe Mode and uninstall the patch. Actually at this moment I still have your bootvid.dll installed without the rest of files from your patch. It probably rules out bootvid.dll as a cause of this problem

http://technet.microsoft.com/en-us/security/bulletin/ms11-oct As always MS messed someting up 1. Windows-en-US-KB2564958.exe <- What's this? Why using such a non-standard filename? 2. .NET Framework 2.0 update KB2572073 is said to replace KBKB983583... but KB983583 had already been replaced by KB2446704. EDIT After short checking I can say that indeed KB2572073 does not replace KB2446704 as mscorjit.dll is not included so you need both KB2446704 & KB2572073.

1. The problem occurs right after installing MS11-011 only. 2. Multiprocessor kernel. Switching PAE on and off doesn't make any difference. Neither does /3GB. I have both of them switched off at the moment. I also have another HDD connected to the build-in SATA controller which uses this SATA/RAID driver. It's for storage only, system itself is installed on the former one.

Could you be more specific? Which updates are you talking about? WildBill, I did more tests and actually I was totally wrong and mislead by the bootlog created when logging to Safe Mode. This problem occurs before even bootlog is created. I have enabled /SOS in boot.ini and the exact moment when monitor goes off is after acpitabl.dat is loaded. This screen doesn't show up at all. I looked for it in Google and what I found out is that it may be related to HDD controller driver which can't be loaded. This is the driver I use.

WildBill, I was busy so I couldn't check all of these kernel versions and WinCap driver but I'll do all necessary tests and post results in short time.

PROBLEMCHYLD, It's not a bug, it's just how HFSLIP is constructed. By newer files I meant the date, not version. HFSLIP doesn't check file versions. WildBill, I'll try with kernel v2 but there are no problems with v5. The problem occurs only after I install your kernel patch

KB2616676-V2 - it's OK as the update only adds fixes to the registry KB896081 - just my guess but probably HFSLIP copies Msv1_0.dll from 960859 instead of the one from this one KB904765 - don't know now but I'll check it KB907868 - newer kerberos.dll in WildBill's KB2508429 KB908506 - I'll check it KB935839 - you mustn't use this one if you use WildBill's kernel patch KB942831 - newer infocomm.dll gets copied from KB2290570 KB981852 - newer files included in WildBill's patch KB982214 - same as above

No problem I've forgotten about KB816868. It's obsolete. The file inside it is WININET.DLL 6.0.2800.1193 and the latest available version is WININET.DLL 6.0.2800.1649 (I don't know now in which update it's included by it's definitely newer than the one from KB816868). EDIT Yes, you shouldn't (=don't need to) install Windows Installer 3.1 because Windows Installer 4.5 replaces it. To be more specific, the replaced updates are: KB893803-v2, 927891 & 968006.

Remote Desktop is fine. That's why you need to put in into HFSVCPACK_SW1. That's the only way to get it installed to the correct folder ("%ProgramFiles%\Remote Desktop"). Otherwise if placed in HF the files will get copied to system32 I could make it work from system32 but I think it's better to stick to the default folder. KB829884 - there's something wrong with the header. I guess it'd be the best if WildBill could have a look at it (if he has some time). Modifype -c doesn't work in this case and there's still an error when copying files during text setup. KB896414 - It's not possible as the file itself causes several problems when replaced directly in i386 folder. (check this topic)

I prepared a few new updates: - Microsoft Remote Desktop 5.2 for Windows 2000/XP/2003 (goes to HFSVCPACK_SW1) - Windows Installer 4.5 for Windows 2000 (goes to HFGUIRUNONCE); WildBill's KBz2360937 & KB2393802 required. - KB906569 (msconfig.exe update) - KB950305 (UniDriver fix) - KB954193 (MS Jet 4.0 fix) and also added WildBill's updates to the list: - KB2360937 - new function added to rpcrt4.dll - KB2393802 - WildBill's kernel patch; many new functions added - KB2508429 - SMB Server fix; many new functions added Details here.

I had a 16 year old model M too but it died because of a thunder storm I've never used a computer anymore since then when there's a storm outside

Yes, you shouldn't use "WINDOWS" as: 1. Some users may have different Windows folder's name. 2. It's "WINNT" for Windows 2000

Of course there are still 4:3 (5:4) LCD monitors available but they are generally directed towards more professional users (see Eizo for example). And they are much more expensive than the commonly used cheap stuff but worth it. I'm not a specialist on monitors but generally if you're concerned about quality you should go for VA or IPS instead of TN (simple comparison ). On the other hand if gaming is your priority you may consider buying a 120 hz TN panel which will be faster than any VA/IPS one.I use a Diamondtron CRT and there still won't be many LCD panels which are comparable in terms of quality / colour display, except the expensive ones designed for graphic designers. It's the same as everywhere - good quality is expensive Still you should check some reviews because there are some interesting monitors even among the cheaper one although the majority of the cheap stuff won't be better in terms of display quality than a used 50$ CRT.

This is after cdfs.sys. I checked what it is and npf.sys seems to be related to WinCap which I use. I'll try to uninstall it and see what happens then.

Oops, what I meant was boot screen When progress bar goes 100%, boot screen disappears and Windows should start but it doesn't. Monitor just goes off and nothing happens, and I need to do a hard reset to be able to start Windows in Safe Mode. At this point Event Viewer doesn't record anything yet. EDIT I enabled bootlog in boot.ini and it seems that the problem happens here: It just hangs at this point. The driver itself is related to CD-ROM but I don't have any CD/DVD devices connected to the computer at the moment.

WildBill, Thanks a lot for all of this Would it be possible either to update this post and update the list with the newer changes you've made or maybe you could add them to the 3rd post (where the list of updates is located) so it'd be easier to navigate and have everything in a one place. I'll try to check different applications and see what works and what does not. Actually I've experienced a problem with your patch. When I install it in my running system, it doesn't start after reboot - the monitor shuts down after the login screen disappears and Windows doesn't boot. In the beginning I thought that it was related to BlackWingCat's kernel v5 but it's the same even with the v2 of your patch. Even though all of the files got copied correctly, the problem still persists. I can boot to Safe Mode and after uninstalling the patches I can boot normally again. On the other hand, I did many tests on a VM with a slipstreamed CD including your patches and everything works fine

Skype 5.3.0.111 is the last version of Skype to work under Win2k. BlackWingCat's kernel v5 (or higher) or WildBill's kernel patch (MS11-011) is required. Thanks to BlackWingCat for this information.