Leaderboard

Release: https://github.com/LordOfMice/Tools/blob/master/nvme9x.zip https://github.com/LordOfMice/Tools/blob/master/nvment.zip https://github.com/LordOfMice/Tools/blob/master/nvme2k-src.zip readme: NVMe driver for Windows 9x. Base: nvme2k 1.0.0.2 https://github.com/techomancer/nvme2k Changes: Port for Windows 9x, 64-bit LBA & Fixes 1. Generic - added SCSI 64-bit LBA commands processing (large drives support). Tested on Windows 9x ONLY - fixed controler shutdown code - speed up of command queueing and it is less CPU consuming - fixed enormously low speed or false positive errors on executing of large size requests - various code rectifications 2. Windows 9x specific - port with 2 bug fixes - install script nvme9x.inf written Install and uninstall as usual hardware, nothing specific.

fileextd.dll its a old rare file that provide some functions that xp useally dont have - it can be seen as kernel extender i dont know its origin either some say its from the xbox and a official file while other say its a handmade file by someone maybe we get some more information about it what i know is that it is shown as used library on microsofts website: https://learn.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-getfileinformationbyhandleex then "Kernel32.lib; FileExtd.lib on Windows Server 2003 and Windows XP"

I am on GitHub. But... You won't like this answer. I technically no longer subscribe to "keep XP alive" or "keep 7 alive". The endeavor is a great endeavor, don't get me wrong. But what we end up with instead is spoon-feeding a sect of society that *CAN* afford a newer mode of internetting (and most even confess HAVING NEWER) but think that they are somehow "entitled" to the rest of the world keeping their XP or 7 capable of "everything".

I cannot reply in your Russian forum but you are mistaken regarding IFSMGR.VXD 2227, it was Q301540.EXE and not 302540. How can you ignore it!

I still build on XP the old fashioned way: python -m pip install -U "setuptools>=71.0.2,<81" pip wheel pip install -U -r requirements.txt python -m pip install pyinstaller==5.13.2 python devscripts/update-version.py -c "nicolaasjan/yt-dlp" -r "nicolaasjan/yt-dlp" "2025.11.25.144622" python -m bundle.pyinstaller --onedir Where `requirements.txt` is: mutagen pycryptodomex brotli; implementation_name=='cpython' certifi requests>=2.32.2,<3 urllib3>=2.0.2,<3 websockets>=13.0 yt-dlp-ejs I have tested building with PyInstaller 6.16.0 from 3dyd (waiting for 6.17.0 now...) It can be done and it works, but it also requires a reinstall, because of the totally different contents of the zip file (link)... (and then also the ugly presence of `psapi.dll` in the root directory to make it work) TL;DR; as long as it works the old fashioned way, I'm hesitant to build with the "modern" PyInstaller on XP. 🤔 It's annoying that yt-dlp always wants the latest and "greatest". 😠

When using dark magic sharp corners and a custom msstyles after restarting the computer the highlight over the start button is rounded.

@nicolaasjan: Sunday is Nov 30th, 2025, thus I believe you'll be having a "hot potato" in your hands : https://github.com/pyinstaller/pyinstaller/issues/9149#issuecomment-3036991021 [build] Bump PyInstaller minimum version requirement to 6.17.0 https://github.com/yt-dlp/yt-dlp/commit/280165026886a1f1614ab527c34c66d71faa5d69 For the Vista+(aka Win7) builds, your PyInstaller fork v6.17 came just in time : https://github.com/nicolaasjan/pyinstaller-builds/releases/tag/6.17.0 ... but what about those WinXP "onedir" packages which, IIANM, are still using PyInstaller-5.13.2 due to this ? (you can always revert 2801650 prior to the onedir compilation for XP, but how practical would that be in the long run? ...)

Agreed!

Notice: although there are some commits in upstream which worth importing, I'm mentally affected by fire news happened in Hong Kong lately so new build will be delayed (i.e. no build this week)

