Leaderboard

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20250419-3219d2d-uxp-42e13fd8bf-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20250419-3219d2d-uxp-42e13fd8bf-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom IA32 Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20250419-3219d2d-uxp-42e13fd8bf-xpmod-ia32.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/ia32 NM28XP build: Win32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20250419-d849524bd-uxp-42e13fd8bf-xpmod.7z Win32 IA32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20250419-d849524bd-uxp-42e13fd8bf-xpmod-ia32.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20250419-d849524bd-uxp-42e13fd8bf-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20250419-d849524bd-uxp-42e13fd8bf-xpmod.7z Win7+ x64 AVX2 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20250419-d849524bd-uxp-42e13fd8bf-w7plus-avx2.7z Official UXP changes picked since my last build: - No issue - Various updates for Mac buildability with XCode 16.3 (59977aa358) - No issue - set UXP to dereference links in file open dialogs. (17031f216b) - Issue #2726 - Remove obsolete FirefoxOS MMS prefs (d13c759467) - No issue - Update Twemoji font to unicode 16.0.0 (9ff0c63602) - Issue #2729 - Add missing jsonifier interfaces to DOM{Matrix|Rect|Point} (8bacedc9a9) No official Pale-Moon changes picked since my last build. No official Basilisk changes picked since my last build. Update Notice: - You may delete file named icudt*.dat inside program folder when updating from old releases. * Notice: From now on, UXP rev will point to `custom` branch of my UXP repo instead of MCP UXP repo, while "official UXP changes" shows only `tracking` branch changes.

@Dietmar @reboot12 @Mov AX, 0xDEAD I discovered this today. https://github.com/FlyGoat/csmwrap Hopefully this means we can boot XP x86 on UEFI class 3 systems now.

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20250503-3219d2d-uxp-5384bb6d14-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20250503-3219d2d-uxp-5384bb6d14-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom IA32 Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20250503-3219d2d-uxp-5384bb6d14-xpmod-ia32.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/ia32 NM28XP build: Win32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20250503-d849524bd-uxp-5384bb6d14-xpmod.7z Win32 IA32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20250503-d849524bd-uxp-5384bb6d14-xpmod-ia32.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20250503-d849524bd-uxp-5384bb6d14-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20250503-d849524bd-uxp-5384bb6d14-xpmod.7z Win7+ x64 AVX2 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20250503-d849524bd-uxp-5384bb6d14-w7plus-avx2.7z Official UXP changes picked since my last build: - Issue #2731 - Fix crashes on unknown BigInt types in JIT (d7f01911b8) - Issue #2728 - Remove obsolete CSP referrer policy. (0331e633bd) - Issue #2732 - Part 1: Rename mContainsBlockContents to mConsiderWholeSubtree (2ef82632d4) - Issue #2732 - Part 2: Stop accepting <a> as a valid image map <area> (9f64d0f4b0) - No Issue - Modernize nsImageFrame/nsImageMap (8db40dbbb5) - No issue - restore nullptr-check (8a21d95ea3) - Issue #2732 - Part 3: Explicitly search for <area> only. (8ae2b45691) - Issue #2737 - Part 1: Base implementation of `SVGGeometryElement`. (fd4a224d1d) - [NSS] Improve locking in nssPKIObject_GetInstances. (be9a6ed2ac) - [devtools] Escape some more characters for copying as cURL on Posix. (ba3a5074c7) No official Pale-Moon changes picked since my last build. No official Basilisk changes picked since my last build. My changes picked since my last build: - nss: update builtin certstore and bump ckbi version (5384bb6d14) Update Notice: - You may delete file named icudt*.dat inside program folder when updating from old releases. * Notice: From now on, UXP rev will point to `custom` branch of my UXP repo instead of MCP UXP repo, while "official UXP changes" shows only `tracking` branch changes.

