Leaderboard

After 10 hours of compilation, I received errors. Then I would face another 10 hours, and in the meantime more errors would appear. Not for my patience, I pity the money for more powerful hardware, as long as I can't compile without errors, and I'm not able to do that at the moment at this compilation rate. I apologize to the users I disappointed, apparently I'm not smart enough after all and despite following the instructions I keep doing something wrong all the time

I always do this with Total Commander.

It's now a question for users whether ungoogled or Vista support is more of a priority. My computer can take more than 24 hours for one compilation. Unfortunately, in the previous system installation and previous software setup, I made such a mess of things with the trial-and-error method (and doing some things at my own discretion, not how the tutorials dictate) that something went wrong during compilation. This time I found much better tutorials and have experience from the previous tries. Compiling Chromium in theory is very simple, but very many things can go wrong. Now I downloading the entire repository with every possible version from the main branch. You can also fetch with the command -gclient sync --revision src@137.0.7116.0.

Could there be strings attached?

We are looking forward to it! Will the Ungoogled patches be also applied?

I have updated the virus definitions of my ancient version of Kaspersky Ok under WinXP via VPN. 16,832,335 signatures, database release date 4/12/2025 11:14 AM. I have used OpenVPN v2.5.4 (schtrom mod) under WinXP, with a .ovpn config file by ExpressVPN, VPN server location in Ireland. TAP-Windows Adapter V9 was set in Device Manager, Advanced tab, Media Status to Always connected. I have used for this signature update a 7-day free trial by ExpressVPN. ExpressVPN worked fine for me with Kaspersky and also with uTorrent under WinXP, but not with eMule, no port forwarding. The screenshot below shows the Update running via VPN and the System Tray with the green [=connected] OpenVPN icon. The blue shield of the Kerio v2.1.5 Firewall icon shows a green arrow indicating the Permitted Outgoing Connection during the signature update. The ability to obtain signature updates of my ancient version of Kaspersky via VPN may perhaps be of use in some countries

I will at least write a compilation tutorial in Windows and for Windows What you need: - Windows 10/11 (before 10 20H1 additional steps with SDK required) - Visual Studio 2022 (can be free Community), git and Python (minimum 3.9.0) Run the Visual Studio installer from CMD with the following arguments. PATH_TO_INSTALLER\VisualStudioSetup.exe --add Microsoft.VisualStudio.Workload.NativeDesktop --add Microsoft.VisualStudio.Component.VC.ATLMFC --includeRecommended. Then install the Windows 11 SDK in the latest available version. Install git and python. In Git Bash, configure: git config --global user.name "My Name" (optional) git config --global user.email "my-name@chromium.org" (optional) git config --global core.autocrlf false git config --global core.filemode false git config --global core.preloadindex true git config --global core.fscache true git config --global branch.autosetuprebase always git config --global core.longpaths true Now we will take care of downloading depot_tools. In my example, you first need to create a src folder in C:/. Then in the CMD: cd C:\src git clone https://chromium.googlesource.com/chromium/tools/depot_tools.git Next add the environment variables: DEPOT_TOOLS_WIN_TOOLCHAIN=0 vs2022_install=C:\Program Files\Microsoft Visual Studio\Community (or other edition) NINJA_SUMMARIZE_BUILD=1 Edit the "Path" variable with path to depot_tools (eg. C:\src\depot_tools) and move it up before any Python installation. Next simply run the gclient command in CMD, it will download the basic components needed. In the folder where depot_tools is located, create a directory, for example, named chromium. Go to it in the console and run the command "gclient sync" if you want to download the latest version, or gclient sync --revision src@xxx.x.xxxx.xx (the version number you need). Use --no-history parameter at the end of command, downloading entire history, including branches and tags is about 50GB, I think it's not worth it. Now we are ready to compile. Go to the src folder inside the folder we named chromium earlier in the CMD, and run gn args out/default (you can name it whatever you want). This will open your default notepad, where you can set all the arguments. If compiling under Windows, I recommend using at least the following: is_official_build = true is_component_build = false is_debug = false target_os = "win" target_cpu = "" (x64, x86) clang_use_chrome_plugins = false (if compiling build with e3kskoy7wqk patches only) symbol_level = 0 v8_symbol_level = 0 blink_symbol_level = 0 proprietary_codecs = true ffmpeg_branding = "Chrome" chrome_pgo_phase = 0 You can also add arguments about Google API keys or widevine google_api_key = " " google_default_client_id = " " google_default_client_secret = " " enable_widevine = true ignore_missing_widevine_signing_cert = true enable_media_drm_storage = true Save the args.gn file and close notepad, gn will generate the necessary files. Now just use the autoninja -C out/Default (you can also add the parameter "-j X", where X is the number of clang compiler processes)

