NotHereToPlayGames

Correct. I've "accepted" the trade-off of correctly-allocated RAM over launch time (at least for now!).

For reference. Rebased 13.5 build 2020 versus rebased 13.5 build 1030 versus rebased 13.0 build 2170. Intel Core2 Quad Q6700 @ 2.66 GHz with 3.24 GB available RAM.

You have to have one or the other, you can't have both. Enabling Chrome Web Store to funtion "as intended" also enables a cookie that you can not delete, a cookie that sends telemetry to Google, a cookie that you can not delete, a cookie that talks with each and every web site you ever visit, a cookie that you can not delete, a cookie that tracks your web usage across all browsing sessions, a cookie that you can not delete, a cookie that is even set in Incognito Mode, a cookie that you can not delete. This cookie is constantly sending "data" to Google. You don't have to sell your soul to Google to download extensions. There are better ways. I'm not so privacy-conscious that I wear a tin foil hat, but things like blocking this Google cookie doesn't require any tin foil. But I do cook all of my Christmas cookies on foil because then the cookie pan last a very long time.

lol, too d@mn funny. I have to laugh out loud at some of the "history" here at MSFN.

Cool, that's a relief.

I really really really neeed a PICTURE to see what you are talking about.

That setting is not supposed to affect WEB SITES. It's intended to change the size of fonts used in 360Chrome MENUS. This is why I requested a PICTURE, to avoid all confusion in the first place.

I still need to see a PICTURE of what fonts you are expecting to see changed. This setting IS changing font sizes. Though not "all" of them. I never use it so am unaware if different versions change different fonts.

I use CRX4XChrome - https://www.crx4chrome.com/

It's labeled "ungoogled" because it breaks the "hand-shake" with the Chrome Web Store that creates a cookie that you can not delete and that relays telemetry back to Google. You cannot install extensions via Chrome Web Store but there are BETTER ways to install extensions anyway.

re: Disable pop-ups - Yeah, I always prefer my Proxomitron determining what a pop-up is versus my browser. For example, 360Chrome won't let me visit my credit card's FICO page because 360Chrome thinks it's a "pop-up". re: Use custom font size - Can you show a picture of this ever working in any of the 360Chrome builds?

Because "life is too short" to sweat the small stuff. And it's all small stuff.

The standard telemetry and GUI changes. I'm OCD about the GUI.

Build 1030 will be discussed in a separate thread -- https://msfn.org/board/topic/184266-arcticfoxienotheretoplaygames-360chrome-v135-build-1030/ Download links will be provided shortly.

<reserved>

<reserved>

<reserved>

<reserved>

Reminder that Chrome Web Store is intentionally broken in the "ungoogled" version. The best route I have found to return a degree of functionality to Chrome Web Store but to do it without the telemetry/tracker/persistent-cookie is to manually install this extension -- https://www.crx4chrome.com/crx/265228/ Scroll down to the Download Now section and click the Crx4Chrome download link (the other links should work as well, I have only ever used the Crx4Chrome link). Note that the download will download without any "where to save" dialog, it will download to your default directory as set in chrome://settings/downloadSetting. To manually install, drag-and-drop this .crx file onto "empty whtie space" on your chrome://extensions/ page. You should get a dialog asking to confirm installation - click the Add button (then close the self-advert nuisance tab). Now whenever you visit a Chrome Web Store addon page, you can download the .crx directly and manually install as opposed to installing via the Chrome Web Store.

This build is targeted to be more RAM-friendly than earlier builds. The chrome.dll file now has a default base address of 0x3e1c0000 and this seems to work well for both x86 XP and for x64 XP. Limited to no tests whatsoever were performed outside of XP. Download links: https://www.dropbox.com/s/90of6ljan32ivm6/360ChromePortable_13.5.1030_rebuild_7_regular.zip?dl=1 https://www.dropbox.com/s/k1h2v0s68lt2g7h/360ChromePortable_13.5.1030_rebuild_7_ungoogled.zip?dl=1

"Regular" build 1030 will maintain "Translate to English" feature. "Ungoogled" build 1030 will have "Translate to English" totally removed/disabled.

That's an oldie-but-goodie little trick. I used to remove Hibernate and Standby on XP x64 systems with more than 4GB RAM because they were "greyed out".

Since 0x3e1c0000 seems to work for everything I've thrown at it (one x86 XP laptop, one x86 XP desktop, one x64 XP desktop, two Win10 x64 laptops), I'm getting ready to repackage everything, upload, and start a new thread dedicated to 13.5 build 1030. There still could be a "better" base address, not really sure. I literally just tacked via trial-and-error until I hit one that worked.

I was originally aiming for "contiguous". ie, force a "defragged" RAM. Looks like this is not really the best approach. Looks like what is working better (and more universal) is to base to an address BELOW all of the SysWOW64 and WinSxS stuff. But to keep it ABOVE a mouse-gesture app I run on all of my machines (ironically, this mouse-gesture app resides at 0x10000000 - ie, the original default for chrome.dll). Admittedly, it's all been trial-and-error and just keep trying new base addresses. 0x3e1c0000 seems to be working out just great. For x86 and for x64.

I suppose I could run with a default that work on x86 even though it will not work on x64. I have a strong hunch that MOST folks here on XP are all on x86. I think me and @UCyborg are the only two on x64.