NotHereToPlayGames

We could "probably" make changes to one version's browser_strings.xml and carry that .xml over to a newer version, but I prefer to avoid any possible mistakes so I modify each-and-every build totally from scratch. I wish there were more MSFN users actually INTERESTED in 360Chrome. It has a lot of potential but the number of users here that use it can be counted on one hand! What really needs done is a total rewrite to get rid of all the REDUNDANCY. As an example, the phrase "Add to Bookmarks" exists about a DOZEN times in SIX different files. I'm OCD so all one dozen entries spanning six different files HAS TO BE IDENTICAL. ALL software developers should be OCD !!!...

The most-recent Build 2206 that was labeled as (unran) has more corrections than the Build 2250. I'll likely redo the Build 2250 in the next few days or so but going through all of those changes takes a long time. The skin subdirectory with the browser_strings.xml file in particular takes a long time. When I redid Build 2206, I opted to Capitalze Every Menu Word like most modern browsers tend to do (unless it is a word like is, in, with, or, an, and).

Crap! My apologies! That is the Russian Repack that my build STARTS FROM but that doesn't have ANY of my modifications. Here is the correct link -- https://www.dropbox.com/s/uqusfcjrbox9akz/360Chrome%20%28unran%29.zip?dl=0 My apologies.

Those screen caps are not from my build.

Does Netflix work in OTHER BROWSERS in XP?

Can you post a screen-cap of the missing english?

I would try the modified 2206 first. Is your YouTube test before or after you install any extensions?

Good deal, hopefully build 2206 proves better. Keep us posted.

I see zero benefit to using DropMyRights (for any web browser of 2021!). It was discontinued in 2004 and its user-base practically fell off the face of the earth in 2009/2010. XP was released in 2001, SP1 was released in 2002, SP2 was released in 2004, and SP3 was released in 2008. uBlock became available in 2014. I would resurrect JauntePE before reurrecting DropMyRights.

Thanks for the feedback. Can you describe why 2206 did not work in your case?

I would delete the Build 1006 version (for now at least), you only need to delete the files. It was for curiosity/testing since Build 2250 was crashing for a few of us. I've reverted to Build 2206 and I have it available from the below links (if we find that Build 2206 crashes for a few of us then I'll revisit Build 1006) -- https://www.dropbox.com/s/vk7fkatsa27l7mz/360_extreme_explorer_13.0.2206.0.zip?dl=0 https://www.dropbox.com/scl/fi/277hb9m3n09dnvy0vgn3h/13.0.2206.0.xls?dl=0&rlkey=tcjlaugbf76xzssd04uxdh1b4 EDIT: the above .zip is the Russian Repack - UNMODIFIED Here is the correct link to my Build 2206 -- https://www.dropbox.com/s/uqusfcjrbox9akz/360Chrome%20%28unran%29.zip?dl=0 Do note that version 9.5 is expected to be slightly faster than version 13, but I wouldn't expect too much of a difference on an HP EliteBook 8540p. I may do an actual BENCHMARK test between the two (as opposed to "gut feelings"), but I'm in no hurry for that. My biggest thing is that v13 CAN DO stuff that v9.5 simply can NOT DO, so it's a balancing act, are those CAN DO'S worth the SLIGHT (if even noticeable!) speed difference? To me they are because I don't own a phone and require v13 to use as a phone. But in the ever-evolving internet, it won't be long before v9.5 simply cannot do half of what it used to be able to do. Web sites are constantly changing and using "new code" that older browsers can't decypher/execute/render.

@we3fan - do you mind trying the beta build 1006 that i linked for @Greyfox77 ? In the meantime, I am in-process of rebuilding my Build 2206 - I have witnessed some crashes/lockups with build 2250 but not quite as much as you two have posted, but enough for me to revert to Build 2206. But an even earlier beta may end up proving even more stable, unsure as of yet (and the file/folder structure is drastically different). But I do know that my needs require v13. I kinda would also be curious as to your CPU, your RAM, and the total number of processes that your setup runs. And I am assuming you are running Win XP SP3 x86 or Win SP2 x64 and not some hacked kernel like some of the Win 2000 crowd. I included POSReady2009 updates as "hacked" - I have witnessed them killing some of my older programs and I no longer install any of them. I just did close to an hour of YouTube on my lowest-grade hardware available without resorting to a 16yr old ThinkPad T43 laptop that I don't "expect" a lot out of (and I subsrcribe to the notion of it being insane for me to "expect" a lot out of). My test laptop is a Dell Latitude D830, Intel Core 2 Duo T7500 @ 2.2 GHz, 4 GB DDR2 SDRAM, WinXP x86. You could get the D830 with a 1.8, 2.0, or 2.2 GHz CPU, so mine was "top-of-the-line" when new (circa 2007, so still 14yrs old). Aside from typical audio-stutter (only while the page is still loading) on low-grade hardware, the browser did not crash or lockup for the entire hour.