I have completely changed and rewritten the original ytBATCH from eppic so that it now works perfectly with both YouTube downloaders youtube-dl and yt-dlp. All bugs and inconsistencies have been fixed by me. Especially the fact that the command line options of both downloaders are not identical, I have taken into account by assigning separate configuration files to each downloader. This allows the user to enter the desired options for each downloader and then receive the media files exactly as desired. ytBATCH for Windows XP is totally customised for the use of youtube-dl and yt-dlp, and ideal as a user interface for these two YouTube downloaders. And due to the new update module, the user can easily get the most recent versions of these two YouTube downloaders compatible with older OSes like Windows XP when ever wanted. This is very important regarding the permanent changes which are done by YouTube.

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20250517-3219d2d-uxp-296db1641b-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20250517-3219d2d-uxp-296db1641b-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom IA32 Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20250517-3219d2d-uxp-296db1641b-xpmod-ia32.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/ia32 NM28XP build: Win32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20250517-d849524bd-uxp-296db1641b-xpmod.7z Win32 IA32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20250517-d849524bd-uxp-296db1641b-xpmod-ia32.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20250517-d849524bd-uxp-296db1641b-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20250517-d849524bd-uxp-296db1641b-xpmod.7z Win7+ x64 AVX2 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20250517-d849524bd-uxp-296db1641b-w7plus-avx2.7z Official UXP changes picked since my last build: - No issue - Include all non-ubiquitous image and media types in nav Accept: (0e02e94278) - No issue - Explicitly indicate image/apng in `Accept:` header (055765d101) - No Issue - Fix incorrectly written pref name (40e01c31e4) - No Issue - Fixes for building with LLVM 19 included with FreeBSD 13.5. Fix a conflict with libc++ 19 and the old Mozilla (re)alloc macros. LLVM 18+ does not allow std::char_traits<unsigned char> so avoid it. https://bugzilla.mozilla.org/show_bug.cgi?id=1849070 Partial NSS upgrade to replace ByteString with a class. https://bugzilla.mozilla.org/show_bug.cgi?id=1851092 (e8b3077d4f) - No issue - Bump general.useragent.compatMode.version to 128.0 (facab7f0ab) - No Issue - Remove obsolete pref. (422ca16a8e) - Issue #2736 - Part 1: Provide more consistent principals to CSP. (9ad680cfc4) - Issue #2736 - Part 2: Pass subject principal to SetAttribute and friends. (824d0cad58) - Issue #2736 - Part 3: Use `TriggeringPrincipal` for image loads. (166b25a42c) - Issue #2736 - Part 4: Re-work img `<src>` attribute. (c8db9efb3c) - Issue #2736 - Part 5: Re-work img `<srcset>` attribute. (2bdb9f3d85) - Issue #2736 - Part 6: Re-work <script> `src` attribute. (1f638b22ec) - Issue #2736 - Part 7: Re-work <frame> and <iframe> `src` attribute. (2416e71cd3) - Issue #2736 - Part 8: Re-work <video> and <audio> `src` attribute. (b6bdce6f98) - Issue #2736 - Part 9: Re-work <source> `src` attribute. (b1b5062dc4) - Issue #2736 - Part 10: Re-work <source> `srcset` attribute. (faf4f2c23f) - Issue #2736 - Part 11: Re-work <input> `src` attribute. (dde21838de) - Issue #2736 - Part 12: Re-work style <link> `href` attribute. (60ad5b2ffd) - Issue #2736 - Follow-up: Fix line endings in nsGenericHTMLFrameElement.h (727acf7b3f) - Issue #2736 - Part 13: Override page CSP for loads by expanded principals. (9847e9f759) - Issue #2736 - Part 14: Make CSP-enabled available to workers. (53a6f6349d) No official Pale-Moon changes picked since my last build. No official Basilisk changes picked since my last build. Update Notice: - You may delete file named icudt*.dat inside program folder when updating from old releases. * Notice: From now on, UXP rev will point to `custom` branch of my UXP repo instead of MCP UXP repo, while "official UXP changes" shows only `tracking` branch changes.

And you wouldn't prefer to to have ESR 128.x? It's more up to date.

https://github.com/Eclipse-Community/r3dfox/releases/tag/v128.10.0

The query on GitHub has been updated. It seems the problem went away with a new clean profile.

StartAllBack 3.9.8

FYI, all releases of ytBATCH for Windows XP have been fixed by me so that the setup routine does not only work correctly on drive C: but also on any other drive. Please, re-download the desired release! ytBATCH for Windows XP 1.6 is currently the most recent, final release and recommended by me. Cheers, AstroSkipper

Your question can only be answered if you specify "a program". ytBATCH for Windows XP, for example, has an option to switch between youtube-dl and yt-dlp in the Preferences window. Just type Y. And it can also deal with playlists whose option can be toggled from false to true in the Enter Action window by the key P.

I think you misunderstood my comment a little. The sequence is not correct. First open the VTHash.exe with a double click, the window is then opened hidden and only then open a new Explorer window. For me and @genieautravail, the VTHash.exe window then becomes visible again on older computers.