This may be of some use for Win XP users in today's world with Win XP being phased out more everyday ... this service is also listed to work with Windows 98 SE / ME also. I used it about 6 years ago myself and now am being forced to use it again in Oct 2025 to be able to get my Win XP computer on the internet with a VPN. The paid service I was using has finally cut off all Win XP connections. They warned two years ago it was coming and the service still works for my Windows 7 computer but I still mostly use my Win XP computer for everyday connecting. As I said above ... I used this free VPN about 6 years ago and I have hooked the XP computer up to the service again. I will say that they have really improved things and the service is great in 2025. Perhaps some of you know about it already but if not ... then you can check it out if you need a VPN for Win XP. https://www.vpngate.net/en/ https://www.vpngate.net/en/download.aspx VPN Gate - Public Free VPN Cloud by Univ of Tsukuba, Japan Welcome to VPN Gate. (Launched on March 8, 2013.) - You can get through your government's firewall to browse restricted websites. (e.g. YouTube.) - You can disguise your IP address to hide your identity while surfing the Internet. - You can protect yourself by utilizing the strong encryption while using public Wi-Fi. More Details... - TunnelCrack protection implemented in SoftEther VPN Client (August 31, 2023) Supports Windows, Mac, iPhone, iPad and Android. Compatible OS: Windows, CPU: Intel x86 and x64 (Windows 98 SE / ME / 2000 SP4 / XP SP2, SP3 / Server 2003 SP2 / Vista SP1, SP2 / Server 2008 SP1, SP2 / Hyper-V Server 2008 / 7 SP1 / Server 2008 R2 SP1 / Hyper-V Server 2008 R2 / 8 / 10 / Server 2012 / Hyper-V Server 2012) -------------------------------------------------------------------------------------------------- It looks complicated but it really isn't. Spend some time reading everything and you should be good to go. I'm impressed from using it 6 years ago to how it has improved. One word about connecting, if you need an US connection for banking, Tubi or whatever ... they are not always there, just at various times. You will figure all this out as you get familiar with the service. ...

Intel finally released an official 24H2 compatible graphics drivers for 7th-10th Gen processors (it should also work on 25H2) https://www.intel.com/content/www/us/en/download/776137/intel-7th-10th-gen-processor-graphics-windows.html?wapkw=driver

I assume that you are talking about the version of Supermium in the 'Web Browsers / Browsers working on Older NT-Family OSes' section. That version does not seem to be portable or am I wrong? I am using Win XP and would like a portable version that is Google free for Win XP. I found a version at Major Geeks: Download Supermium Portable - MajorGeeks / Supermium Portable 132.0.6834.226_R5.02 Date: 08/26/2025 Size: 192 MB License: Open Source Requires: 11|10|8|7|Vista|XP https://www.majorgeeks.com/files/details/supermium_portable.html Then at PortableApps.com: Supermium Portable 126.0.6478.261 R7 (web browser with legacy support) Released A new version of Supermium Portable has been released. Supermium is a web browser based on Chrome with legacy Windows support (XP/vista/7/8). https://portableapps.com/news/2025-01-27--supermium-portable-126.0.6478.261-R7-released and there appear to be at least a couple versions at Github ... but they seem to be only for Windows 7 and 8. I've been wanting to try Supermium for a year or so but just not sure which version to work with and if a portable version would work. In the Supermium topic in 'Web Browsers' there is never any talk of a portable version. Would that portable version at Major Geeks be OK to go with? ... I've read the talk about using only an 'ungoogled' version. Thanks ...

Thanks AS for the detailed explanation of the steps in setting up a new profile that you use. I will do the same ... it sounds like the way to go after reading your post. ...

I can't really say whether the problem also occurs in Pale Moon (32-bit or 64-bit ), as I don't use this browser. It was also just a guess. In any case, the Speed Dial 0.9.6.18 and Tab Utilities 2.1.2 extensions in the latest New Moon 28 32-bit release definitely break the session restore function on my Windows XP system. The Session Manager extension only generates some errors in the Browser Console but is still working so far. @UCyborg For reproducing this issue, it is simply enough to only use either Speed Dial or Tab Utilities. So, for example, disable Tab Utilities and Session Manager, start latest New Moon 28 (32-bit), close some tabs and restart the browser. Then you should actually notice that the already closed tabs are still there which means the internal session (re)store does not work anymore if Speed Dial is enabled. You should also see the error message "ReferenceError: nsIWebNavigation is not defined" in the Browser Console when closing tabs from the current browser session. The more tabs you close, the more error messages you will get. At least, that's what I observe in dirty or clean New Moon 28 (most recent version) profiles on my Windows XP 32-bit computer. And I'm pretty sure that I'm not the only one affected by this issue. Maybe, other members may also confirm this issue.

I can't really say whether the problem also occurs in Pale Moon (32-bit or 64-bit ), as I don't use this browser. It was also just a guess. In any case, the Speed Dial 0.9.6.18 and Tab Utilities 2.1.2 extensions in the latest New Moon 28 32-bit release definitely break the session restore function on my Windows XP system. The Session Manager extension only generates some errors in the Browser Console but is still working so far.