The current name is better.

I have just managed to start compiling for now a clean Chromium 137.0.7116.0 without any patches, just to be sure that no problems will occur. If successful, my intention is to apply all the patches from https://github.com/e3kskoy7wqk/Chromium-for-windows-7/tree/main/137.0.7116.0 and restore Vista and 7 SP0 compatibility, and 32 and 64 bit versions using https://github.com/Chuyu-Team/YY-Thunks/ - what the author of Chromium for Windows 7 does not intend to continue for some reason, despite the fact that it is the simplest and very well working solution.

14 watt is pretty much due to the additional memory size, otherwise it'd be 11 watt, too.

I use Windows XP on my old, beloved but weak Pentium 4 computer. I therefore prefer another approach since the PowerShell reacts very slowly on this machine: -- YouTube Link Resolver for VLC with Separate Video and Audio URLs -- Place this script in VLC's lua/playlist directory function probe() -- Check if the input is a YouTube link return vlc.access == "http" or vlc.access == "https" and (string.match(vlc.path, "youtube%.com") or string.match(vlc.path, "youtu%.be")) end function parse() -- Construct the full YouTube URL local youtube_url = vlc.access .. "://" .. vlc.path -- Path to yt-dlp executable (modify as needed) local yt_dlp_path = 'yt-dlp.exe' -- Start cmd hidden and ... local cmd_hidden = 'hidecon cmd /c &' -- Construct the command to get the direct video and audio URLs local cmd = string.format( '%s %s -g "%s"', cmd_hidden, yt_dlp_path, youtube_url ) -- Execute yt-dlp to get the direct video and audio URLs local handle = io.popen(cmd) -- Read video URL (first line) local video_url = handle:read("*l") -- Read audio URL (second line) local audio_url = handle:read("*l") handle:close() -- Trim any whitespace video_url = video_url and video_url:gsub("^%s+", ""):gsub("%s+$", "") or "" audio_url = audio_url and audio_url:gsub("^%s+", ""):gsub("%s+$", "") or "" -- Log the resolved URLs vlc.msg.info("[YouTube Resolver] Original URL: " .. youtube_url) vlc.msg.info("[YouTube Resolver] Video URL: " .. video_url) if audio_url and audio_url ~= "" then vlc.msg.info("[YouTube Resolver] Audio URL: " .. audio_url) return { { path = video_url, name = vlc.path .. " (Video)", options = { -- Add audio URL as input option ":input-slave=" .. audio_url } } } else vlc.msg.warn("[YouTube Resolver] No separate audio URL found. Playing single URL with both video and audio.") return { { path = video_url, name = vlc.path .. " (Video + Audio)" } } end end The tool I use is hidecon and is very fast. You can get it here: http://code.kliu.org/misc/hidecon/

Next time, just delete "iCafe" folder, before you install, solved.

For me, the official releases are always decisive when assessing the compatibility of programmes. It's great that this problem has now been fixed in the nightly version. However, my statement was clear: Nevertheless, I will give the current nightly from 09.04.2025 a try. Therefore, thanks for the hint!

The official release of VLC Media Player in version 3.0.21 is not compatible with Windows XP, even not with service pack SP3. This has been well known for a long time. So, the last official XP-compatible version is 3.0.20. But so far this version runs very well under Windows XP. And with the new youtube.lua script, links to media files on YouTube work again.

Hmm, how fascinating. It must be something about your specific hardware that only works best on Vista, and malfunctions (and sounds bad) on any other version. My hearing is fairly good, and I still can't really tell the difference between 44.1 and 96 or 192, so I just go with 44.1 to save on disk space. MP3 at the highest possible bitrate (320) is tolerable, I find, but once it starts dropping below 192, it becomes increasingly awful. My preference, of course, is uncompressed WAV or AIFF (I guess FLAC is supposed to be good, but I tend not to use it much because support for it isn't as universal as it is for MP3 and WAV). c

That's strange. I've never had any trouble with sound on XP. All cards I've tried function as they should, and I could set 44.1kHz (or any other supported sample rate) easily. Of course, I've often used USB or Firewire (IEEE1394) audio interfaces with ASIO support for top sound quality, and they usually include decent drivers; in my experience, I've found that virtually all of the so-called "HD" sound systems built into most XP-era motherboards have stupidly bloated and half-broken drivers and often are hideously noisy and cheap sounding regardless of driver or Windows version (if anything, newer Windows versions with newer drivers sound worse as the already mediocre support the bad drivers have deteriorates further). Perhaps your drivers weren't fully compatible or something was wrong with your sound card? c

