roytam1

Any chance making new Chinese(Traditional) version of Extended Kernel and Extended Core?

and also PPAPI link: http://fpdownload.macromedia.com/pub/flashplayer/latest/help/install_flash_player_ppapi.exe

blackwingcat did that. search ".net 1.1" in wlu will give you a list of .net 1.1 fixes, installable on both 2000 and XP.

KB3046306 update in April Patch Tuesday seems to be buggy. I had 2 times of system freeze after installing it.

I wonder if KDW has update for win2000 PC that is not able to apply UURollUp and extended kernel?

see this for solution: http://www.msfn.org/board/topic/173049-windowsmicrosoft-update-not-working-on-windows-2000xp2003/#entry1089383

Does win2000 support Paragon GPT Loader?

http://bearwindows.boot-land.net/scsifix.7z

harkaz, i appreciate the work that you have done.. i installed your "FIX" for the MS15-010/3013455 update, which, incidentally, took a leap of faith, since it is a modified "windows" file and it also requires installing a "certificate" for it.. with all of the talk about komodia's installing certificates etc, and with "privdog", and everything else associated with that, when you talk about installing a certificate (not to mention installing a modified windows file), it is concerning: http://arstechnica.com/security/2015/02/lenovo-pcs-ship-with-man-in-the-middle-adware-that-breaks-https-connections/ http://www.pcworld.com/article/2887632/secure-advertising-tool-privdog-compromises-https-security.html i would like to know how to remove your certificate that i installed, in case i ever want to.. does it have a name? to remove the certificate, would you simply delete the "HKEY_LOCAL_MACHINE\Software\Microsoft\SystemCertificates\Root\Certificates\F2C90A445A5E0F0F79AEDEB694D50B9656B24A71" regkey, or would deleting that regkey cause problems with other certificates? i just wanted to mention something.. looking at the screenshot that you posted, you say that "the order of command execution is reversed", but there seems to be more to it.. in your screenshot, in the code in the window on the left, it has a "@sc1_InitializeTwilightcontours@12" while the code in the window on the right doesn't, at least that is the way that it looks to me.. maybe you already noticed that, or maybe i am confused and that actually was the point that you were making.. regarding the MS15-010/3013455 update, from what you have posted, it seems that the "win32k.sys" file that was installed by the 3013455 update was flawed, and that the 3037639 update, which was meant to fix the font problem, simply tweaks windows in order to allow it to use the flawed win32k.sys file, but without the font-problems.. tweaking windows to where it can use a flawed win32k.sys file (but without the font problems) doesn't sound good to me.. from reading some of the other posts here, it seems that some people opted to tweak the win32k.sys file themselves.. i suppose that they also had to use their own certificates in order for windows to allow the modified win32k.sys file to be installed and to run.. for the record, i don't know anything about "coding" software.. i am not an "expert".. i am just a regular home-computer-user.. nope, I just modified win32.sys and replace them(in both dllcache and system32) on-the-fly right after installing original KB3013455 patch. So no cert. are needed.

I do not believe there's a similar project for Windows NT 4.0 sadly. That's one reason why I've sort of given up using it, even though I like NT 4. The only thing I know of that exists for NT4 is a transformation pack that makes NT4 look a bit like Windows Vista and the link can be found in this forum, but that just changes the looks, it won't change the functions. BWC's FCW doesn't even run on NT4 and just crashes with an error message. So someone can correct me if I'm wrong but I don't believe I am.There is a group of people playing around the leaked sources to reconstruct an usable build. http://opennt.net/?id=Home

Thanks for report. Did I misunderstood the instruction?Patch harkaz code as fixed code for all languages? Patch 55D1F : E8 F7 04 00 00 Patch 55D2A : E8 17 7E FF FF seems so.

Adjust PE checksum http://www.coderforlife.com/projects/utilities/#PEChecksum A XP at a virtual machine does boot still. Edited: Ignore this. Try you patch. A different approach, the same patch: search for 8b cb 8b d7 e8 expect address about 55D1F find e.g. E8 22 7E FF FF at 55D1F search for 8b d7 8b cb e8 expect address about 55D2A find e.g. E8 EC 04 00 00 at 55D2A Patch 55D1F : E8 EC 04 00 00 Patch 55D2A : E8 22 7E FF FF Yeah, that was exactly the result I got by doing it my way, but I didn't adjust PE checksum - after using the tool you suggested, I didn't get a BSOD anymore when booting, but the font corruption wasn't cured. So, as Dave-H said that he had to re-do the ClearType tuning, I tried this, too, by installing Microsofts Cleartype Tuner Powertoy. But then I got BSOD after BSOD, so in the end, I had to recover my imaged file :-( Has anyone an idea what did go wrong? not only copying bytes but also need offset value adjustment as http://www.msfn.org/board/topic/171814-posready-2009-updates-ported-to-windows-xp-sp3-enu/page-13#entry1095037posted.

I can't find such difference in my 6712 CHT when comparing with 6648 CHT. EDIT: oh you mean WindowsServer2003-KB3013455-x86-ENU vs WindowsServer2003-KB3037639-x86-ENU in post http://www.msfn.org/board/topic/171814-posready-2009-updates-ported-to-windows-xp-sp3-enu/page-13#entry1095037does work. thanks!

