Leaderboard

OK, I have jush finished to test PatchPE 1.30 (why not version 1.31, see below) with hexdump for Windows https://www.di-mgt.com.au/hexdump-for-windows.html By default, hexdump doesn't works on XP: So, I have patched hexdump with PatchPE 1.30 and that's works : I have used version 1.30 because version 1.31 doesn't works on XP ! BUT, if you want, you can patch PatchPE 1.31 with PatchPE 1.30 and it will works again on XP : There is only one disavantage with the version 1.31, now PatchPE need a computer that's support SSE2. It is not the case with the version 1.30. It seems that PatchPE can be useful in some situations.

In this topic I'll post my modified drivers for Windows 2000 with SP4 (no Updates Rollup or Extended Kernel needed). For testing purposes only, so beware. If considered stable, will be promoted to Final. - Intel Matrix Storage 7.6.9.1002 (AHCI/RAID) Driver only: Win2000_7.6.9.1002_DriverOnly.7z Complete package: Win2000_7.6.9.1002_Complete.7z This one is slightly newer than BWC's 7.6.0.1011, with a few fixes. - AMD(Hudson?) / Intel / VIA XHCI USB3.1 driver 1.1.0.0276 Driver only: 276BETA_W2K.7z Has the same issues with PAE as XP. Don't know if Windows 2000 is also affected by qword ACPI issue (the XHCI controller won't initialize and reports Error code 10). In this case, please try it in MPS Uniprocessor/Multiprocessor mode.

- Installed Windows 2000 SP4 (with drivers integrated) in MPS Multiprocessor mode (ACPI doesn't work here) on VirtualBox. - Followed the instructions in this question: exporting a virtualbox VDI to a harddrive to boot it natively - Plugged in a PS/2 keyboard, booted Windows 2000 and proceeded with all driver installs. - Used the Composite devices solution outlined here: Universal Serial Bus (USB) Interface drivers (scroll down) - And the result is: Driver works fine with both Intel and VIA controllers.

I set it to - monthly 2019-12 to 2019-12 - and I get 1.16%

I now see it at 2.25%, so we're above Linux and Mac OS 10.13! The numbers in the table seem to update constantly, and show Windows 7 at 33.1% when the December share is stated as 26.6%. I'd like to say that business PCs are considerably more likely to have Windows XP and 7 than home PCs, but it's New Year's Day. I wouldn't think that many people are working today.

The new year (and decade) has just arrived in UTC -05:00 (eastern continental United States as well as Ontario, Quebec and eastern Nunavut in Canada*) I am pleased to report that there doesn't seem to be an undocumented "2020 bug" in Microsoft Windows. My Windows 95, Server 2003, Vista and 8.1 installs have successfully entered a new decade. And no mass failures of XP either it appears. *Not including northwestern Ontario communities such as Kenora and Quebec's Magalden Islands in the Gulf of St. Lawrence

I suppose I could try yet again from another PC, but registering for that site is just a ridiculous amount of trouble for a hack that does little but save me from going to the M$ Update Catalog once a month. They even seemed to not like my passwords because they were too random! Besides, I'm sure this forum will soon have its own @Bersaglio who posts links to the new updates every Patch Tuesday.

What about Jan 01, 1970?

yes I've edited my precedent post with these very shortened proposals ....

So I've read it like 3 times and ignored "November" in title? Shame on me.

Not the point. Opinion in instructions lacks professionalism.

In the text file which comes with OldNewExplorer it would be best if @Tihiy leave out his personal comments. Whether or not you like dark mode @Tihiy is not relevant, and your included opinion is not necessary.

I finally managed to get also new versions of Basilisk work on windows NT 4.0 with my kernelex, now they work new versions of firefox too (up to 52.0 for now). The first release of my kernelex will be on the first term of July. Be patient, I'm working hard to get newer software and drivers working on it :)