I am using this library for now for personal use and temporarily. I will try to use advapi32 from SP1 Absolutely zero success, even though advapi with SP1 does not lack dependencies in SP0. BTW I forgot to mention, but in v137 the flag to disable clients hints actually worked, including on Vista. Besides, every time I use these libraries, I mention that they come from Supermium. And the fact that I use them to run other, better browsers at the moment, is just my business. As long as I don't create ready-made mods and make its libraries available with them (no, I won't do that, I will prepare simple tutorials at most)

I like how XP can be "tamed" and with a few simple settings, the whole "fisher-price" theme can be disabled, after which it looks and feels basically like an upgraded version of Windows 2000, especially before SP2. c

Windows has been going downhill since Internet Explorer integration to Windows 98, and it also had ads, known as "the channel bar". XP had the fisher-price theme and pre-SP2 versions would nag about signing up for .NET passport service and other things<LINK>, but nothing compares to the awfullness of Windows 11. It shouldn't have existed in the first place! Who in the world thought moving the right-click on file menu options like rename as some stupid icon was a good idea, and why is the start menu re-designed again and now in the middle of the taskbar and not where it's supposed to have been since Windows 95? It's as if the people who designed it have never even used Windows and have no idea about it! They even removed features such as clock with seconds in the calendar 'app', something even Windows 10 has! I guess they needed extra resources for hoarding more data and telemetry for their stupid overhyped 'AI', even though it existed years ago, but now it's 'trendy', so everything needs to have it.

Just for your information! All solutions, be it UC.JS scripts, extensions or CSS stylesheets, I have posted here are definitely working up to the version 68.14.4b. Unfortunately, the most recent version Mypal 68.14.5b causes breakages. (German saying. Translated: There is the worm in it!) Therefore, be careful when updating Mypal 68! A backup of your profile should be done first. Do not post here any issues regarding this version! Mypal 68.14.5b contains changes which break different things like extensions, scripts and styles. Therefore, it should be used with caution in production systems. I have installed it for testing purpose only and for reporting issues. All issues should be reported in the Mypal 68 thread or to the issues on GitHub.

The Custom Buttons extension worked fine in Mypal 68 from the very first release until the previous version 68.14.4b. @feodor2 also has this extension available and can certainly test what's going on. In any case, he has made significant changes. The menu bar is also affected and no longer behaves as it did before. This may also be one of the reasons why some of my CSS stylesheets no longer work. Same applies to the Add-ons Manager. P.S.: @feodor2 And FYI, I also tried xiaoxiaoflood's method you recently pointed to and installed the boostrapped version of Custom Buttons (this extension always comes in two different versions). In this case, the extension options appears again in the Add-ons Manager (no error in the Browser Console in terms of the boostrap.js file) but when installing custom buttons, none of them are available. Although they are listed under the entry Custom Buttons in the Add-ons Manager, they are simply not accessible and their tool bar icons missing in the Customize window. Same to the Custom Buttons menu in the main toolbar. As you may know, Custom Buttons is an extension that also runs in newer Firefox versions up to the very latest. BTW, all was tested by me in a clean, fresh profile. If you need all the no longer working stuff, please let me know. I will then upload it for you. P.S.2: Furthermore, new errors can be found in the Browser Console compared with your previous release, even when opening the about:preferences page. Since you haven't been around here since 27. October, and the bugs are plentiful and serious, I even jumped over my shadow and reported it to your issues on GitHub to make sure you were aware of the problems with your new release.

Hi @feodor2! Thanks for your new release and all your efforts to improve Mypal 68! Unfortunately, I have to report that my beloved Custom Buttons extension is no longer working due to the changes you made in Mypal 68.14.5b. Furthermore, some UC.JS scripts have stopped working. Same applies to some CSS stylesheets. All of them have been working fine in Mypal 68.14.4b but in your new release, they do not work anymore. Although the Custom Buttons extension can be installed, the extension options is missing and when installing some custom buttons, they do not appear. Neither they are listed under the entry Custom Buttons in the Add-ons Manager nor their tool bar icons are shown in the Customize window. The CB menu in the toolbar to create buttons is also missing. The Browser Console shows errors when reading the boostrap.js file of this extension. Try it yourself as you already have the Custom Buttons extension! At the moment, I will stay with Mypal 68.14.4b. Too much is not working in Mypal 68.14.5b.

I can't say if these extensions I found do their job correctly in modern browser. This thread is about Mypal 68 which of course isn't a modern browser. It is more an old browser modified to be a bit more recent, especially its JavaScript engine. So, do you look for such an extension targeting Mypal 68?

In my opinion, even XP is a crappy version of Windows! The only reason it isn't is if you know how to tweak it, optimize it, axe the extras, et cetera. Which is the same exact thing to be said of ANY version of Windows! ie, you're not really running XP, your running XP plus Windows 10 Firewall Control Plus XP 7.5.105.217, plus who knows what else, that's not "technically" XP.