Leaderboard

I can't say what's going wrong in your system as I never have used Windows 2008. And I don't know whether New Moon 28 targets this OS at all. Under Windows XP, the "Make New Moon the default browser" button has always worked like a charm. And if this feature didn't work in other browsers, I either edited the respective registry entries manually or I used the tool Default Browser 1.8. Unfortunately, this tool is for Windows XP only but maybe, there is also a tool which does this job under your OS. Here are important registry locations which were set by me for using New Moon 28 as default browser under Windows XP: HKEY_CLASSES_ROOT\Applications\palemoon.exe HKEY_CLASSES_ROOT\http HKEY_CLASSES_ROOT\https HKEY_CLASSES_ROOT\ftp HKEY_CLASSES_ROOT\PaleMoonHTML HKEY_CLASSES_ROOT\PaleMoonURL HKEY_CURRENT_USER\Software\Classes\Applications\palemoon.exe HKEY_CURRENT_USER\Software\Classes\http HKEY_CURRENT_USER\Software\Classes\https HKEY_CURRENT_USER\Software\Classes\ftp HKEY_CURRENT_USER\Software\Classes\PaleMoonHTML HKEY_CURRENT_USER\Software\Classes\PaleMoonURL HKEY_LOCAL_MACHINE\SOFTWARE\Clients\StartMenuInternet\Pale Moon web browser HKEY_LOCAL_MACHINE\SOFTWARE\Clients\StartMenuInternet\PALEMOON.EXE Under the registry path HKEY_LOCAL_MACHINE\SOFTWARE\Clients\StartMenuInternet all registered standard web browsers are listed. So if you want to be offered a standard browser, you have to enter the corresponding one there. BTW, New Moon's native function for setting it as default browser is SetDefaultBrowser(). When checking its source code, you will exactly know what actions the "Make New Moon the default browser" button performs.

... So far, I have resisted selling my soul to Google by registering an account with them (yes, I do use their "services" occasionally, but only as an "anonymous" user ; I do not even own an Android device ), but that would be "the last straw on the camel's back" for me if a Google account becomes now mandatory to grab a local copy of a YT clip (via yt-dl, yt-dlp, etc.) ; not to mention that downloading while being logged-in is a sure recipe for Google's AI to (b)lock your YT account eventually (lots of such reports inside the yt-dl/yt-dlp GH trackers) ...

For yt-dlp, I use no UA parameter and everything works. For youtube-dl, I use: --user-agent "Mozilla/5.0 (Android 14; Mobile; rv:128.0) Gecko/128.0 Firefox/128.0" But it doesn't seem to work any more... Relevant issue: #32905.

@feodor2 Unfortunately, I have to report that the website amazon.de is no longer working in Mypal 68 as before. I tested it in both versions 68.14.4b and 68.14.5b. Here is one link as an example: https://www.amazon.de/Original-Blumax-DMW-BCG10E-Panasonic-DMC-TZ31/dp/B00I04P3ZU?nsdOptOutParam=true&sr=8-3 When I try to open this page, the loading process is a torture compared to how it was months ago. It always stays at 100% CPU utilisation regardless of whether the website has been fully loaded (or appears to be fully loaded) or not. Although my hardware is weak (single core CPU Pentium 4 Northwood 2.8 GHz), amazon.de has worked tolerably well in Mypal 68 in the past. BTW, in New Moon 28, this site is loading much faster and comes to an end without 100% CPU utilisation. As far as I noticed, the issue is related to the loading of images and media. Even the additional use of uBlock Origin couldn't help, unless you neuter the site to the point of informationlessness. P.S.: With the help of additional user scripts and own filters for uBO, I was able to tame a bit the amazon.de website. Now, the loading process finally ends at some point. But all loaded images and media definitely lead to extremely higher processor utilisation than before. The entire loading process still takes some minutes.

