Search the Community
Showing results for tags 'Windows 2000'.
The search index is currently processing. Current results may not be complete.
Found 14 results
-
Hello Windows 2000 fans, a while ago when WildBill was backporting security updates from Windows XP to Windows 2000 he noticed a flaw in Microsoft's implementation of the security fix in the function "_SetWindowWord". By now Microsoft released an update for Windows 2000 to fix the security problem so WildBill's backported version has been superseded. However, the flaw still exists in the newest versions of win32k.sys from Microsoft both in Windows 2000 and in Windows XP. The flaw causes problems in some applications which try to deal with their graphical user interface. In an extreme case it can cause the bluescreen "WINLOGON_FATAL_ERROR". The flaw has a pretty small security impact. There is an update available to fix the flaw: WINDOWS2000-OTSKB000004-V1-X86-INTL.exe Since the newest version from Microsoft contains the security fix already, this update fixes the flaw only. It's all that was left to do. There is more information available about this issue and this update in the article in the knowledge database: OTSKB.chm The patch updates the file "win32k.sys" from the version "5.00.2196.0004" to the version "5.00.2196.0005". Special thanks go to @dencorso for reporting the bluescreen "WINLOGON_FATAL_ERROR" (0xC000021A) in Windows XP and narrowing down the problem to the Windows update "Windows XP (32 bits)/KB981957" and @WildBill for further narrowing down the problem to the function "_SetWindowWord" and to the exact machine instruction within the function. -
Hello Windows 2000 fans, I noticed that there is another bug in the function "CreateXlateObject" in the file "win32k.sys". The execution order of 3 loops is incorrect which leads to the situation, that the static colors in a translation table (Xlate-object) is stored in the table but then are overwritten by dynamic colors directly afterwards. There is an update available to fix this problem: WINDOWS2000-OTSKB000003-V1-X86-INTL.exe There is more information available about this issue and this update in the article in the knowledge database: OTSKB.chm The patch updates the file "win32k.sys" from the version "5.00.2196.0003" to the version "5.00.2196.0004".
-
Hello Windows 2000 fans, by chance I noticed that there is a bug in the function "bMakeXlate" of the class "EXLATEOBJ" in the file "win32k.sys". The initialization of XLATE data structures doesn't fill out all fields. Some fields remain uninitialized and therefore keep their random data which they received during the memory allocation. This can lead to unexpected and unwanted behaviour of functions which read the random values from the affected fields. There is an update available to fix this problem: WINDOWS2000-OTSKB000002-V2-X86-INTL.exe There is more information available about this issue and this update in the article in the knowledge database: OTSKB.chm The patch updates the file "win32k.sys" from the version "5.00.2196.0002" to the version "5.00.2196.0003".
-
Hello Windows 2000 fans, when using vanilla Windows 2000 with a rather new version of win32k.sys, there is a bug in the function "fsg_RunPreProgram" which reduces that drawing quality of some fonts. This bug was fixed with the version 5.00.2195.7610 by Microsoft. However, it was reintroduced into the operating system shortly afterwards, so it still exists in the newest version of win32k.sys (5.00.2195.7640). To fix this bug there are 2 ways: Use Extended Kernel 3.1H or newer. Blackwingcat fixed this bug. If you don't like or can't install Extended Kernel, there is now a second option available: WINDOWS2000-OTSKB3037639-V1-X86-INTL.exe There is an article in the knowledge database available with more information on the nature of this bug. There is some more auxilliary information available, which I do not plan to distribute among end users: code.htm The patch updates the file "win32k.sys" from the version "5.00.2196.0001" to the version "5.00.2196.0002". --- If someone likes to help with an upcoming Windows 2000 update: I am looking for Windows XP updates which contain a version of win32k.sys. My list of known updates is currently pretty short: KB3013455 contains version 5.1.2600.6712 KB3034344 contains version 5.1.2600.6755 KB4039384 contains version 5.1.2600.7334 Thank you.
-
Hello Windows 2000/XP/Embedded fans, while I was working on a graphics driver, I noticed random crashes (blue screens) which were hard to reproduce. They don't happen often, but when using a display mode with 16 colors (for example 640x480x16 colors) they seem to happen more often than with other color depths. Eventually I was able to narrow down the problem and came to the conclusion, that the root cause is a buffer overrun in the function "CreateXlateObject" in the file "win32k.sys". This buffer overrun sometimes caused a random crash. In the most cases it happened within win32k.sys. I observed, that this issue is not fixed even in the newest version of win32k.sys from a Windows 2000 update from April 2016. An old version of win32k.sys from Windows XP has the same problem. I don't know which Windows XP update contains the newest version of win32k.sys for Windows XP, so I could not validate whether this issue was ever fixed - and if so: how. So I thought about what to do and came up with the idea, to write a Windows update of my own to fix this bug. So far I gathered necessary information and wrote a help file which contains most of what I know about the nature of this issue and how it can be fixed: OTSKB.chm There is some more auxilliary information available, which I do not plan to distribute among end users: code.htm Eventually, I fixed the win32k.sys from Windows 2000 manually with a hex editor to test the proposed solution: 5.00.2196.0001.zip The update, which would do this automatically and then install the new file automatically, is not written, yet. I would appreciate some feedback before I continue writing the update. Please let me know what you think. Maybe I just got it all wrong, don't know. Edit: The title has been changed from "request for comment" to "looking for a beta tester". Edit: The title has been changed from "looking for a beta tester" to "released". Edit: If you don't want to read everything but only grab the released files: OTSKB.chm (if you like a newer version than the one that is included in the update) WINDOWS2000-OTSKB000001-V8-X86-INTL.exe (for Windows 2000) WINDOWSXP-OTSKB000001-V3-X86-INTL.exe (for Windows XP (32 bits)) WINDOWSXP-OTSKB000001-V3-X86-EMBEDDED-INTL.exe (for Windows Embedded for Point of Service (32 bits)) The patch for Windows 2000 updates the file "win32k.sys" from the version "5.00.2195.7640" to the version "5.00.2196.0001".
-
Hello, I want to recreate the Microsoft Windows Update v3/v4/v5 sites in local with all the elements. I know the Wayback Machine Downloader to do this but I can't find any pages of this site on web.archive.org. So, can you help me doing that project? Note: this is a public project, anyone can participate, but pls, don't share other Windows Update sites than v3, v4, v5 or v6.
-
This is a new project I am working on—Windows 2000 installation with NT6 setup. This is a prototype version of the project. Supposed to be the Windows 2000 equivalent to XP2ESD. Hopefully this will eventually make it easier to install Windows 2000 and older NT versions on modern hardware by bypassing the textmode phase. I have successfully installed this on my Dell Latitude 5490
-
Hi, I am wanting to install Windows 2000 on a Dell Latitude 5490, a Kaby Lake machine. I've installed XP with XP2ESD 1.7 by @George King, and Windows Vista and Windows 7 on that laptop. And before anyone says it, no, I am not going to use a VM. And also, the legacy internal boot wouldn't be a problem, as even though it isn't supported, I can use something like WinSetupfromUSB to get around it as legacy external boot is supported. What would I need to do to get 2000 running on the Dell? The laptop has no CD drive, so I would have to install with USB. I have a SATA m2 SSD and USB 3.0. Also, @George King ported the Windows 8 drivers to Windows XP for AHCI and USB 3.0 in the XP2ESD pack, would they work on 2000? And how would I get ACPI working on 2000? -
Hello everyone, We’re excited to share a major milestone from the Win2000_dev_community — we've successfully ported ACPI 2.0/NTOSKRNL Emu_Extender support to Windows 2000! 🎉 This achievement was made possible thanks to the incredible work of @Damnation, along with valuable assistance from Rairii, and valuable contributions from others in the community in testing and debugging issues along the way. ✅ As of now, the following are fully working on Windows 2000: Windows 7's NVMe driver Windows 8's USB3 driver Windows 8’s STORAHCI driver Windows 7's Storport.sys KMDF 1.11 support ⚠️ Known Issues: processr.sys does not function correctly due to differences in CPU throttling mechanisms between Windows 2000 and XP. ▸ This may be caused by the lack of PROCESSOR_STATE_HANDLER2 in Windows 2000 kernel, which only implements PROCESSOR_STATE_HANDLER. InsydeH2O BIOS is not fully tested yet. Currently, it still presents problems at the "Setup is starting Windows 2000" phase. -
A while ago I found this driver to work with exFAT partitions in Windows 2000 vanilla but it didn't work for me. https://web.archive.org/web/20130808055452/http://www.merawindows.com/Forums/tabid/324/forumid/15/postid/35485/scope/posts/Default.aspx I even tried using the Windows XP driver dlls but I still couldn't read exFAT partitions. Right now if I connect an external USB hard disk with an exFAT partition then Windows 2000 won't boot, nothing happens it just keeps trying to boot. If I connect the hard disk after Windows 2000 has booted then other partitions can be accessed. Do you know of any way to read exFAT partitions in Windows 2000 vanilla? Thanks
-
How would I go about getting USB 2.0 to work on Windows 2000? I do not possess a PS/2 Keyboard and the keyboard and mouse does not appear to work after the "Setup is starting Windows 2000" phase of the setup, my PC specifications are here: https://valid.x86.fr/jqvha7
-
Tutorial: VirtualBox 1.6.6 On Windows 2000 (Without Updates/Extended Kernel)
Guest posted a topic in Windows 2000/2003/NT4
You will need: Orca MSI Editor Windows 2000 (for obvious reasons) VirtualBox 1.6.6 (also for obvious reasons) Note: This was done on Service Pack 4. 1. Download and install Orca. 2. Right click on the VirtualBox MSI file, Then select "Open With Orca" 2a. Make sure you have unchecked "Read Only" In Properties 3. Select the "LaunchCondition" Table, Then right click then "Drop Table" 4. After Dropping the table, Save it then install Virtualbox. 4a. Make sure you close Orca. Everything Works! If this doesn't work, try change the VersionNT=500 to VersionNT=400 I'm Assuming they blocked Windows 2000 so people would switch to XP.
-
Hi there! I have managed to get Virtual PC 2007 SP1 (6.0.192) working on Windows 2000 with the help of this tutorial by Gabrielustuca: https://www.betaarchive.com/forum/viewtopic.php?t=26980 But what I'm stumped around here is that Virtual PC 2007 SP1 with KB958162.msp (6.0.210) can't be run at all on Windows 2000 due to a missing function, CancelIPChangeNotify in IPHLPAPI.DLL. The current version of IPHLPAPI.DLL is locked by the Windows 2000 OS. Here's the forum thread regarding VPC2007 SP1 + KB958162 rollup: https://www.betaarchive.com/forum/viewtopic.php?t=31220 I'm looking for the IPHLPAPI.DLL file that comes from Blackwingcat's KernelEx v15 that is fully compatible with Windows 2000. If you have a version of the modified IPHLPAPI.DLL file, please let me know. Also, is it possible to modify the KB958162.msp file so that it will work with Virtual PC 2007 when run under Windows 2000? Thanks for your time. -
So, I've been trying out a older version of Process Hacker, version 1.11 under Windows 2000 and when I try to run it, I get these error messages: "An unhandled exception has occurred in Process Hacker. Please report the error to the Process Hacker team via bug tracker at SourceForge by clicking Send Report. You will receive a tracker item for keeping track of its resolution status." Here is the output error that I have received: System.NullReferenceException: Object reference not set to an instance of an object. at ProcessHacker.ProcessTree.GetProcessColor(ProcessItem p) at ProcessHacker.ProcessTree.<>c__DisplayClass9.<provider_DictionaryAdded>b__7() at System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry tme) at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj) at System.Threading.ExecutionContext.runTryCode(Object userData) at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme) at System.Windows.Forms.Control.InvokeMarshaledCallbacks() DIAGNOSTIC INFORMATION Process Hacker 1.11.0.0 Process Hacker Build Time: 01/24/2010 08:38:54 CLR Version: 2.0.50727.3053 OS Version: Microsoft Windows NT 5.0.2195 Service Pack 4 (32-bit) Elevation: Full Working set: 20.57 MB Settings file: C:\Documents and Settings\ppgrainbow\Application Data\Process Hacker\settings.xml KProcessHacker: not running OBJECTS Live: 13 Created: 71 Freed: 58 Disposed: 56 Finalized: 2 Referenced: 0 Dereferenced: 0 PRIVATE HEAP Address: 0x36b0000 Live: 2 Allocated: 54 Freed: 52 Reallocated: 0 MISCELLANEOUS COUNTERS LSA lookup policy handle misses: 1 PROCESS HACKER THREAD POOL Worker thread maximum: 2 Worker thread minimum: 0 Busy worker threads: 0 Total worker threads: 0 Queued work items: 0 CLR THREAD POOL Worker threads: 0 current, 2 max, 1 min I/O completion threads: 0 current, 2 max, 1 min PRIMARY SHARED THREAD PROVIDER Count: 3 ProcessHacker.ServiceProvider (Enabled: False, Busy: False) ProcessHacker.NetworkProvider (Enabled: False, Busy: False) SECONDARY SHARED THREAD PROVIDER Count: 0 WINDOWS MemoryEditors: 0, 0 PEWindows: 0, 0 PWindows: 0, 0 ResultsWindows: 0, 0 As far as I know, ProcessHacker v1.7 works on Windows 2000. I tried to get it to work, but got the same error. Has anyone tested older versions of ProcessHacker to see if it works on Windows 2000 or not. Is there any idea how this can be fixed? Thank you for your time.