Intel Pentium 4 Northwood 2.80 GHz CPU (single core, 32 Bit), 1.5 GB SD-RAM and a NVIDIA GeForce 6200 graphic card. As I already mentioned, the hidden window appears again if I open an Explorer window. Very strange.

The latest official version of youtube-dl is from 2021. To get a more recent one, the user would have to compile an executable with all recent changes. Fortunately, @nicolaasjan has been doing this even for SSE only CPUs. When it comes to YouTube-DL Gui 0.4, I now have tested it again. Basically, it still works with both youtube-dl and yt-dlp. But the internal switches are from 2017 and cause problems. The subtitles option has to be switched off as it stopped working. The different, pre-adjusted switches for the video quality do not really work well. If you set 480p, you get something with 398p. To get the programme running smoothly again, the source code would have to be considerably revised and recompiled. ytBATCH for Windows XP, on the other hand, can be set so perfectly that you get exactly what you want.

I use Process Hacker for many years. It shows only one VTHash.exe process whose window entry is disabled though. I also had sometimes two processes in Process Hacker if I forgot to close the previously opened one.

@genieautravail The behaviour of your compiled VTHash.exe file reminds me of executables I have compiled in the past with the "invisible on startup" option. Perhaps, you can check your chosen options for compilation. Just an idea.

Since this shortcut works perfectly, it is very unlikely that a background programme could be the cause. I have even closed Min2Tray from my ProxHTTPSProxy programme, but this has had no effect. Apart from that, it only minimises windows and does not hide them. Otherwise, no other window manager is running in the background here. If I understand you correctly, then calling VTHash.exe by double-clicking works for you under Windiws XP. Is that correct?

New build of post-deprecated Serpent/moebius for XP! * Notice: This repo will not be built on regular schedule, and changes are experimental as usual. ** Current moebius patch level should be on par with 52.9, but some security patches can not be applied/ported due to source milestone differences between versions. Test binary: Win32 https://o.rthost.win/basilisk/basilisk55-win32-git-20250517-c2f7c8359-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk55-win64-git-20250517-c2f7c8359-xpmod.7z repo: https://github.com/roytam1/basilisk55 Repo changes: - import from UXP: No issue - Include all non-ubiquitous image and media types in nav Accept: (0e02e942) (fde26a193) - import from UXP: No issue - Explicitly indicate image/apng in `Accept:` header (055765d1) (395bab66e) - import from UXP: No Issue - Fix incorrectly written pref name (40e01c31) (29041562f) - import from UXP: No Issue - Fixes for building with LLVM 19 included with FreeBSD 13.5. Fix a conflict with libc++ 19 and the old Mozilla (re)alloc macros. LLVM 18+ does not allow std::char_traits<unsigned char> so avoid it. https://bugzilla.mozilla.org/show_bug.cgi?id=1849070 Partial NSS upgrade to replace ByteString with a class. https://bugzilla.mozilla.org/show_bug.cgi?id=1851092 (e8b3077d) (8a4ba96e2) - ported from UXP: No issue - Bump general.useragent.compatMode.version to 128.0 (facab7f0) (e77671e81) - ported from UXP: Issue #2736 - Part 1: Provide more consistent principals to CSP. (9ad680cf) (3cc87110c) - ported from UXP: Issue #2736 - Part 2: Pass subject principal to SetAttribute and friends. (824d0cad) (058c37fa0) - ported from UXP: Issue #2736 - Part 3: Use `TriggeringPrincipal` for image loads. (166b25a4) (70eba97bf) - import from UXP: Issue #2736 - Part 4: Re-work img `<src>` attribute. (c8db9efb) (4f874413c) - import from UXP: Issue #2736 - Part 5: Re-work img `<srcset>` attribute. (2bdb9f3d) (22c94d27d) - import from UXP: Issue #2736 - Part 6: Re-work <script> `src` attribute. (1f638b22) (79991b522) - ported from UXP: Issue #2736 - Part 7: Re-work <frame> and <iframe> `src` attribute. (2416e71c) (097ef177e) - import from UXP: Issue #2736 - Part 8: Re-work <video> and <audio> `src` attribute. (b6bdce6f) (9c111f82f) - import from UXP: Issue #2736 - Part 9: Re-work <source> `src` attribute. (b1b5062d) (84759664a) - import from UXP: Issue #2736 - Part 10: Re-work <source> `srcset` attribute. (faf4f2c2) (939dade79) - import from UXP: Issue #2736 - Part 11: Re-work <input> `src` attribute. (dde21838) (747190ee5) - import from UXP: Issue #2736 - Part 12: Re-work style <link> `href` attribute. (60ad5b2f) (206c5b2a8) - ported from UXP: Issue #2736 - Part 13: Override page CSP for loads by expanded principals. (9847e9f7) (2f5762f73) - ported from UXP: Issue #2736 - Part 14: Make CSP-enabled available to workers. (53a6f634) (c2f7c8359)

