NotHereToPlayGames
Content Type
Profiles
Forums
Events
Everything posted by NotHereToPlayGames
-
Not sure how far this will get you... In order to exceed x1080, you will need VP9 codecs which require hardware acceleration (to the best of my knowledge). I have never had any luck with hardware acceleration on XP so I'm not really sure where that leaves you.
-
Awesome Find!
-
I currently use my v12 build 1247 rebuild #3 as my default web browser - a rebuild #4 is due out within the next day or two due to two missing no-harm-done closing-parentheses found while working on a v11 rebuild. I am in-process of releasing a v11 build 2031 rebuild #1 but it is still "beta" at this stage but will also be uploaded within the next day or two. Unsure which of the two will become my overall preference (https://www.diffchecker.com/ does not seem to work in v11 but I have not debugged as of yet).
-
Videos work for me on that site.
-
When you Google for fixes, this has been a Chrome/Chromium issue since 2018. Will work for some logins, will not work for others. Looks like I will not be able to fix this for you. Unsure if there is a Web Store Extension that might do the job for you.
-
Root Certificates and Revoked Certificates for Windows XP
NotHereToPlayGames replied to heinoganda's topic in Windows XP
-
Here is a screencap of Humming Owl's most recent v13 rebuild with DNS over HTTPS "enabled". I respect and admire Humming Owl, please do not misread my intent here. I cite this only to highlight that this feature does not work in any of the 360Chrome versions and this is why I remove it from the GUI ("out of sight, out of mind", so as not to falsely mislead any user into thinking it "is" working). I have only tested in XP (and this is an XP thread here at MSFN), if this feature works in something other than XP (though I suspect that it does not) then I submit that the non-XP threads should have their own thread dedicated to 360Chrome.
-
Here is how you can "test" DNS over HTTPS -- https://1.1.1.1/help But as I mentioned, this feature is broken and does not work in any of the 360Chrome versions, so it is misleading for the setting to be there because it makes people falsely think that it is working.
-
That feature is broken and does not work in the original Chinese, is broken and does not work in the Russian Repack, is broken and does not work in my rebuilds, is broken and does not work in Humming Owl's rebuilds. I therefore remove the portion from the GUI because it does not work and is misleading for it to be there.
-
Try this version of v12 -- https://www.dropbox.com/s/fkzivlb3qqwhu3i/360ChromePortable_12.0.1247_rebuild_3.zip
-
You have the latest v12.
-
As far as benchmarking goes, it seems that v12 is the fastest for browser metrics out of v11, v12, and v13. Startup time for the first run after returning from hibernate or a full reboot is won by v11 - quite literally HALF the startup time! For browser metrics, v12 wins. For loading the GUI the fastest, v11 wins. I find the browser metrics all close enough to each other that I'm opting for v11 as my default based on that startup speed. Integrating "support" for XP x86 SP2 seems to have really HURT the browser's startup speed!
-
I don't think that there is anything that I (nor Humming Owl) can do about that. If the original Chinese version does not support XP x86 SP2, there is nothing that either one of us does in our rebuilds that will change that.
-
I guess when I think about it, it does make sense that all three versions consume identical RAM when all three versions have the same exact 20 YouTube tabs open. I guess I kind of was assuming that v13's RAM would be higher than v12's RAM which in turn would be higher than v11's RAM -- but this is not the case, all three versions consume the same EXACT amount of RAM.
-
My rebuild v11 does keep logins (once we make the changes we have already discussed, I generally have the options set to clear everything). Here is a BETA version of my rebuild v11 -- https://www.dropbox.com/s/xqyftttpx20rsnv/360ChromePortable-v11%20-%20in-process-14%20-%20BETA.zip This is 90% complete - all of the telemetry has been removed and this is fully-functional. I still have some GUI and English translation strings to go through. The BETA version already has the save-logins settings and keep-cookie settings set and should be ready for you to use as-is for your needs.
-
Does anyone have any suggestions for monitoring browser RAM? Not the OS RAM, but RAM used only by the browser. This one looks promising -- https://chrome.google.com/webstore/detail/cpu-and-memory-performanc/nmpbhigddhbbhopeeagpnnmnihgagbfk But I find it very strange that I can load TWENTY YouTube tabs into 360Chrome v11, 360Chrome v12, and 360Chrome v13 and the amount of RAM being used at IDLE and with TWENTY YouTube tabs is IDENTICAL across all THREE versions!
-
Open this link -- chrome://settings/content Make sure that under the Cookies section that the "Allow local data to be set" option is selected. My v11 GUI may be worded differently that Humming Owl's v11 GUI -- you should have three "circle options" and then two "square options" in the Cookies section, you need for the FIRST/TOP "circle option" to be selected. Not sure if you will need the two "square options" unchecked or not.
-
Open this link -- chrome://settings/advanced Click the "Clear browsing data" button then uncheck "Delete cookies and website data" option. If you like keeping data between browsing sessions, you may also want to uncheck "Clear selections every exit".
-
@cmccaff1 - which flag is that?
-
No prob. I have been in-process of rebuilding a v11 and plan to use it as my default-for-all for the sake of less RAM consumption. I think I showed v12 testing "slightly" higher in most benchmarks but v11 is "lighter" and loads the GUI faster so it's a slight tradeoff. Both are rock-solid and neither one has yet to ever crash on andy of my systems.
-
Device Manager -> Display adapters -> Nvidia GeForce FT 635 -> Properties -> Driver lists my driver version as 6.14.13.4788 and is dated 3/13/2015.
-
Not that I'm finding. I would suggest an Autoit script as your own loader that copies the contents and then launches the 360Chrome loader.
-
Found it! When you are browsing a time.com article on 360Chrome v11 (or v12/v13 with scripts disabled), open your Developer Tools (F12), scroll to the top of the Elements tab HTML code but below the "Time text cartoon", highlight the body line, then over in the Styles section UNCHECK the "position: fixed" entry. Now the article will scroll in v11 (and in v12/v13 with scripts disabled). Hope that helps.
-
Disregard. You will NOT get time.com to work using ANY user agent. I get the same page from a "new" UA, an "old" UA, a mobile UA, an iPad UA, an iOS UA, a Mac UA, "old" Firefox, "new" Firefox, Opera, even an IE6 UA. I've personally never witnessed a website until just now that served the same exact page to an IE6 UA that it serves to Firefox and even Mac. Time.com is clearly NOT using UA and might be using other "techniques" too new for 360Chrome v11 (Chromium v69).
-
Did you try going the other way with the User Agent? Don't pick something "new" but pick something "old".