Leaderboard

Temporary deleted 02.05.2025: I'm revisiting this topic back, now I 99% know what I need to do to get it running on Windows 7 SP0. EventSetInformation seems to be able to be overridden by TraceSetInformation to the extent of making the browser work, hence I will have to make it so that EventSetInformation is loaded dynamically, and TraceSetInformation is used if it fails. I probably also already know how to use YY-Thunks, which will allow us to run this on Vista.

It's still very old. Let's see, 11th of January, 2017 is over 8 years old, not to mention it's a Quadro card. And you were going to stream on Supermium with your cards!?! You'd be outright blocked on Netflix. lol The driver support was dropped in 2019, 6 years ago, it's hopeless. Here's an old article, and even then they already demanded GTX 1050 (which still gets the drivers, unlike all of yours). GTX 1050 4GB is only for the poorest members of our society. https://www.ncesc.com/gaming-pedia/what-gpu-does-netflix-use/

Garbage files/folders you can safely delete from this browser. Sites work, video plays without 'em, logging in also works. Faster startup. ("gut feeling"). lol. What are these? Who the Hell knows. chrome_proxy.exe chrome_pwa_launcher.exe chrome_wer.dll d3dcompiler_47.dll eventlog_provider.dll Extensions IwaKeyDistribution libEGL.dll libGLESv2.dll MEIPreload notification_helper.exe PrivacySandboxAttestationsPreloaded VisualElements vk_swiftshader.dll vk_swiftshader_icd.json vulkan-1.dll

You mean spent? Because it sounded you're not going to do it any more. I'm very grateful you helped to bust down the odd Supermium brightness with proof, and its' clearly seen on your screengrabs. The fact you don't see it on your alleged 40 years old Dell is not relevant, so it's not "Circle", there's nothing to go around in circles about. We see it. and it's enough, so nothing was done in vain. Here I asked you: did you notice, and no need to open up a full-blown investigation about this browser. Just a quick answer would be enough. Thanks.

It is a H810 ITX board, need to disable above 4G decoding，than use wrap seabios to load the old system. win7 can work well now. But dos/xp need to fix some bugs.

very happy to see it is still being worked on thanks kasumi

@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.

@feodor2 Although Mozilla does and has done things to their Firefox browser for years that I personally think are terrible, certain features, even if they are considered deprecated and not secure, will be retained for compatibility reasons. That's something positive. On the subject of XBL and binding, what about the CSS property -moz-binding in your new release? This property is also used by Custom Buttons. For example, for the code editor in the file codeeditor-cbeditor.css: cbeditor { -moz-binding: url(chrome://custombuttons/content/cbeditor.xml#custombuttons-codeeditor); } #accelkey { -moz-binding: url(chrome://custombuttons/content/cbeditor.xml#accelkeytextboxbinding); } Can Mypal 68.14.8b even cope with this?

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.

I, for one, instead of having pointless arguments on the forums, came to how to avoid compilation errors that appear (which may not be there in your case, from what I learned on the Chromium forums, the problem can occur randomly depending on a great many factors) For start, autoninja -C out/chromium135r72 ..\..\chrome\windows_services\elevated_tracing_service\elevated_tracing_service.cc^^ When the error occurs, you will see the name of the directory in the system %TEMP%, e.g. tmpxxlxwh5i, and the destination path where you should paste the files contained in it. Then autoninja -C out\chromium135r72 ..\..\chrome\updater\app\app_server_win.cc^^ and repeat the previous step, except that now the directories in the temp folder will be three. This way I will be able to compile uninterrupted while I am sleeping or not at home. Edit: I forgot, after copying the files you need to run the command again to complete the compilation of the module. “chromium135r72” should be replaced with the name which you selected in the gn args out command