Regarding Speed Dial I found a ReferenceError in the Browser Console: ReferenceError: nsIWebNavigation is not defined[Learn More] speeddialOverlay.js%20line%201595%20%3E%20eval:42:13 This error message is generated every time I close a tab. And here is a screenshot taken from NM's Browser Console: And I got this message after resetting Speed Dial and browser restart: [Exception... "Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch.getCharPref]" nsresult: "0x8000ffff (NS_ERROR_UNEXPECTED)" location: "JS frame :: chrome://speeddial/content/speeddialOverlay.js :: startBackgroundLoad :: line 1770" data: no] (unknown) So, the culprit seems to be the JavaScript file speeddialOverlay.js. The main problem with Speed Dial is that when tabs are closed, they are there again after a restart. The current browser session is therefore not restored as it has always been. Same applies to the extension Tab Utilities 2.1.2.

First of all, the extensions don't show any error message pop-ups. However, I didn't check the console. Next time, I will reinstall Speed Dial and check the console messages.

Although your question is of rhetorical nature, I just want to understand what happened. The reported extensions worked for many years properly. So what is the cause for their sudden breakage?

What is this? The main script inside the legacy extension turbolauncher.xpi.

Everything works for me. The userscript Vorapis.user.js, the script patcher.user.js from the webextension, the webextension Project_VORAPIS_OBT_Test_0.8.10.26_(1727286007541).zip itself, the launcher webextension v3_get_old_youtube_layout-1.0.8.xpi and the legacy extension turbolauncher.xpi. The only issue I have is the missing suggestions in the YT search box while typing in UXP browsers.

Mute

rule P.S. I'm still faster

ruse

Lust

Dust

Edge is based on Chromium and closely follows the upstream changes, so no wonder.

So I have gone through group policy and shutdown everything I understand. completely disabled auto updates via group policy, and disabled all telemetry that can be disabled, consumer experiences, and everything else that can be shut down there. No apps, no cortana. Disabled unneeded services. Disabled all unneeded scheduled tasks. Now I am trying to minimize logging. Going through perfmon I find that there are a few logs which I can disable safely without any ill effects. The one that got me was WdiContextLog, as it took some trial and error to figure out that this was the one that caused the start menu to become extremely unresponsive when disabled. There aren't that many logs in here anyway. After disabling a few I have 11 enabled here. Now I don't completely understand how all this works, but I gather that these logs are pulling data from multiple sources in some cases, so maybe that is why NirSoft's EventLogChannelsView shows 299 event log channels as enabled. I am actually doing this for a friend just now, but it will apply to my own system when I get home next week as well. My friend initially wanted to just turn off all the logs, and he tried to, and he broke his OS - lots of strange behavior, extremely slow, and unstable. I'm not sure what all he did, but he was smart enough to take a disk image before his attempt. So I wonder if any of you smart people would not mind helping me to identify which of these 299 channels are essential, which are maybe not essential but might be important, and which are not really needed for someone like me (or my friend) who will never make use of any of them anyway. I really only want those ones running which have to be running for general application compatibility and system stability. EventLogChannelsView gives lots of options for sorting these. You can see which ones are 'classic' and which ones are new. I can see that many have zero entries, and a few have lots of entries. I temporarily disabled all of them, and shut down a number of services in order to open a window of opportunity to create a junction and move winevt directory off the system volume and onto a smaller cheap SSD which is used for vram, scratch disk, indexing, and logging. There was one (Intel-SST-CFD-HDA%4IntelSST.etl) that was very stubborn, but somehow I did manage to gain control of it long enough to create the junction. Then I re-enabled everything just as it was before that operation. Hope some of you might be willing to offer some deeper insight here. For list of enabled event channels see the spoiler at the bottom. As an aside, I am also very curious about NtfsLog in Perfmon. In Windows 10 I seem to recall it writing directly to D:0\$LogFile which is an integral part of the ntfs drive format. This file is presented as if it is essential for the volume to be able to recover failed writes due to unexpected shutdowns or some such. It seems like this is actually of limited use to average users. In general if our system shuts down suddenly, in the middle of writing data, we lose the data. Ntfs or no. Other file systems seem to work perfectly fine without this 'feature,' discounting potential data loss if shutdown mid-write. It seems to me like the major benefits of Ntfs are mostly not facilitated by this logfile. Such as bigger file sizes, and advanced permissions. I digress though. Shouldn't $LogFile be handled by the Ntfs driver or something on a very low level, rather than an event log? Maybe my recollection is mistaken. I will have to recheck Windows 10, but I could swear that the event log "NtfsLog" in perfmon startup was writing to D:0\$LogFile in win 10. Yet right now, I am looking at the very same entry on Server 2016 but it is writing to C:\Windows\system32\LogFiles\Wmi\NtfsLog, which kind of makes more sense. So what is up with NtfsLog?