NotHereToPlayGames

Here's a brief height comparison for a WinXP skin I've come up with for 360Chrome. I focused primarily on tabs in the middle as I prefer my WinXP applications to have a standard title bar and standard XP min/max/restore/close icons. I'll post files and instructions over the next day or two.

Added an "update pack" to first page. "Mileage may vary".

DISREGARD. This release is a GIGANTIC step BACKWARD as far as an English release goes. "Inspect" has reverted to Chinese. And "simple" (albeit minor) fixes no longer properly attribute themselves to the embedded "lookup tables" (ie, capitalizing the "s" in the Options Page "UI style" and "Personal stuff"). Minor, I know, but evidence that "lookup tables" no longer work (which I suspect is the root cause for the Chinese contained within "Inspect" but I'll not be digging into it myself. I will be sticking with build 2206 for now and may revisit when the next repack is released.

Updated to v13.0.2212.0 https://lrepacks.net/repaki-programm-dlya-interneta/182-360-extreme-explorer-amp-portable.html

Sorry, I have no interest in Yandex. For starters, the portable version I found (17.6.0.1633) requires Win7 as opposed to XP. And secondly, it's only as new as Chrome 58 [April 2017] whereas 360Chrome v13 is Chrome 86 [October 2020]. But based on file structure of portable 17.6.0.1633, NOPE, the method can NOT be applied to Yandex.

I have a "WinXP skin" that I can upload and provide installation instructions if there are enough folks interested.

Here's one -- https://lrepacks.net/repaki-programm-dlya-interneta/182-360-extreme-explorer-amp-portable.html

Odds are it is the website you are downloading from. Try a different download from a different website.

There's a "million" reasons that give that cert warning. Proxy server, revoked certificate, lack of WinXP updates, et cetera ad nauseam. google.com.hk shows up perfectly fine for me. Also, your screencap shows an instance of Mypal / New Moon / Pale Moon running -- what does it show for google.com.hk? And if you Mypal / New Moon / Pale Moon is NOT using a Proxy, then make sure that 360Chrome is also NOT using a Proxy.

Thanks. I have been able to track down why some skins do not have a .srx "override" file and others do. That trick lies within [HKEY_CURRENT_USER\Software\360chrome\default\ui_persist_value] keys stored in "360chrome_1.reg". Doesn't answer your original question but I learned more of the inner workings of 360Chrome :) I think your original question still seems to revolve around "http_nosafe_bar.xml" and "browser_strings.xml", both of which still contains a lot of Chinesse.

For your "skin.srx", what is your 'modified' date via file properties? Are you running the "installed" v13 or the "portable" v13?

Both of these "features" (as I understand them) sends your trackable data to a third-party, the third-party analyzes that data and then reports back if it is 'safe' or not (by their definition, not yours), then the browser proceeds based upon that reply. But WHO is this third-party, WHERE is this third-party ??? I simply do NOT "trust" either one because I don't have ANY information on HOW / WHERE / WHO "behind the scenes". When you rely on an extension such as Adblock Plus, uBlock Origin, uMatrix, Ghostery, Privacy Badger, et cetera, you have a community of users and a plethora of online reviews and critiques to base your "trust" on. In my view at least, relying on something built-in to the browser is like actually thinking that some petty "Do Not Track" 'feature' is really doing anything or that "blocking third-party cookies" actually blocks third-party cookies. I highly prefer my blacklists and my whitelists to be "local" and not sent who-knows-where and analyzed by who-knows-who. I use uMatrix and one-and-only-one list - https://gitlab.com/curben/urlhaus-filter/raw/master/urlhaus-filter.txt Then I use NoScript and only whitelist PARTIAL javascript on a small handfull of websites. If you go to 360Chrome -> Chrome -> User Data -> skin (at least that's the folder structure for the "portable repack") you should find one file with an .srx extension. If you can provide the file name for that .srx file, I might be able to see if that skin is the culprit. Or you could do so some digging on your end, the .srx will unzip with 7-Zip, PeaZip, IZArc, et cetera. There will be an .xml file (maybe two, depending on skin) and a bunch of .png files. The .xml file can be opened in Notepad++ -- look to see if the .xml references OTHER .xml files (if it does, it/they likely reside within 360Chrome -> Chrome -> Application -> 13.0.2206.0 -> skin -> skin.srx which itself will need unzipped. Which also contains http_nosafe_bar.xml and browser_strings.xml, either of which still contains a lot of Chinesse. Hope that helps.

@dencorso Are you using the "anti-tracking privacy protection" 'feature'? Or the "protect you and your device from dangerous sites" 'feature'? (I don't trust either one of them, to be honest.) Have you looked at "http_nosafe_bar.xml" that is contained inside "skin.srx" which exists in 360Chrome -> Application -> 13.0.2206.0 -> skin folder? Very close to what you have above so could be altered by alternate skins by the looks of it. What skin are you using?

You could try Roytam's "loader" and maybe it fits your needs better -- http://o.rthost.win/palemoon/palemoon-portable-loader.7z I've never actually used it so feel free to report back your opinion of it.

From what I can gather, the "libGLESv2.dll" file is needed for older graphics cards for 3D rendering. Not sure "how old", per se, as none of my computers seem to be old enough to "require" this file for 3D rendering. I don't really do a lot of 3D graphics via web browser. I used this as a test - https://www.wirple.com/bmark/ Mypal 27.9.4 scored 461. palemoon-27.9.7.win32-git-20210220-3b1d2cdd8-xpmod scored 384. palemoon-28.10.3a1.win32-git-20210220-729367b92-uxp-2b6effbf2-xpmod scored 618. bnavigator.win32-20210220-355db4de-uxp-2b6effbf2-xpmod scored 608. basilisk52-g4.8.win32-git-20210220-d9301c4-uxp-2b6effbf2-xpmod scored 645. And, drum roll, please -- 360Chrome v13 build 2206 scored 2941. 360Chrome v12 build 1592 scored 2565. 360Chrome v11 build 2251 scored 2457.

I benchmarked x86 versus x64 once-upon-a-time and x86 has better performance than x64, not the other way around. I do admit that this was a couple years ago, but the results were so CONVINCING and UNDENIABLE that I've never bothered with an x64 browser ever since.

Not sure, to be honest. File name suggests mobile phone.

Update. Content added for Russian to English Chrome Web Store.

I'll use my XP *FOREVER*. Even if THIRTY YEARS from now I "might" not be able to use a web browser or email client, I will STILL be using XP even if only on a secondary computer for Chess, Scrabble, Monopoly, Solitaire, Mahjong, Soduko, Kakuro, Crossword Puzzles, and other miscellaneous pass-the-time games that retired old folgies do between naps and yelling at the neighbor kids to get off their lawn. Although, having said that, I will also have to admit that ONE of my SIX "secondary" computers DID get upgraded to Win10 LTSB about five months or so ago because I got tired of several web sites "forcing" me to have FOUR web browsers! One web browser ONLY for ONE web site. Another web browser ONLY for a SECOND web site. A third web browser for rare miscellaneous. Then my at-the-time default for everything else. But now, ONLY because of 360Chrome, I have THANKFULLY been able to "upgrade" that secondary computer back to WinXP! Because while I like to tinker with several web browsers, I have no interest in being forced to have different web browsers for different web sites.

To each their own, but since you bring it up and seem to be requesting feedback -- my feedback is this, I DON'T GIVE A RATS ARSE ABOUT "UPDATES". The very FIRST thing I do whenever I install ANY operating systems is to DISABLE UPDATES !!! !!! !!! However, I do SLIPSTREAM updates before every installation - so I do "update". And one of the things I *LOVE* about Win XP is that I don't have to WASTE THE TIME slipstreaming MORE updates. I stopped slipstreaming and patching SO-CALLED "risks" in June 2017 on this computer (WinXP x64) and in January 2018 on my SIX computers running WinXP x86. I do NOT run antivirus - haven't for a good 15 years or so. If you know "how" to use a computer and know when to click and when not to click and if you do NOT let your software "phone home" and if you only allow WHITELISTED javascript, then "you'll do just fine". And make sure your hardware firewall (I also no longer waste my time with software firewalls) is set up properly. "You'll do just fine". WITHOUT concerning yourself with HYPOTHETICAL "so-called" 'security risks' propegated by an industry perpetuated as "needed" only when you allow 12 year olds to install "games" or when grandma installs some "coupon app". But anywhoo...

The "wrapper" program previously mentioned is called JauntePE and can be found here -- https://sourceforge.net/projects/jauntepe/files/ I'm not sure those 2 folders are worth the "learning curve" to learn JauntePE but I guess that's up to you. I personally clear my cache of EVREYTHING upon exiting EVERY browser session so at least on my end those 2 folders are EMPTY so they don't bother me sitting in ~\Application Data\. The "portable loader" does have a "[RunAfter]" section but I confess that I've never used it.

Not that I'm aware of. Those folders are temp and will be EMPTIED every time you close the browser. SEVERAL portable browsers can even share that same folder without affecting each other. I use a "wrapper" program at home that will perform what you seek, but I don't recall what it is called offhand. And with those folders being EMPTIED by default, I just let them sit there and ignore them.

Update. Added freebie software to first post and added step to remove Incognito Mode "background".

I used to use SpeedyFox under the FALSE assumption that it was making things "faster" - IT WAS NOT! Nothing but a "placebo effect", akin to "snake oil". I challenge you to prove me wrong, with quantitative before-and-after "measurements" -- 'good luck' to those accepting the challenge :)

Here's a quick guide on how to use the "official Pale Moon portable" version as a "loader" for Roytam releases. I use the older portable versions but the process is the same if you use a newer portable version (I don't like the icon color behavior in Win10 on the newer portable version but that's just a matter of personal preference). I use both the 27.9.4 version and the 28.2.2 version. I cannot find a link for the 27.9.4 but here is where you can find the 28.2.2 -- http://archive.palemoon.org/palemoon/28.x/28.2.2/Palemoon-Portable-28.2.2.win32.exe But there is no real reason to avoid the "new" if you prefer that route -- https://www.palemoon.org/download.php?mirror=us&bits=32&type=portable (ie, from here - https://www.palemoon.org/download.shtml#Portable_versions ) When you execute it, nothing is "installed" (ie, no registry changes, for example), it's simply just extracted (you could extract via 7-Zip or any preferred archiver, if you prefer). It will ask "where" to extract the files to - I generally create a new folder named "BasePortable" on the desktop just for convenience. This folder will contain six sub-folders (Backups, Bin, Downloads, Lib, ReadMe, and User). It will also contain two files, "Palemoon-Portable.exe" and "Palemoon-Portable.ini". We'll just keep default .ini settings for the sake of this tutorial. Open the "Bin" sub-folder. There will be a sub-folder inside it called "Palemoon" - we will keep it by that name even if we are using this for Basilisk, ArcticFox, New Moon, Mypal, et cetera. Open that "Palemoon" folder and DELETE all of the files in it (if your File Manager reports a read-only file, confirm in order to delete all of the files). The "Palemoon" folder should now be EMPTY. Now browse back to the folder where you extracted "BasePortable" (I used the desktop). Make as many copies of this folder as you want in order to make several portable browsers. But keep the "BasePortable" (with the EMPTY "Palemoon" folder) for future use if you like testing lots of Roytam builds without effecting your "everyday browser". As an example, let's say we want a Pale Moon 27 browser, a Pale Moon 28 browser, and a Basilisk 52 browser. We would copy the "BasePortable" THREE TIMES. Then rename the three copies to, for example, "PaleMoon27Portable", "PaleMoon28Portable", and "Basilisk52Portable". The folder name can be anything you want it to be. Next we download the Roytam versions we want to make as a portable browser. For this tutorial, I'm using the following three - http://o.rthost.win/palemoon/palemoon-27.9.1a1.win32-git-20180707-54887c52d-xpmod.7z http://o.rthost.win/palemoon/palemoon-28.1.0a1.win32-git-20180922-3c04affe2-xpmod.7z http://o.rthost.win/basilisk/basilisk52-g4.4.win32-git-20190727-9b0ff0e8b-xpmod.7z Then all three of those .7z files are extracted into their own folders. If you use 7-Zip context menus in your File Manager, highlight all three, right-click, hover over 7-Zip, then select Extract to '*\' These will all have sub-folders of their own of either "palemoon" or "basilisk" for these examples. Open the 27.9 folder's "palemoon" sub-folder and copy all of the folders and files. Paste those copied folders and files into the "Bin" -> "Palemoon" folder of "PaleMoon27Portable". Open the 28.1 folder's "palemoon" sub-folder and copy all of the folders and files. Paste those copied folders and files into the "Bin" -> "Palemoon" folder of "PaleMoon28Portable". Open the 52-g4.4 folder's "basilisk" sub-folder and copy all of the folders and files. Paste those copied folders and files into the "Bin" -> "Palemoon" folder of "Basilisk52Portable". For the case of the Basilisk52Portable, you will also need to rename "basilisk.exe" to "palemoon.exe". Once you become more comfortable with the .ini file and the folder structures, you don't need to keep the generic default "palemoon" naming scheme. But it's easier to just keep "defaults" if new at the portable loader. You now have three browsers completely independent of each other. You can execute all three at the same time. You execute the "portable" browser by executing (or shortcutting to) "Palemoon-Portable.exe" in the root folder of each browser. This method will start new profiles for each browser. The profiles are independent of each other. The profile locations for these three examples are as follows - PaleMoon27Portable -> User -> palemoon -> profiles -> default PaleMoon28Portable -> User -> palemoon -> profiles -> default Basilisk52Portable -> User -> palemoon -> profiles -> default Hope this is helpful to those that reached out requesting more details for the "portable loader".