Recently, there was an almost unique case - you asked a legit, on topic question about streaming on Supermium, I answered why it's not possible, and even if Supermium buys a 10K digital key, your hardware will never get through, I also explained why - very politely, if you're insulted with the fact of having such a hardware, it's not my problem. And I honestly can't comprehend why it gets you so deep. I run a 10 years old Videocard with the initial price of 1200Euro, I feel no shame in it. I don't upgrade because newer don't have Vista drivers. What are your reasons to stay on such oldies, we don't know - Win10 has all the drivers. BTW, be careful with curses, you never know whom you wished them to. I'm a Black magic practitioner, I do séances, read books on the occult, etc.

I'm no longer surprised why you had terrible stuck-ups with the modern Supermium, whereas other members didn't! GPU with DDR3 is 2003 tech, I had a GPU with DDR3 in 200 or so, over 20 years ago. Your computer OEM simply used very cheap VRAM. At that time, GPU already had GDDR5.

Oh, and that alleged Dell 2407, or the "newest" of yours (less than 12 years old) display will never get through with the streaming on Supermium because it lacks HDCP 2.2.

@NotHereToPlayGames BTW, such a legacy Custom Buttons extension I have already provided in September of 2022 in my thread "Extensions and custom buttons for UXP browsers - Corrections, modifications, adjustments, and special recommendations" which can be found here: Custom Buttons - The extension for installing custom buttons. As already said, this version cannot be installed in Mypal 68. And here are more of those old Custom Buttons extensions you are referring to which are all incompatible with Mypal 68: https://sourceforge.net/projects/custombuttons/files/ Can be checked very easily. The good is you won't "have to dig through stacks and stacks and stacks of DVD-Rs" to find your Custom Buttons extension because with a probability bordering on certainty, those old versions, if you ever find any, won't either work in Mypal 68.

Mypal 68.14.6b - GIF image animation broken in single-process mode @feodor2 Purely by chance, I have discovered that the animation of GIF images in Mypal 68.14.6b does not work when the browser is operated in single-process mode. Of course, the preference image.animation_mode is set to the value normal. When switching to multi-process mode, however, the animation of GIF files works again. So this seems to be an issue that only affects the single-process mode. Look at my Matrix GIF image below! I should still mention that this issue didn't occur in your previous releases. Cheers, AstroSkipper

@feodor2 First of all, thanks for all your efforts! Especially for restoring the compatibility with the legacy Custom Buttons extension in Mypal 68.14.6b. At the moment, I am testing this new release and found several issues. Mypal 68.14.6b - The loading and scrolling websites issue in multi-process mode Unfortunately, I have to report that loading websites and scrolling them from top to bottom is seriously broken in my fresh installation with a fresh profile (untouched) when running Mypal 68.14.6b in multi-process mode. If scrolling to the top of this MSFN page, for example, leads to a blue window without content. Here is a screenshot: I didn't notice any corresponding errors in the browser console. I have installed the browser versions 68.14.4b, 68.14.5b and, since today, the browser version, 68.14.6b under Windows XP. The website loading and scrolling issue does not occur in version 68.14.4b or in version 68.14.5b. That means the issue started as of your new release 68.14.6b. And the general.smoothScroll preference is of course set to true which is the default value. So, this issue seems to be a more general one in multi-process mode and does not only happen if the general.smoothScroll preference is set to false. P.S.: After some more tests, I noticed that the website loading and scrolling issue doesn't seem to occur in your new release 68.14.6b when running the browser in single-process mode. In this mode, the loading and scrolling of this MSFN website here is very fast and error-free. It therefore appears to be primarily a multi-process mode issue. Maybe, this information is useful for you. At least I do hope so. Cheers, AstroSkipper

I assume you rather have a problem with a Windows XP SP3 essential security update since you didn't specify which update you are referring to. This, however, means that no one can help you.

The programme LegacyUpdate has been updated and is now available in version 1.10. Here can be found the corresponding changelog: https://github.com/LegacyUpdate/LegacyUpdate/releases/tag/v1.10.0.0 I'll also update my original post as soon as possible. Cheers, AstroSkipper