Leaderboard
Popular Content
Showing content with the highest reputation on 03/20/2025 in Posts
-
Yes I did. Why would I lie about something like that? Anyway, here is a link to a Github bug, with one of them showing a Windows 7 machine exhibiting the same symptoms. https://github.com/win32ss/supermium/issues/1263 Scroll down the page ... See the image? That's what I had. Anyway, I went back to R7. Thanks @D.Draker. That was very kind of you. Have a good day.3 points
-
Exactly! I have no idea why the author changed it to overblown white! All Chromium forks I saw to this date, had the standard brightness. And even the white colour there was pleasant, not too bright.2 points
-
2 points
-
Hi all, I'm moving to Windows 11 after using Windows 10 forever, so I'm trying out StartAllBack to see if it would fix the annoyances with the Win11 taskbar. So far StartAllBack seems to be a perfect replacement for 11 except that I have encounter a possible bug when I have multiple windows open on the same app like Chrome. If I enable LastActiveClick for windows, StartAllBack will always show the first window instead of the last active window. Below are the steps to reproduce it. Switching back to regular Win11 taskbar will function as expected. I'm using Win11 24H2 with the latest version of StartAllBack that's available for download. 1. The taskbar settings should be Always Combine and hide titles/labels, and enable click to activate last active window with the registry key [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Advanced] "LastActiveClick"=dword:00000001 2. Open a browser (e.g. Chrome) and open multiple windows of this same browser with Ctrl+N and maximize the windows. 3. Open multiple Explorer windows. 4. With Explorer window in focus, hover over to the browser app in the taskbar, and select/click on a browser window thumbnail that's not the first one to bring it into focus. 5. Click on the Explorer window in the taskbar; now Explorer window is in focus. 6. Click on the browser app on the taskbar; since the LastActiveClick reg key is active, it should show the last active window for the browser, but this doesn't happen, and it shows the first browser window instead. Is there a workaround/fix for this? I'm tempted to move back to Win10 again before doing too much configuration lol1 point
-
No. But no unnecessary security bullying when I use self-modified or unsigned extensions or themes. I don't need such Mozilla checks. They don't exist in New Moon, either. So in my case, I prefer to get rid of them. However, for the normal user, such security checks are completely ok and in certain cases even sensible.1 point
-
I just now saw, there is a build for Vista, try it, maybe it will work on 7 without SP1: https://github.com/e3kskoy7wqk/Chromium-for-windows-7/releases/tag/136.0.7063.01 point
-
This should be possible with 3.9.6 with StartMenuMonitor=2 registry setting1 point
-
Pre-release of ytBATCH for Windows XP - A fork of ytBATCH by AstroSkipper ytBATCH is a YouTube video and music downloader script (actually rather a batch script ensemble) developed by eppic on GitHub: https://github.com/eppic/ytBATCH. Therefore, credits to eppic for his great work! Unfortunately, the original ytBATCH is not compatible with Windows XP as it uses more recent versions of youtube-dl and yt-dlp, and even failed to download any of these releases under Windows XP due to commands which do not work under this OS. Additionally, it needs ffmpeg which can't be downloaded any longer by this script, either. I changed and added a lot of code inside the batch files of this script ensemble to get it working under Windows XP. For this purpose, I implemented the use of youtube-dl and yt-dlp releases created by @nicolaasjan which will now automatically be downloaded by ytBATCH and updated when needed. At this point, logically credits to @nicolaasjan for his great releases! Furthermore, I implemented the last ffmpeg release in version 7.1-2362 created by @Reino which will now also automatically be downloaded by my ytBATCH fork. And therefore, credits to @Reino for his great releases! An updating of this version by ytBATCH is not needed as @Reino unfortunately abandoned creating XP-compatible ffmpeg releases. To make the download of these files by ytBATCH working again under Windows XP, I added the last XP-compatible version of wget to this package. Additionally, I inserted the 7-Zip command line tool in my package for unpacking the downloaded files. When starting the original ytBATCH script, another issue happens under Windows XP. The script needs the DOS command CHOICE which is not part of ytBATCH and doesn't exist under Windows XP by default. At least, it is the case on my Windows XP installation. Therefore, I added the choice.com file to this package. All in all, I changed many different things but now, ytBATCH is working fine under Windows XP. The advantages of ytBATCH are the low consumption of resources, the high download speed, the custom settings such as preselecting the video and audio formats, their quality, the download of subtitles, the embedding of metadata and thumbnails and so on, and most notably the possibility of adding command line options to youtube-dl or yt-dlp which all can be saved inside ytBATCH. I personally love this script ensemble which can be modified to the needs of the users at any time since batch scripts are fully editable. I rebranded my fork of ytBATCH and called it ytBATCH for Windows XP. Most probably, it will also run under other OSes like Windows Vista or Windows 7 but I didn't test it. The current version of my fork is based on the latest ytBATCH version 2.9.2. Here are some screenshots: And here is the download link for the pre-release of ytBATCH for Windows XP 1.0 (aka 2.9.2): https://www.mediafire.com/file/6c9hfkfpiwextf0/ytBATCH_for_Windows_XP_2.9.2.7z/file The use of ytBATCH for Windows XP is actually self-explanatory and well documented on ytBATCH's homepage: https://github.com/eppic/ytBATCH. Extract the downloaded archive file to a location of your choice and start the ytBATCH.bat file located in the main folder. A prompt appears asking to install ytBATCH. You can now either install ytBATCH to AppData and generate a shortcut or keep ytBATCH as a portable programme. I personally prefer the latter. The download of all necessary files will then automatically start. All files will be unpacked and saved in a freshly created exe subfolder. I have to mention at this point that the user of such scripts should not only be able to click with the mouse. This script is mainly controlled by the keyboard. Solely the YouTube link to be downloaded can also be inserted using the mouse. My recommendation is to check all options inside this script by pressing corresponding keys to set it optimally. I did that, and it works simply great, especially on my old, weak computer. To make even better use of it, you should be a bit familiar with youtube-dl and yt-dlp. The latter is documented in detail on its homepage https://github.com/nicolaasjan/yt-dlp. Any opinions, questions or experiences on my fork are of course welcome here in my thread. If you encounter any issues with my fork, please post it only here and not on GitHub! This fork is unofficial and not supported on GitHub. In any case, I hope ytBATCH for Windows XP can be useful for YouTube users under Windows XP. Greetings from Germany, AstroSkipper P.S.1: If ytBATCH should be updated on GitHub at some point (the last update was in June of 2022), you are well advised not to perform such an update, as otherwise all my changes would be overwritten, and ytBATCH for Windows XP would become non-functional under Windows XP. To be honest, there is no reason for such an update under Windows XP. Maybe, I will deactivate this function in ytBATCH for Windows XP in general in a further release. P.S.2: I have changed the version number assignment. Consider my pre-release ytBATCH for Windows XP 2.9.2 as version 1.0! This means: ytBATCH for Windows XP 2.9.2 = ytBATCH for Windows XP 1.0.1 point
-
That's why I do not get any security warnings when opening the Add-ons Manager :1 point
-
You are absolutely right. If any security patches can be applied by @feodor2, then this should be done in any case. Of course, one should also be aware that activating user scripts or using certain hacks has unfortunately a negative impact on the security of Mypal 68. I, for example, use both. But I also know what I'm doing.1 point
-
Updating the embedded root certificates of Mypal 68 is of course a very good idea and important for using this browser in the future.1 point
-
1 point
-
Sorry, I didn't see that topic before, In China, we have an old saying: Listening is false, seeing is true1 point
-
@Jody Thornton is a trusted member, moi fellow Canadian friend, there's no reason not to trust Jody. Are you sure you write about the 132 R1 re;ease?1 point
-
1 point
-
Oh! So the *agenda* here on this Circle Jerk Discussion is for the developer of Supermium to go out and get the same exact video driver, the same exact monitor, the same exact everything, so that all the rest of us no longer have to listen to the BIATCH AND MOAN about "brightness" that shows up every three weeks and lands itself in every topic from media players to web browsers.1 point
-
Looks good in Vista, I use it. And how would you know it, you don't use, never used Vista.1 point
-
https://github.com/win32ss/supermium/issues/1006#issuecomment-2478023725 "Unfortunately, Supermium will need a VMP certificate to play back most content using Widevine."1 point
-
Read the whole thread. Too many folks keep speed-reading and jumping over the important parts. The INACTIVE WINDOW is light gray. But that light gray in Official Chrome is changed to BLUE in Supermium. The "offense" is that a light gray is changed to (and I *quote*) "piercing white". Blue does not equal "piercing white", SO THE INACTIVE WINDOW (TAB BAR) IS *NOT* THE "OFFENSE". By all means, ask the developer himself. He's going to tell you the same exact thing that I've already told you - NO COLORS HAVE BEEN CHANGED. Font rendering has been changed, but that is NOT what is being "complained about". Until we find proof in a CSS DECLARATION, then you "dark mode" folks can keep running in circles all you want (none of you use Supermium anyway). I, on the other hand, have a vested interest in Supermium. I need a PORTABLE chrome-based for a laptop being set up for streaming. Some have had success with Supermium+Widevine, others have not. I'm still in-process.1 point
-
THINK ABOUT IT !!! If we are to "report" something to GitHub and "claim" that a color changed, THEN IT IS ON US TO FIND THE RGB/COLOR CHANGE WITHIN THE CSS DECLARATIONS !!! Then, AND ONLY THEN, can we ask the developer, "Why did you change RGB (a, b, c) to RGB (x, y, z)?"1 point
-
If I was bashing on an old version, then yeah. In this case, the brightness keeps climbing up with every and each release. Like the author's monitor was closer ans closer to the deathbed, Or his eyesight rapidly declined.1 point
-
1 point
-
No more for me. Everything shows *IDENTICAL* for me (anti-aliased font difference YES, *expected*, color brightness difference NO)! I'll let you "dark mode" folks fight over this one. And fight... And fight... And fight... My VMs are closed for the day. Supermium targets pre-10 so that font may likely not even be Segoe UI whereas Official Chrome would be. As this really does come up *ALL THE TIME*. Kind of gets old, in my not-so-humble-opinion. I've shown side-by-side out-of-the-box, nothing more I can do, some will always see what they want to see, hear what the want to hear. It's a FONT RENDERING ISSUE, not a brightness issue. THERE IS A DIFFERENCE. It's called "sub-pixel" rendering. Moving on now... "Toodles"...1 point
-
Yes, I am. The key needs to be purchased for 10 000 Canadian dollars or so, it was explained by the win32ss in the issues thread. I'm sorry, I won't browse through 16183218318 pages of issues. But you're very welcome.1 point
-
For the record, I've given up on trying to keep up with all of your "brightness complaints". They pop up ALL THE TIME and I stopped following if the complaint is a button on a web site being rendered this way or that way or if the complaint is a blue color (correct spelling, I'm allowed to use US spelling even if folks around here think everybody should use non-US spellings, but I digress). One moment, I'll load up two brand new VMs that have never seen Supermium or Brave and do a side-by-side color-check.1 point
-
Already tried that. Does not work. Each and every launch reaches out to "go-updater.brave.com". Removing that string from chrome.dll doesn't even stop the each and every launch from contacting "go-updater.brave.com".1 point
-
Agreed! Reminder that I only use Supermium from inside a VirtualBox VM. I monitor the project and continue to have high hopes for Supermium. Though I am a bit skeptic that I will ever use it on my host OS [reminder, I'm on Win10]. Yes, my Supermium cache folders are "bigger" than my Ungoogled Chromium - but not "2/3 times" and not "disastrously high". Edge uses all of these cache folders also, I'm assuming you are aware. I should point out that some of the folders that have "cache" in their name are inconsequential and the end-user does not gain anything by preventing them. The test is to monitor their file/folder size. If the size is a couple hundred bytes, or even kilobytes, but the size is CONSTANT from NEW PROFILE, to never opened any web sites, to having several dozen tabs open, then KEEP AS IS, there's no "tracking". If a first-run "cache" file/folder is the same size and doesn't change after opening dozens upon dozens of tabs, then there is no "tracking". I *keep* them! Undo read/write/erase disc drive activity to just have the SMALL file recreated all the time.1 point
-
Supermium uses all of those folders in the same way "as that of Chrome". But you should NOT have a "disastrously high" cache IF YOU HAVE SET THE DATA DELETION ON CLOSING THE BROWSER. Personally, your BEST route of CONTROL is to use a LOADER. Supermium does not ship with a LOADER and I myself do not use Supermium "as it ships". This is for every end-usser to LEARN and ADJUST. No different than any browser, as far as that goes. There are "nuances" with ANY browser that only those that USE will LEARN and tweak accordingly. If you really really really have a vested interest in using Supermium, then you would already be studying how to resolve such nuances. Bottom line, my Supermium/Chrome/Chromium cache is NOT "disastrously high" but that is also because I have taken steps to NOT RUN AS IT/THEY SHIP. I don't think it is the responsibility of the Supermium Developer to "also" create a "loader" - but speaking solely for myself, I would never use it without a "loader". To each their own...1 point
-
Yes. Very interesting. Which version of the Custom Buttons extension did you install in Mypal 68? And which method of installation did you apply to get this version fully working in Mypal 68? And since we're on-topic now, you're welcome to be as detailed as possible. In any case, I'm very curious to read what you will report. BTW, the UXP browsers New Moon and Serpent are of no interest here as Mypal 68 is a Quantum browser.1 point
-
@feodor2 Inside the omni.ja file, you changed, for example, the chrome://browser/content/browser.xul file in Mypal 68.14.4b to the new chrome://browser/content/browser.xhtml file in Mypal 68.14.5b. Without any announcement and information, such changes are predestined to cause problems. Now, nothing surprises me anymore. Edit: I removed the image with a toolbar and icon issue as it was caused by one of my scripts which is now broken in Mypal 68.14.5b.1 point
-
For using this modified script, the @updateURL should be removed as the modification will be overwritten again with the next script update. I use the original script to receive regular updates and to see how the script develops. And all videos I tried to play worked without any problems in New Moon 28. No crashes and no resets after a few seconds as it was before. In any case, YouTube videos are working fine again in UXP browsers and especially in New Moon 28.1 point
-
1 point
-
You didn't follow the discussion. The search box issue only appears when using the VORAPIS V3 frontend and not the original YT interface.1 point
-
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.1 point
-
Use nlite to slipstream AHCI Driver AHCI/RAID Driver: http://www.win-raid.com/t29f25-Recommended-AHCI-RAID-and-NVMe-Drivers.html [Thanks a whole lot to Fernado][Greatest tech person] Graphics Driver [intel HD Graphics]: https://downloadcenter.intel.com/download/22875/Intel-HD-Graphics-driver-for-Windows-XP32-Embedded [This are said by intel for embedded but working well with normal xp sp3] LAN Driver [intel]: https://downloadcenter.intel.com/download/24555/Intel-Ethernet-Drivers-for-Microsoft-Embedded-Operating-Systems [Thanks a lot to misha 32 of winraid forum] Chipset [intel]: https://downloadcenter.intel.com/download/23061/Chipset-Intel-Chipset-Device-Software-for-Intel-Desktop-Boards1 point