Everything seems to be fine here on Windows 10. It's almost certainly a false positive, but until win32ss comments on the report, we don't know.

Sorry for the off-topic, these are more beautiful to my taste, pleasant colours and look more like XP era drivers. 36x,xx has a more "moderm" look. Besides, 352.xx and 355,xx have the better Directx9 speed. 368 give nothing new to XP.

Early tests on IG with the new 32-bit version on XP look promising, but as far as I know the issue I reported has never been flagged on GitHub anyway! I was thinking of doing so. I will try later with the 64-bit version on Windows 10. Twitch and TikTok I don't use, I'm afraid.

A new update of Supermium 132.0.6834.222 R3 has been released. Changelog - This exceptional release of Supermium includes various enhancements over Supermium 132 R3, including: (#1372) - some tweaks to the look-and-feel of v109 Tabs. Tab-specific compact UI options are separated from #compact-ui, now in #compact-tab-ui. (#1370) - a new feature named #open-bookmark-option allows users to open bookmarks in new tabs, either in the foreground or background. This replaces the equivalent Chrome++ functionality that is currently unstable with Supermium. (#1382) - drag-and-drop fully restored on NT 5.x. (#1368) - CR23: tab separator duplication disabled by default, other metrics modified including tab gaps (#1367) - Widevine patch updated for version 4.10.2891.0 Glad that drag and drop has been restored to the XP version, you couldn't even re-order the extension icons on the previous version! The feature to always open bookmarks in a new tab is one I've lobbied for for ages, so I'm really pleased with that too. It means that I don't have to use Chrome++ on Windows 10 any more, and I now have that facility on XP (Chrome++ doesn't work on XP). If it all works as it should, I'm really delighted with this!

Ok. Then I'll try to answer the question about the compatibility first of all with the example of extensions in Mypal 68 myself. Unfortunately, my answer has to be: No. Mypal 68.14.8b does not have a clear compatibility policy. Even some extensions that are actually FF68 compatible do not work for various reasons. One of them is the fact that Mypal 68 has never been a complete Firefox 68 version. Consider, for example, the still missing Internationalization & Localization feature I reported to Mypal's issues on GitHub three years ago that, however, some extensions, for example those dealing with time, date, timezones and so on, definitely require. uBlock Origin 1.62, on the other hand, works in Mypal 68.14.8b, although it is actually FF78+ compatible. Another example is the Scratchpad 0.7.1 extension. Since @feodor2 has removed the very useful, internal Scratchpad in Mypal 68.14.8b following Mozilla , I wanted to retrofit it with the help of this extension, which is FF72+ compatible. Unfortunately, that didn't work out. Not compatible. In Firefox 74, however, it works. So, Mypal 68.14.8b and extension compatibility is rather a game of trial and error. MinVersion numbers of extensions are only of limited use in this browser. At this point, I would personally appreciate a Mypal 68 browser with a state of development of 74 announced by its developer that then also should behave like its brother Firefox 74 in terms of compatibility. Strictly according to the motto: Whoever says A, must also say B. (German saying) And that's completely independent of whether I like these newer Firefox versions or not.

Which official MyPal extension page? There is none. Extensions for Mypal 68 have to be downloaded from the official Firefox Add-ons page, i.e. from addons.mozilla.org.

Forget the about:performance page! It has never been reporting memory usage correctly and reflecting the true values. Here is a comment from a developer: https://bugzilla.mozilla.org/show_bug.cgi?id=1744869 And a quote from there: I can confirm this statement. It always has been a junk feature.

@feodor2 In case it has escaped your attention, here is my question again:

@feodor2 Ok. Now, your fix seems to be working. At least, the code editor has started again to behave as usual. The reason it didn't work before was when purging the startup cache, then the code editor becomes inaccessible and a normal restart has additionally to be performed. However, I modified the fix a bit to depend on the current platformVersion instead of a static number. For this purpose, I had to insert one additional line. The code posted beyond is the part from line 1 to 59 of the SelfHelper.jsm file. The changes are located in line 55 and 56: var EXPORTED_SYMBOLS = ["SelfHelper"]; var AC, SelfHelper = { data: { "chrome://custombuttons/content/editor.xul": { 65: "groupbox", 68: "ondialog", 71: "textbox menulisticonic cbeditor", 76: "input", 77: "menulist", 85: "fluent", 108: "contentbox", 109: "menulist109", 113: "flexapocalypse", 116: "wrapwidth", 125: "picker" }, "chrome://custombuttons/content/prefs.xul": { 65: "groupbox", 68: "ondialog", 107: "checkbox", 111: "dialogwidth", 113: "flexapocalypse" }, "chrome://custombuttons/content/dialogs/finddialog.xul": { 65: "groupbox", 68: "ondialog", 71: "textbox", 76: "input", 107: "checkbox", 111: "dialogwidth", 113: "flexapocalypse" }, "chrome://custombuttons/content/dialogs/cbpromptdialog.xul?type=checkbox": { 65: "groupbox", 68: "ondialog" }, "chrome://custombuttons/content/dialogs/cbpromptdialog.xul?type=radiobox": { 65: "groupbox", 68: "ondialog" }, "chrome://custombuttons/content/dialogs/replconfirm.xul": { 68: "ondialog", 111: "dialogwidth" }, }, noop() {}, get map() { var {AppConstants} = AC || ChromeUtils.import( "resource://gre/modules/AppConstants.jsm" ); var {platform} = AppConstants; this.platform = ["win", "linux", "macosx"] .includes(platform) ? platform : "linux"; var { Services } = ChromeUtils.import("resource://gre/modules/Services.jsm"); this.version = parseInt(Services.appinfo.platformVersion); if (this.version >= 95) { var pref = "extensions.custombuttons.prefersColorSchemeOverride"; var pb = Cc["@mozilla.org/preferences-service;1"].getService(Ci.nsIPrefBranch); Thanks for the temporary fix! I hope you can fix your browser in terms of the versions problem soon.

Once again, this is the new code from line 1 to 58: var EXPORTED_SYMBOLS = ["SelfHelper"]; var AC, SelfHelper = { data: { "chrome://custombuttons/content/editor.xul": { 65: "groupbox", 68: "ondialog", 71: "textbox menulisticonic cbeditor", 76: "input", 77: "menulist", 85: "fluent", 108: "contentbox", 109: "menulist109", 113: "flexapocalypse", 116: "wrapwidth", 125: "picker" }, "chrome://custombuttons/content/prefs.xul": { 65: "groupbox", 68: "ondialog", 107: "checkbox", 111: "dialogwidth", 113: "flexapocalypse" }, "chrome://custombuttons/content/dialogs/finddialog.xul": { 65: "groupbox", 68: "ondialog", 71: "textbox", 76: "input", 107: "checkbox", 111: "dialogwidth", 113: "flexapocalypse" }, "chrome://custombuttons/content/dialogs/cbpromptdialog.xul?type=checkbox": { 65: "groupbox", 68: "ondialog" }, "chrome://custombuttons/content/dialogs/cbpromptdialog.xul?type=radiobox": { 65: "groupbox", 68: "ondialog" }, "chrome://custombuttons/content/dialogs/replconfirm.xul": { 68: "ondialog", 111: "dialogwidth" }, }, noop() {}, get map() { var {AppConstants} = AC || ChromeUtils.import( "resource://gre/modules/AppConstants.jsm" ); var {platform} = AppConstants; this.platform = ["win", "linux", "macosx"] .includes(platform) ? platform : "linux"; this.version = 74; if (this.version >= 95) { var pref = "extensions.custombuttons.prefersColorSchemeOverride"; var pb = Cc["@mozilla.org/preferences-service;1"].getService(Ci.nsIPrefBranch); Is that correct? You should think carefully about what you say. None of what I have written is spam or flame. Do you even know what spam or flame means or is? However, your statement I quoted above comes closer to that. Politeness doesn't seem to be everyone's cup of tea. Anyway! Can you finally explain why the Custom Buttons extension properly works in Firefox 74 without any fix but not in Mypal 68.14.8b? Just a wrong version number which your browser reports to the Custom Buttons extension at a certain point as I assumed at the beginning?

I tried your fix. If I have understood you correctly, in the SelfHelper.jsm file, I should replace line 55 this.version = parseInt(AppConstants.MOZ_APP_VERSION); with the following one: this.version = 74; If so, then this does not fix anything. The only thing that happens is a lot of new ReferenceError messages "Service is not defined" in the Browser Console. Furthermore, I think that it is not the Custom Buttons extension that needs to be fixed, which runs properly under Firefox 74, but Mypal 68.14.8b. What do you mean by "hubbub"? Did you even read what I wrote? I consider such an answer to all my information, investigations and questions that I have put a lot of effort into to be absolutely inadequate. I have asked you a few questions, but have not received any answers. And once again, I no longer think the issue is related to a version mismatch. All is explained in the posts above and in my thread "Mypal 68 in Windows XP". Keyword: XBL But I will not repeat myself here.

@feodor2 I'm afraid that you've overshot the mark with your changes as you did in version 68.14.5b. With a probability bordering on certainty, there will be other "patients" who suffer from similar "symptoms" as is currently the case with Custom Buttons. Whatever the actual cause, I hope I could help you with my investigations and information.

Thanks for your reply! I investigated the code of Custom Buttons more deeply, and you are right, the Custom Buttons extension solely relies on the platformVersion, Since you removed the XUL stuff, you logically can't keep the platformVersion at 68. But your new release Mypal 68.14.8b has become somehow versionless. It doesn't behave as a Firefox 68 and it doesn't behave as a Firefox 74. It's a bit lost. Your browser tells Custom Buttons that it is Firefox 74, but it is not. Today, for this purpose, I have made a proof and installed Firefox 74 Portable on a Windows 7 Professional 64-Bit notebook, injected the two files config-prefs.js and config.js, and installed the legacy Custom Buttons extension. As I have already predicted, Custom Buttons runs perfectly under Firefox 74. The code editor is fully functional. The legacy Custom Buttons extension has always been compatible with much newer Firefox versions and is constantly being developed further. Here are two screenshots to demonstrate what the issue is about: Custom Buttons' broken code editor in Mypal 68.14.8b: Custom Buttons' fully functional code editor in Firefox 74.0.1: As I already said, you must have removed something that Mozilla did not. And I suspect it has something to do with XBL. Certain functions for binding XML files are required by the Custom Buttons extension for the code editor, which you have probably removed. That's why I said your new release is somehow versionless. Neither fish nor fowl. Sorry for that! The conversion from XUL to XHTML is no problem as you can see. Anyway! I hope you won't behave worse than Mozilla did in the past, and I urgently hope you will be able to restore a general version compatibility. And it doesn't matter which Firefox version you raise the platformVersion to as nevertheless the Custom Buttons extension should work then.

Sorry but unfortunately, I have to disagree when it comes to Windows XP -> Windows NT 5.1 and Mypal 68. As you know, this topic here is about Mypal 68 in Windows XP . I have tested all possible Firefox version numbers by a SSUAO in Mypal 68.14.8b, and 128 was definitely the minimum to get rid of the yellow message box. Any version lower than 128 failed. Greetings, AstroSkipper

@feodor2 Thanks for your new release Mypal 68.14.8b! I am currently testing this version more closely. Due to the complete removal of XUL and XBL, a lot has changed. I have already reported about it here. Similar to version Mypal 68.14.5b, the legacy Custom Buttons extension is no longer fully functional. The internal code editor is totally broken and therefore has become unusable. You can no longer access, view or edit the code with the extension. New custom buttons can't be created, either. The legacy Custom Buttons extension should actually also work in higher Firefox versions. It has corresponding XHTML files and compatible code that is made available via appVersion queries. It could be that an incorrect version is being determined, as version 68 or version 74 is displayed in Mypal 68.14.8b depending on the corresponding command. I checked that in the Browser Console. BTW, I really miss the Scratchpad which is also gone in your new release. Another guess I have is that you have removed something important that requires the legacy Custom Buttons extension. As you know, in Mypal 68.14.7b, the legacy Custom Buttons extension still worked. Maybe, you can take a look at it. BTW, what is the current level of JavaScript and CSS in Mypal 68.14.8b?

Thanks for replying! This is just a leftover and has now been edited by me. But the other announcements are correct and point to the most recent version.

A night's sleep always brings new ideas to light. The 7-Zip commands for extracting can be simplified to remain completely relative in the path information such as I already did in the whole ytBATCH for Windows XP script ensemble. I will implement this in the next release. Sometimes, things are that simple.

@Cixert Both your system error 3 and the message "permission denied" do not happen here in any case and therefore can't be reproduced by me. They seem to be related to your system only. So, solving that is up to you. On the other hand, the inability of correct unzipping on your drive D: was caused by a 7zip command which was actually relatively created by me but was unintentionally bound to drive C: exclusively. However, this had no negative effect on standard computers with C: as the system drive. That's why I didn't notice it. Anyway! ytBATCH for Windows XP should now be able to be set up automatically and without any errors (at least, no erros caused by ytBATCH for Windows XP), even on a non-standard computer as yours. Thus, thanks again for your report here and for being non-standard!

The current final is version 1.6. It was clearly announced. Where did you read anything about a beta? The versions 1.5 and 1.6 are final ones. The programme ytBATCH for Windows XP usually does not use any absolute paths but relative ones or those stored in system variables. When installing it, you can choose between the location stored in the system variable %ProgramFiles% or the current location of the extracted archive folder. When setting up on drive C:, it works fine. Of course, I didn't expect anyone to come up with the idea of setting it up on a different drive. The information that you tried to set up ytBATCH for Windows XP on other drive than C: is of course important. Thanks for that! You have exceptional skills and really came through here. And now, you get your special treatment. I had a short look into my code and directly found the cause of the inability to unpack both archives on a drive other than C:. I have tested it on my drive D: and then directly fixed the code. But no system error 3 or message "permission denied" here. @Cixert In which format has your D: drive been partitioned? Possibly in NTFS with some restrictions? I urgently need an answer to this question from you. P.S: I'm glad that there are individualists like you who do things differently from the rest of us. Thank you for that!

https://github.com/ytdl-org/youtube-dl#video-selection --playlist-start NUMBER Playlist video to start at (default is 1) --playlist-end NUMBER Playlist video to end at (default is last) --playlist-items ITEM_SPEC Playlist video items to download. Specify indices of the videos in the playlist separated by commas like: "-- playlist-items 1,2,5,8" if you want to download videos indexed 1, 2, 5, 8 in the playlist. You can specify range: " --playlist-items 1-3,7,10-13", it will download the videos at index 1, 2, 3, 7, 10, 11, 12 and 13. ... Then make sure you have perused ALL available CLI options (aka switches) for BOTH; for youtube-dl (often abbreviated as just yt-dl), the place to start is: https://github.com/ytdl-org/youtube-dl#options FWIW, yt-dlp is a more "advanced" tool (with more complex syntax and options), that requires some additional expertise on the part of the user ; yt-dlp is not guaranteed to continue to work under XP (and Vista) after this October, when its devs drop py3.9 support (to this day, no py3.10+ fork has been made public that can run on NT 5.x/6.0 ) ....

And that attempt was made using gtx1060, which is even older than 1050! XP drivers only exist up to 36x.xx , for 1050 you need 373.xx as the minimum. But it's only made for Vista and up (thanks to D.Draker). If you try, you will get BSOD.

( Happy Easter to all those who observe it ! ) New r3dfox releases have appeared on its GitHub repo : https://github.com/Eclipse-Community/r3dfox/releases/tag/v128.9.0 ... and: https://github.com/Eclipse-Community/r3dfox/releases/tag/v136.0.4 Many thanks to the maintainer! ...

@genieautravail Long time ago, I downloaded a package of DOS auxiliary tools. Inside this package was the Window.exe tool. I can't remember from where exactly. But I always download programmes only from trusted sources and developers. I now have large archives with all kinds of tools. These little tools are simply great and can be of help when programming new projects. A good source for command line tools is GitHub and DosTips. However, since the end of March, DosTips's certificate has unfortunately expired, which is of course immediately recognised and warned by all browsers. Not really a problem for me. I hope this will be fixed soon.

I have updated the YouTube files in the last XP-compatible PotPlayer version some days ago, taken from the most recent PotPlayer release. It works like a charm. No problems with cookies or anything else here. BTW, this last XP-compatible, slightly older PotPlayer is still the best media player under Windows XP, IMHO.

Setting up ytBATCH for Windows XP And for all setting up (I deliberately avoid the term installing at this point since my downloader is actually portable) ytBATCH for Windows XP, here some more technical explanations in terms of the setup process. Executing the ytBATCH.bat file located in the main programme directory of the unpacked archive calls up the Launcher.bat file which decides apart from other tasks whether it is an initial setup or not. In the case of such an initial setup, it performs then an automatic, unique start of the file called Installer.bat which copies the unpacked folder to the %ProgramFiles% location if wanted by the user, generates a desktop shortcut and adjusts all additional shortcuts with different colour schemes in the subfolder lnk. After finishing its job, it then starts the FileDownloder.bat file which downloads, unpacks and stores all necessary files into the exe subfolder. All is automatically done by the script. The user has only to make some few decisions. Furthermore, all important things are explained by the output of the script. If the user decides to reinstall my YouTube downloader ytBATCH for Windows XP, both the complete programme folder and the desktop shortcut have to be deleted, or alternatively all files inside the exe subfolder and only the UserConfig.bat file inside the cfg subfolder have to be removed. The setup or reinstall routine has always to be started with the execution of the ytBATCH.bat file located in the main programme folder. And that means do not manually call up any of the batch files inside the bin subfolder! These files will be only executed by the batch files themselves. At no time does one of these need to be called up by a user. This also applies when everything is set up. Anyone who still manages to generate an error message while setting up ytBATCH for Windows XP after all these explanations has exceptional skills and should contact me urgently here in this thread for further treatment. And don't be afraid, all at no costs, of course! Cheers, AstroSkipper

New build of post-deprecated Serpent/moebius for XP! * Notice: This repo will not be built on regular schedule, and changes are experimental as usual. ** Current moebius patch level should be on par with 52.9, but some security patches can not be applied/ported due to source milestone differences between versions. Test binary: Win32 https://o.rthost.win/basilisk/basilisk55-win32-git-20250419-0be39e8b3-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk55-win64-git-20250419-0be39e8b3-xpmod.7z repo: https://github.com/roytam1/basilisk55 Repo changes: - import from UXP: No issue - Various updates for Mac buildability with XCode 16.3 (59977aa3) (a13deb49e) - import from UXP: No issue - set UXP to dereference links in file open dialogs. (17031f21) (5a8f82087) - ported from UXP: Issue #2726 - Remove obsolete FirefoxOS MMS prefs (d13c7594) (e54ee7599) - ported from UXP: No issue - Update Twemoji font to unicode 16.0.0 (9ff0c636) (d49d038cb) - import from UXP: Issue #2729 - Add missing jsonifier interfaces to DOM{Matrix|Rect|Point} (8bacedc9) (0be39e8b3)

ytBATCH for Windows XP was developed by me primarily as a YouTube downloader. I have preset its configuration files for this purpose and configured it by default so that users with weaker hardware can also use it. Those using much more powerful hardware should adapt the two configuration files yt-dlp.conf and youtube-dl.conf in the cfg folder to their needs. I was recently asked whether ytBATCH for Windows XP can also be used to download video or audio files on other platforms. This should be possible, as yt-dlp and youtube-dl support different websites and platforms by default. However, new, additional configuration files must be created for these and provided with command line options that are compatible with these services. When doing so, it is very important that the currently active config files always have to be named yt-dlp.conf and youtube-dl.conf. In any case, I would personally like to hear about your experiences with ytBATCH for Windows XP. Furthermore, I have expressed the assumption that my downloader also works under other, older operating systems such as Windows Vista or Windows 7, which I am looking forward to receiving confirmation of. In any case, developers who don't earn a cent with their programmes live at least from the feedback of their users.

You're very welcome, the max. TDP for 780 is 250W, 5.73% idling is about 14 watt, which is very near to yours, and absolutely fine for a 28nm GPU.

I used the drivers that came with the Xonar CD (which contained both Xp and Vista), but obviously not 11, hence I don't know and can't make judgements about 11. At that time, I had just D1, but later upgraded to the more advanced Xonar D2, The sound on Vista was fantastic, on XP and 7, very similar to what we were listening in the 80's terrible cassette walkmans. or similar to the garbage mp3. On Vista, I always choose 192Khz, of course not 44, and 44 is more like for partially deaf people, the ones who have nothing to lose in the terms of quality anyways. I served in the artillery, my hearing is damaged, and even I hear the clear difference in favour of Vista.

@mjd79, the new 135 is 400mb in size, is this normal?

Found it! This driver worked for that member, I don't remember, probably, and most likely I gave it. https://drivers.softpedia.com/get/GRAPHICS-BOARD/NVIDIA/NVIDIA-GeForce-iCafe-Graphics-Driver-35573-for-XP.shtml

Mark, but this screenshot is from 344, not 347 I gave you earlier, I remembered, we had a user@UCyborg with an identical card, and it had no problems with XP. I'll try to find the driver that worked for that user. Hold on.