
NotHereToPlayGames
MemberContent Type
Profiles
Forums
Events
Everything posted by NotHereToPlayGames
-
For your mixed content preference (if I follow), add the below line to the very end of the Parameters line in the [FileToRun] section of your 360Loader.ini file, make sure there is a space between the new command and the previous command: --enable-strict-mixed-content-checking For your tls preference, I think you need to set a min and a max both to 1.2, add the following: --ssl-version-min=tls1.2 --ssl-version-max=tls1.2 Either that or you might just need the following: --tls1.2 For reference -- https://peter.sh/experiments/chromium-command-line-switches/ I would personally always use 360Loader.ini over "flags", but that's because I can do more with "switches" than I can with "flags".
-
PC randomly powers off with no BSOD or error message
NotHereToPlayGames replied to GD 2W10's topic in Hardware Hangout
ps - have you tried this in an Admin-Rights Command Prompt window - powercfg.exe /hibernate off -
PC randomly powers off with no BSOD or error message
NotHereToPlayGames replied to GD 2W10's topic in Hardware Hangout
I would be interested to see if it does it WITHOUT any VMs running. Maybe that would at least isolate it to whatever you use for VMs (VirtualBox?). -
Oh, I also compared RAM with and without those five embedded extensions - no noticable difference. Also why I provided the resources.pak file numbers so again under the guide of "trust, but verify" so people who are following can see for themselves how TINY those embedded extensions are. Don't misread, I applaud and appreciate learning something new (disabling embedded extensions) - but again, I saw ZERO performance gain. Is that due to XP? I suppose it is possible.
-
It's honestly not that simple. I am from the Ronald Reagan Era - Trust, but verify. Which was not coined by Reagan, just popularized by Reagan. The Russian Proverb is actually a bit cooler because it rhymes - Doveryai, no proveryai. I never trust any claims on performance without witnessing a quantitative and repeatable measurement that others can use on their system as well - which is why I tested the performance claim using PassMark AppTimer. Without some form of quantitative and repeatable measurement, all we really have is some form of Placebo Effect or some form of "gut feeling".
-
Load times after reboot -- 6.3227 0.5036 0.5153 0.5105 Load times after reverting changes and keeping these inside resources.pak (no reboot) -- 0.4841 0.4948 0.4821 0.4841 According to PassMark AppTimer, my 360Chrome actually loads FASTER when I KEEP these embedded extensions. With them being Chromium/Chrome upstream files and in no way tied to China or Russia, I'm kinda leaning towards the side of keeping them. At least until I can find some proof that they are making connections behind my back (which I have not seen yet). The "feedback" one is kinda the only one that bugs me - but I also only think it "does" anything if you yourself click on a Help - About - Feedback link.
-
Okay, so I successfully removed PDF Viewer, CryptoToken, Feedback, and Cloud Print and everything seems to be working without them. Load times BEFORE removing them -- 0.4871 0.4907 0.4938 0.5447 Load times AFTER removing them -- 0.5064 0.5096 0.5037 0.5163 Rebooting and timing a load of first run after a reboot -- reference reboot first-start is 6.7134 and 6.1693
-
I couldn't get my 360Chrome to launch if I removed the above manifest.json's embedded in resources.pak by way of hex editor. Revisiting the route of unpacking, isolating pertinent files, then repacking. 156 == PDF Viewer 162 == CryptoToken 160 == Feedback 152 == Cloud Print not found == Identity API Scope Approval UI --> will attempt to kill again via hex editor
-
Note to self -- https://chromium.googlesource.com/chromium/src.git/+/71.0.3578.98/chrome/browser/resources/pdf/manifest.json https://chromium.googlesource.com/chromium/src.git/+/refs/heads/main/chrome/browser/resources/cryptotoken/manifest.json https://chromium.googlesource.com/chromium/src.git/+/refs/heads/main/chrome/browser/resources/feedback/manifest.json Cloud Print deprecated December 2020 - unable to find manifest.json - removed code from "name:" through "display_in_launcher": false https://chromium.googlesource.com/chromium/src.git/+/refs/heads/main/chrome/browser/resources/identity_scope_approval_dialog/manifest.json
-
I assume that the custom DPI lets the web page that you are visiting set the DPI instead of using your system DPI. I have not seen that setting do anything in the original Chinese release or the repack Russian release. I'll have a custom font size change shortly but I'll upload again as the same file name. Also will change Use custom DPI to Do not use system DPI - but technically I have no clue what this setting is "supposed" to do. I'll post when you can re-download.
-
Updated build 2206 rebuild has been uploaded. Did not do any changes with Chinese Avatar (I don't use the Avatar but I'll visit that at some point). No resources changed as of yet, the discussed resource changes also exist in "vanilla" Chromium so I'm unsure as of yet on their removal. 360Loader.ini has been reverted to default format as far as cache and cookie management - but the settings to keep cache and cookies between sessions will require the end-user to visit the pertinent settings. https://www.dropbox.com/s/e2pwk0551kbe4b8/360ChromePortable%20%20--%20%20Build%202206%20-%20MSFN%20rebuild%20v2.zip?dl=0
-
I don't see a resources.dll so I am assuming that you meant resources.pak. resources.pak for Build 2206 contains 1,561 files (one of them just the index.ini). 1,393 of them being typical no-extension files -- none of them contain the text crbug. 2 of them are .html files -- neither contain the text crbug. 51 of them are .js files -- there are 55 results for crbug but all of them are comment lines so that you can read up on the Bug Report for various sections of .js code [we can both agree that changing http to hxxp for a comment line is meaningless]. 8 are .json files -- none contain crbug. The remaining are all .png files.
-
I used PassMark AppTimer to time how long it takes 360Chrome to load. I did this with all six of my Extensions enabled. My load times are -- 6.7134 0.5007 0.4870 Timed a second set of load times -- 0.5115 0.4851 0.4821 That very first load time (6.7 seconds) is normal for the first load after a reboot (Pale Moon, New Moon, and MyPal [almost all web browsers, as far as that goes] do the same thing for first load after a reboot) Going to reboot and perform a second set of numbers for comparison. After a reboot - My load times are -- 6.1693 0.5173 0.4841 Timed a second set of load times -- 0.4812 0.5065 0.4801 Now I'll try those resource.dll edits and repeat load times for comparison.