@Greyfox77 - I would be interested in your feedback on the below version. It's one of the earlier BETA versions (only the second BETA if I tracked correctly) (Build 1006). Please note that this is an unmodified version and I would not visit any of you banking sites with it, but I am curious if this may solve your stability issues. https://dl.dropboxusercontent.com/s/htxqcsco69yl540/360Chrome%2013.0.1006.7z

I've had two lockups in two days, so I was waiting for others to reply before deciding my own next step. The lockups that I have had on Build 2250 are at startup and I have to exit the browser and restart it. But while the browser appears to exit, a new restart will not actually restart. I've had to go into Task Manager and kill a few processes pertaining to 360Chrome and then I can restart - I've never had that occur while using Build 2206. So I have been on the fence on whether to revert to Build 2206 or not because it was my gut feeling that it is more stable. Not sure if Build 2206 will solve your stability issues as well, I'll provide a copy of my "base" with all modifications and untouched by a "first run" later today or early tomorrow. Thanks for the feedback, it kinda confirms my own hunch that Build 2206 is better than Build 2250. ps - v13 is the ONLY browser I have been able to find that runs in XP and where Google Voice can make phone calls (I don't own a phone, haven't for close to 20 years, not when I can make phone calls for free using my computer!). I've had to rely on a VirtualBox Win7 VM and ungoogled Chromium builds for Google Voice in recent years and it wasn't until 360Chrome v13 was discovered that I no longer need the Win7 VM.

I thought the LTSB was supposed to be void of all telemetry? Not a matter of disabling because it's simply not there. But maybe that is my company's IT department and the way they set it up, as I kind of have no control on my Win 10 LTSB laptop.

Has anyone been able to figure out why 360Chrome v13 does not download .csv files? If I recall, other Chromium builds do not download .csv's either.

"Base" build update - For anyone that may have downloaded my "base" build and the accompanying .xls notes, I have since made two changes (but have not uploaded a new .xls). Step 3 -- I now REPLACE dark with chrome in the Preferences file so that it now reads "id": "jisu9_chrome", [note: the comma at the end is intentional] Step 8 -- I now RENAME original jisu9_dark.srx to jisu9_dark.srx.bak and RENAME original jisu9_chrome.srx to jisu9_chrome.srx.bak Then download my XP skin now-named jisu9_chrome.srx and place it in the ..\Chrome\Application\13.0.2250.0\skin folder The updated XP skin download link is -- https://dl.dropboxusercontent.com/s/9tq4s4dezizsts5/jisu9_chrome.srx The only update to the XP skin (aside from file name) is I updated the download icon in the main toolbar. ps - Build 2250 has a tendency to lockup on First Run and requires processes to be killed via Task Manager. Subsequent runs are flawless and I haven't had any crashes or lockups in three days.

No worries, I'm sure we'll still see you around on other MSFN subforums.

Already looked into it. Special order and I only use that laptop to tune turbo engines on project cars so it doesn't get used that often.

I almost forgot about this post. I'll revisit my build notes but I'll hold off for a few days, it took a major chunk of the entire weekend to do the "rebuild" and track each-and-every change along the way. I did discover that I forgot to update the download icon, the icon that's there "works", I just use a different one in my normal XP skin and forgot to port it over when I did my rebuild for 2250.

Only 16 years old? Knock on wood! But I think I may outlast you My ThinkPad T43 is from 2005 and is also 16 years old. I have to set the BIOS clock every time I turn it on but other than that she's humming along in third gear.

Too funny. Did they catch the colsed typos versus closed? Or Colse versus Close? Or Backuo versus Backup? Or clouds (plural) when you back up to the cloud (singular)? Or bookmar versus bookmark? Or just the total misuse of SPACES? My complete rebuild notes and a copy of my "base" with all modifications and untouched by a "first run" is provided below. https://www.dropbox.com/s/5twje35tkzfh8ay/360ChromePortable.zip?dl=0 https://www.dropbox.com/scl/fi/obhxz6smkkt6030hn90ks/13.0.2250.0.xls?dl=0&rlkey=3i1ghxtckjhzw67t0nxpkoq94

DITTO !!!

Why abandon XP? IF you must abandon XP, I've had performance-success with Win7 Enterprise and Win10 LTSB. But they were also both provided by place-of-employment - with a license that allows me to install at home due to remote work. I haven't taken the leap to test-drive Win11 yet, I haven't even looked at if these copies floating around are "legal" or "leaked".

I used to have a program that would TIME my startup. Like @j7n pointed out, just because a service is delayed to start, it still has to start. That's the oldest trick in the book - instead of hammering the CPU(s) with EIGHTY startup processes, you hit it with 20, wait a minute and load 20 more, et cetera. A computer user turns his/her computer on, he/she can't DO ANYTHING when the CPU is trying to load EIGHTY startup processes. But only load 20 instead and now the user gets that warm-and-fuzzy feeling that they can open their web browser 15 seconds after hitting the Power On button versus 80 seconds after hitting the Power On button. Doesn't matter that three minutes later the computer is STILL loading startup processes, at least the user was able to load his/her web browser before all of those startup processes were fully loaded.