Thanks for your information. Too late for me to read this and I wasted whole day battling with it, I even opened a question in superuser. http://superuser.com/questions/876542/ugly-font-in-xp-how-can-i-restore-it/876668#876668 http://answers.microsoft.com/en-us/windows/forum/windows_xp-windows_update/kb3013455-breaks-font-smoothing/0400147f-fe2e-4d53-8b35-1a7a06962087?tm=1423669336226

Embedded KB2686509 has kblCheckerE.dll but not kblChecker.dll and it checks for HKLM\SYSTEM\CurrentControlSet\Control\ProductOptions\ProductSuite == "EmbeddedNT" as Prerequisite

IIRC POSReady has no .net 1.1 runtime installed

BTW blackwingcat had made .net 1.1 patch available to 2000/XP as well.

found another issue: patched kernel (with any hal) makes EAC can't read Virtual Drive created with Daemon Tools.

BTW I wrote another starter to auto-select most idle core for the program that requires single-core. https://mega.co.nz/#!GYlGjDCZ!VQGTLKL2Cjr6XCxI4jb2786KaynIMbJh3Sd-sDftTsM As it reads HKEY_PERFORMANCE_DATA for measuring CPU usage per core, it takes 1 second before starting program. And it keeps running for 2 seconds after starting program for setting active core again because some programs try to set itself to use Core 0 upon start.

The temporary solution would be to allow Virtual PC 2007 process to use only one processor. For instance, I used Process Explorer and right =click Virtual PC.exe, set the Processor Affinity to only use CPU 0. By setting the Processor Affinity to use only CPU 0 under Windows NT 3.51, I was able to install Windows NT 3.51 successfully. Once I close VirtualPC 2007 and restart it, VPC gets defaulted to use four cores which in retrospect that causes data corruption on the Windows NT 3.51 guest to appear. Other OSes such as MS-DOS, FreeDOS, Windows 3.0, Windows 3.1 and OS/2 Warp all work without problems. It seems to me that Windows NT 3.51 guest under Virtual PC 2007 doesn't even like multiple cores. Is there a permanent solution to overcome this issue? I'm sorry if my comment clearly didn't make since or that I wasn't being all that specific, but I'm tired and I'm heading for bed soon. Update 1: Nevermind. I solved it when I stumbled upon this article regarding running Virtual PC 2007 on multi-processor and/or multi-core processors. Have a look: http://virtuallyfun.superglobalmegacorp.com/?p=154 I've learned that operating systems such as Windows for Workgroups 3.11, Windows 95 and even Windows NT 3.51 won't work correctly leading up to long latency, disk and data corruption errors to a point where the operating system will not even boot at all. When Microsoft Virtual PC was a Connectix product it was mean to run on a single CPU or single core (up to 4.29 GHz). And now since newer computers with multi-core processors are replacing older computers with single core processors, the fix would be to set the Virtual PC.exe CPU affinity to a single core before any virtual machines are started. Now to overcome this limitation, I downloaded a utility called Start Affinity. It can be found on this page: http://www.adsciengineering.com/StartAffinity/ StartAffinity is a freeware tool that is designed to start software by restricting it to certain CPU affinity masks. Since Virtual PC is not designed for multi-processor/multi-core computers, I had to enter this command to make sure Virtual PC 2007 always starts on CPU processor 0: I hope that that setting the CPU affinity to use only core 0 solves the data corruption/failed installation of Windows NT 3.51. Update 2: For some reason, StartAffinity shows the command prompt window for a brief moment upon starting Microsoft Virtual PC 2007 with only Core 0 enabled. To get rid of the command prompt window, I had to modify the shortcut properties and add this line: By using HStart with the /noconsole and /idle switches, HStart will make StartAffinity start without the command prompt window and lower the CPU priority to idle status. The Hidden Start utility can be found on this page: http://www.ntwind.com/software/hstart.html If there are any questions regarding this thread, let me know. I recompiled StartAffinity with TinyCC and have no-console flag set. https://mega.co.nz/#!6cdRRCLQ!YfIM2F4j4DHPgglfuwZcuEVOLTIwp7LqJNgFYvJfW-g

I'm home now and tested new hal patch with exact environment with the procedure that caused BSoD before.And test passed. although the hal.dll is patched, the rtenicxp.sys is updated to latest version, it is still crashed.

1.alter's uniata driver may work. see http://www.betaarchive.com/forum/viewtopic.php?f=61&p=332204#p332204 2.3rd party USB 1.1 driver available 3.some old 802.11b adapter has NT4 driver 5.isn't MS released an update for AGP? more info: http://bearwindows.boot-land.net/winnt4.htm

I'm home now and tested new hal patch with exact environment with the procedure that caused BSoD before. And test passed.

BTW for those using USB WebCam with 4GB/64GB patch, it is better to replace usbvideo.sys from 2K3 SP2.

I haven't test "new" hal patch on the system that can crash(I have the patch from you running on the machine in $workplace, but since it is not using Realtek NIC I don't know how to crash it)