I've updated youtube-dl, applying the pending fix for YouTube. See: https://github.com/ytdl-org/youtube-dl/pull/32987. You may have to pass cookies (from logged in account) and the following user agent: --user-agent "Mozilla/5.0 (Android 14; Mobile; rv:128.0) Gecko/128.0 Firefox/128.0" --cookies "C:\Documents and Settings\$USER\Application Data\youtube-dl\cookies.txt"

The air in Canada has become drier this winter. I has to buy a humidifier.

Usually they dim when old, or become orange/yellowish.

But then again, not worth if it's very old, better find the same model on the used market. As it could be costly to buy the good caps.

A very unfortunate event indeed! If you already checked it with another PC (not only the card), then I'd start with more in-depth testings, like replacing the caps and measuring their capacity/ripples.

My French brother, please accept my deepest condolences. That loss is so tragic, no words can describe. And yes, be on your guard with scammers, they usually know our weak places, where to push. Prenez soin de vous ! / Take care.

Forgot to tell, It's good to have clear thinking people on MSFN, (I just made you a compliment). So, please go on, keep up.

I agree with you, at this point we still know nothing, I too want to see more proof! System kernel is way too important to install from unknown sources! I'd prefer the developer to have a verified MSFN account, I don't trust github after reading their TOS.

Yes! The flags have updated themselves to reflect the real location. So now we all know Tommy is from Canada. How far from me is still unknown though.

No mystery, sorry! And I wrote about it 1.5 years ago. https://msfn.org/board/profile/439498-karla-sleutel/?tab=field_core_pfield_18

Would be about the level of nVidia G210, at best,

... The separate standalone mpeg-dash streams are in a media format/container (iso6dash) that IS NOT compatible with old media players (such as mpv from back in 2015 ); when you download via yt-dl and a recent-ish build of ffmpeg is used, the separate media streams are muxed together into a standard iso MPEG4 container that has been supported for at least two decades... The 360p encode is itself by default packaged (and streamed) inside a "proper" MPEG4 container (with its mov atom placed in the beginning of the MP4 file) ...

I believe that updating Chrome components in the background on Windows XP may now be more of a problem than a benefit. It's been so many years since support for Chrome on Windows XP was discontinued that components for this operating system are no longer being developed, let alone checked for compatibility. Thus, using the flag --disable-component-update seems to me a logical consequence.

As I already wrote, no components were installed in my Thorium installation. The list is simply empty. It was just an idea. Personally, I use the flag --disable-component-update.

@Dave-H I have just seen your recently opened issue "Side by Side Error Recorded in Windows XP #85"on GitHub. I then checked my event logs but can't see any corresponding entries so far although the sub folder screen_ai also exists in my USER_DATA folder including this ominous chrome_screen_ai.dll file. Furthermore, I checked my installed components under chrome://components/ but there are none. Maybe, you simply delete or rename the complete screen_ai sub folder and use the command line flag --disable-component-update for the next browser start.. It might be necessary to de-register the chrome_screen_ai.dll file, too. I can't say whether this will help you, but you could give it a try.

I know these command line flags. Personally, I use the extension Animation Policy in Thorium. By using this extension, you are able to exactly adjust via a toolbar popup how the animations are supposed to be handled by the browser. Thus, the user has the possibility to let an animation play or stop from inside Thorium at any time without editing the flags and restarting the browser.

After some tests, I would even say that the loading behaviour of different websites also has been improved by the updated Chrome XP API Adapter. More test are necessary, of course.

As already reported in the Supermium thread by @rereser, a new progwrp.dll file was released for Supermium. This file is the Chrome XP API Adapter and is supposed to be compatible with Thorium. Therefore, I replaced the old version 1.1.0.5002 by the new version 1.2.0.5035. The file size from version 1.1.0.5002 to 1.2.0.5035 has been significantly reduced by an incredible 82%. In any case, I can confirm that now the browser start is much faster and smoother than before. I think this is a great improvement.