VistaLover
About VistaLover
- Currently Viewing Topic: KernelEx for Win2000
Recent Profile Visitors
39,234 profile views
VistaLover's Achievements
3.1k
Reputation
-
My Browser Builds (Part 5)
VistaLover replied to roytam1's topic in Browsers working on Older NT-Family OSes
https://en.wikipedia.org/wiki/International_Components_for_Unicode -
Probably for the same reason it doesn't install on WinXP Pro SP2 x64; the Panda devs, in a narrow-minded decision , have hardcoded WinXP to ONLY be NT 5.1; anything higher (e.g. 5.2) is assumed to be Vista+, for which they mandate a version of .NET FW > 4.0.x (4.6 to be precise):
-
... Surely a typo, but you actually mean MB there, don't you ...
-
My Browser Builds (Part 5)
VistaLover replied to roytam1's topic in Browsers working on Older NT-Family OSes
Both, very old (end of 2017), links to WindowsXP-KB936235-v2 (EN) and/or WindowsXP-KB944340 (EN) return 404 currently ... -
I suppose your investigation results are quite valuable to XP SP3 users on old and under-resourced H/W; so, thanks for your time spent ; however, unless one had downloaded to disk v21.01.00 when it was still current, it's now a real task to find working/valid links to actual (off-line) installers to it ; I did a simple G-search for it and ALL results on pages 1-3 point to (mostly) stub or off-line installer-links hosted on the vendor's (PANDA) servers; but these tend to download the latest version of the software, not the older one we're after ; I did succeed in the end in finding links to offline installers for v21.01.00, but these were self-hosted on Iranian and/or Russian sites, so, as you can understand, I won't share them publicly here ; other than that, is there a special setting one should configure in v21.01.00 so that it doesn't auto-update to a more recent version? FWIW, v23.00.00 has now become the latest (digitally signed 22/12/2025) ... Kindest greetings.
-
https://github.com/yt-dlp/yt-dlp/issues/15325 (for reference: https://github.com/yt-dlp/yt-dlp/issues/14923 )
-
FWIW, .NET FW 4.0 isn't a replacement for older .NET frameworks; 2.0/3.5/4.0 can co-exist on the same machine, and each one caters to applications targeting that specific version of .NET FW; i.e., if an app was built against 2.0, it needs 2.0 installed to run; likewise for newer apps built against 4.0... On Vista and later Windows versions, a newer 4.*.* version will overwrite a previously installed 4.*.* version of .NET FW, however this is NOT applicable to XP SP3, where only 4.0.x was made available; loyal XP users here can chime in to assist you, but from memory I recall than some feature/security updates for .NET FW 4.0 were made available at the time for XP SP3; unless the (recent) installer you linked to has those bundled ...
-
My Browser Builds (Part 5)
VistaLover replied to roytam1's topic in Browsers working on Older NT-Family OSes
I fail to see how this is a CPU-related issue (but, please, someone correct me if you have concrete technical details that prove the opposite); I disabled WASM in my browser, but the Krakow map still loaded fine; unless each one of the cited CPUs (Intel i7-4770 vs Intel Core2 Quad Q6700) comes with an embedded iGPU, so it may well be an iGPU "issue" on your case; FTR, the laptop my screengrab was taken on comes with an Intel Core2 Duo T5250 @1.50GHz CPU (Merom), with a Mobile Intel 965 Express Chipset Family iGPU, both pieces of junk by today's standards... @adata has failed to provide any detail about their H/W, or even browser build, other than the info under their avatar that they're running XP SP2 x64; as I've hinted already, if at least WebGL 1 is functional in their UXP browser (and other WebGL-based sites load OK), this is likely a JS issue... I no more use UXP as my main platform on Vista SP2 32-bit, so I'm not very likely to dig any deeper on this ... -
My Browser Builds (Part 5)
VistaLover replied to roytam1's topic in Browsers working on Older NT-Family OSes
There is no map in Chrome v140 ... But it loads OK in r3dfox-140.0.4: so this isn't, probably, a site issue ... Do note that this service embeds "maps" from the https://openmaptiles.org/ https://www.openstreetmap.org projects and for the maps to display correctly in a browser, it has to have WebGL (1 or 2) support enabled (and I remember from his 360EE days that NHTPG has a tendency to disable WebGL in his browsers ) ... If your NM28/St52 copy has WebGL support enabled (check in about:support -> graphics), then the most probable reason the Krakow map doesn't load is UXP's Javascript-related shortcomings ; in a slightly older (not current) NM28 build, BrowserConsole reports a TypeError: -
... It would appear "someone" is reading this thread ; disregard above link (it now 404s), here's the new one: https://github.com/3dyd/pyinstaller-builds/releases/tag/latest (with previous releases (6.16.0) reinstated )
-
New 6.17.0 releases by 3dyd (and it's a shame every new release overwrites the previous one ; not a good practice if "things" break and one needs to revert ) : https://3dyd.github.io/pyinstaller-builds/
-
... Well, this isn't a very reassuring answer, you do realise that ... Don't know ; perhaps @user57 is on the right track on this (or even @cmalex, safe may he be, knows more ); the question to be asked is why did it magically appear in the latest yt-dlp WinXP compiles, whereas it wasn't present (needed?) all that time before? ... Can't tell; my AV solution gave it a "clean bill of health" ; you can try to see if the WinXP packages launch and function OK WITHOUT it, then take the necessary steps to remove it altogether; I'm not being paranoid (I think ), but I'd rather not have it there, if it isn't indispensable... Best festive wishes ...
-
Another thing I wanted to mention to you @nicolaasjan is that in both the latest "WinXP" packages: https://github.com/nicolaasjan/yt-dlp/releases/download/2025.11.25.144622/yt-dlp_x86_winXP.exe https://github.com/nicolaasjan/yt-dlp/releases/download/2025.11.25.144622/yt-dlp_x86_winXP.zip a new DLL appears to have infiltrated, "fileextd.dll", which wasn't there in all of your previous "WinXP" releases, e.g. in https://github.com/nicolaasjan/yt-dlp/releases/download/2025.11.12.051143/yt-dlp_x86_winXP.exe https://github.com/nicolaasjan/yt-dlp/releases/download/2025.11.12.051143/yt-dlp_x86_winXP.zip Was that an inadvertent inclusion?
-
Ditto that...
-
Makes sense; if Z was the last to have been loaded in the tab when that tab was closed, why do you expect otherwise? After all, the browser feature is called "Recently Closed Tabs", not "Recently Visited Sites" ; however, a closed-tab's history isn't being deleted (it's saved in session data); re-open the tab with site Z on it, then use the back button once to revisit site Y (or twice for site X, etc.) ...