NotHereToPlayGames

I was leaning in that direction also, once I realized how much file size storage was going to be required.

The drawback is going to be file size. !'m 90% done with the v13.5 changes and its file size increased from 70 MB to 88 MB. So that should put v13 at an increase from 69 MB to approximately 87 MB, v12 at an increase from 76 MB to approximately 94 MB, v11 at an increase from 67 MB to 85 MB, plus however I can puzzle SP2 versus SP3 and we're looking at somewhere around 350+ MB for an "all-in-one" 360EE. If users are downloading all four versions anyway, then we might as well make it one large download. The file names will clearly indicate what belongs with which so users could always remove items they have no use for. Another drawback could be extensions that work in v13/v13.5 but do not work in v11 - I do not know if this exists, to be perfectly honest, as all eight of the extensions that I use work in all four of my rebuilds. But part of my "all-in-one" end-in-mind is ONE profile that you can run in any one of my four rebuilds.

lol, I'm aware. That was just a quick-and-easy mockup using nothing but spreadsheet cell borders because my first copy-and-paste into the forum reply box didn't "stick the landing".

I rarely (only once in the last two years) log into my Win10 of my triple-boot setup. My Win10 partition is 1607 LTSB. Does anyone know if the DNSAPI.dll hack needs performed on LTSB? Also, I'd be curious to see the list of Windows services that you lock down.

Regarding Dev Tools reverting to Chinese in versions newer than v13 build 2206 -- new incognito window Dev Tools will also always revert to Chinese. Exists in original Chinese so carries over to anybody-and-everybody that rebuilds anything newer than v13 build 2206. Have not found any way to hard code default to English.

I've deleted DcBrowser. Don't have any use for it, sorry.

And I knew that was the icon you were hiding, I would have bet money on it

Agreed. The MSFN crowd really is very unique. And extremely rare. We really are very tiny in the grand scheme of things. I knew of MSFN long before becoming a member. And it was official Pale Moon dropping support for XP that landed me here as a member. But I feel like I was the ONLY person that landed here when official Pale Moon dropped XP. Fast forward and we saw what offical Pale Moon continued to do for XP. But did people flock to MSFN? Nope, we had two new members, maybe three. But for a day or two and they're not here anymore. I may be overexaggerating but you can follow that logic. 25 million or so XP users worldwide and you only need to take one shoe off to count all of the XP users active here at MSFN.

Actually, what strikes me as funny is that you took the time to "whiteout" the taskbar icon between Serpent and Windows Calculator.

I can add that skin as one of the options for a future "Builder". If I recall, that skin works very well with the rest of my GUI modifications - the only real reason I disabled it is more for "uniformity" with basically ALL other software on my computer, personal preference. I've never understood why Chrome got rid of the "title bar". I can understand back when a 17" square monitor was pretty much standard and all it could do was 1280x1024 and that "title bar" used half an inch of real estate. But nowadays with widescreen monitors basically running 1920x1080 or higher, that "title bar" is half the size of what it was on a 17" square monitor. Not like the days when we were running 800x600 and 25 pixels for a "title bar" was 4.2% of our vertical real estate. Contrast with 2.3% for 1920x1080.

The route I am considering is a "Build Your Own All-in-One" where ALL versions are contained within ONE download. What this would enable folks to do is run the "standard" to install their extensions directly from the Chrome Web Store but then they could switch over to the "ungoogled" to prevent the Google telemetry. Whenever they need to visit the Chrome Web Store, they'd just have to run the "Builder" to switch back to "standard", install their extension, then run the "Builder" again to switch back to "ungoogled".

Were you in the process of downloading something at the time? If so, there may be a hidden API "download manager" being used by DcBrowser.

Do you ENABLE this in Options -> Advanced? -- Check for intercepting certificate risk

I prefer v11 99% of the time. I use v12 every once in a while and v12 actually scores higher on pretty much every benchmark score you can throw at these browsers. BUT v11's GUI loads in a THIRD of the time that v12's GUI loads and that's more important to me than the very slight benchmark difference. My local copy of v13.5 uses this ("string" values below correspond to extension IDs) -- [RunAfter] DirRemove=%Profile%\safemon|e DirRemove=%Profile%\Webstore Downloads|e DirRemove=%Profile%\BrowserMetrics* DirRemove=%Profile%\ShaderCache DirRemove=%Profile%\GrShaderCache|e DirRemove=%Profile%\PnaclTranslationCache DirRemove=%Profile%\pnacl DirRemove=%Profile%\PepperFlash DirRemove=%Profile%\plugins FileDelete=%Profile%\*-journal*;chrome_shutdown_ms*;switch_core*;*.log;Last * FileDelete=%Profile%\Default\*.tmp;*-journal;log;log.old;*.log;*.ldb FileDelete=%Profile%\Default\*.txt;*.bak;reext;ruc FileDelete=.\Chrome\Application\*.log;*.tmp FileDelete=%Profile%\Default\Local Extension Settings\string1\LOCK;LOG;LOG.old FileDelete=%Profile%\Default\Local Extension Settings\string2\LOCK;LOG;LOG.old FileDelete=%Profile%\Default\Local Extension Settings\string-id\LOCK;LOG;LOG.old FileDelete=%Profile%\Default\Local Extension Settings\string3\LOCK;LOG;LOG.old FileDelete=%Profile%\Default\Local Extension Settings\string4\LOCK;LOG;LOG.old FileDelete=%Profile%\Default\Local Extension Settings\string5\LOCK;LOG;LOG.old FileDelete=%Profile%\Default\Local Extension Settings\string6\LOCK;LOG;LOG.old FileDelete=%Profile%\Default\Local Extension Settings\string7\LOCK;LOG;LOG.old FileDelete=%Profile%\Default\Local Storage\leveldb\LOCK;LOG;LOG.old;*.log FileDelete=%Profile%\Default\Local Storage\*-journal FileDelete=%Profile%\Default\MANIFEST-*;*.ldb;*.tmp;*.bak;*-journal;Archived History;History Provider Cache;Visited Links;Current *;Last * FileDelete=%Profile%\Default\360Bookmarks FileDelete=%Profile%\Default\Cookies FileDelete=%Profile%\Default\Google Profile.ico FileDelete=%Profile%\Default\History FileDelete=%Profile%\Default\History Provider Cache FileDelete=%Profile%\Default\Media History FileDelete=%Profile%\Default\Network Action Predictor FileDelete=%Profile%\Default\Network Persistent State FileDelete=%Profile%\Default\QuotaManager FileDelete=%Profile%\Default\Reporting and NEL FileDelete=%Profile%\Default\Secure Preferences FileDelete=%Profile%\Default\Shortcuts FileDelete=%Profile%\Default\Top Sites FileDelete=%Profile%\Default\TransportSecurity FileDelete=%Profile%\Default\Visited Links DirRemove=%Profile%\Default\Cache DirRemove=%Profile%\Default\Code Cache DirRemove=%Profile%\Default\GPUCache DirRemove=%Profile%\Default\Media Cache DirRemove=%Profile%\Default\Pepper Data DirRemove=%Profile%\Default\DailyBackup DirRemove=%Profile%\Default\Application Cache DirRemove=%Profile%\Default\AutofillStrikeDatabase DirRemove=%Profile%\Default\blob_storage DirRemove=%Profile%\Default\BudgetDatabase DirRemove=%Profile%\Default\DailyRollingBackup DirRemove=%Profile%\Default\data_reduction_proxy_leveldb DirRemove=%Profile%\Default\databases DirRemove=%Profile%\Default\Extension Rules DirRemove=%Profile%\Default\Extension State DirRemove=%Profile%\Default\Extensions\Temp DirRemove=%Profile%\Default\Feature Engagement Tracker DirRemove=%Profile%\Default\File System DirRemove=%Profile%\Default\IndexedDB\chrome-extension_strind-id_0.indexeddb.leveldb DirRemove=%Profile%\Default\JumpListIcons DirRemove=%Profile%\Default\JumpListIconsOld DirRemove=%Profile%\Default\Platform Notifications DirRemove=%Profile%\Default\Service Worker DirRemove=%Profile%\Default\Session Storage DirRemove=%Profile%\Default\Sessions DirRemove=%Profile%\Default\Site Characteristics Database DirRemove=%Profile%\Default\shared_proto_db DirRemove=%Profile%\Default\Sync Data DirRemove=%Profile%\Default\VideoDecodeStats

It's all pure speculation, to be honest. I personally HIGHLY doubt that Win7 will ever evolve into what WinXP has evolved into. We have some Win7 fans that will hate me for saying so but I'm just being honest. Part of XP's claim-to-fame is how LONG it lasted before Microsoft pulled the plug on it. XP has been around for TWENTY YEARS. 7 is twelve years old - basically HALF but the difference is not worth pulling teeth over. A 2015 article (here - https://redmondmag.com/articles/2015/04/08/windows-xp-usage.aspx ) states 250 million people were using XP several months after Microsoft pulled the plug. Microsoft pulled the plug on 7 in January 2020 and a year later 7 was already down to a mere 100 million (according to here - https://www.theverge.com/2021/1/6/22217052/microsoft-windows-7-109-million-pcs-usage-stats-analytics ) And drastically declining at a much steaper rate (according to here - https://www.zdnet.com/article/how-many-pcs-are-still-running-windows-7-today/ ) Again, it's all pure speculation. I'm honestly not trying to be biased (I am an admitted XP Die-Hard, but I still know the difference between "subjective" and "objective"). I see article after article that very strongly indicates that 7 is declining at a much steaper rate than XP ever declined. XP has dwindled to 25 million by late 2020 (according to here - https://www.xanjero.com/news/approximately-25-million-pcs-are-still-running-the-unsecured-windows-xp-os/ ) If it's any consolation, this XP Die-Hard will migrate to 7 when XP's shimmering light vanishes into oblivion. I also cite that XP had "POSReady" updates (which I do not use!) that helped eek out a few more years for XP for users that "care" about that type of 'crap' (yes, that was "subjective", lol). POSReady for XP was introduced MONTHS after XP was "retired". We're close to TWO YEARS that 7 was "retired" - does 7 have any "POSReady" types of updates? I have no clue because I don't use 7. But it's a fair question - does 7 have any "POSReady" updates that extended it beyond "expiration"?

ps - I was going to abandon v13 completely in favor of v13.5 but have since decided to keep both. At least until I can (if possible) find a way to hard code the Developer Tools language preference.

Not premeditated, lol. See post above, I had to modify the way that I pasted the image into the forum's reply box. Some of my past posts are intentional in the sense that I'll "waste time" to upload an image to an image hosting site (I use Dropbox because I already use it for other stuff), grab a share-link, then embed that share-link on my posts here. All of that really is a "waste of time" (and "space"). When those images are simply for the sake of "discussion", I do not keep them on my Dropbox, I delete them when the conversation is done (don't care that folks not engaged currently will not see those images "after" the conversation is over). I'll delete them from my Dropbox to prevent the "waste of space" - downside is that future readers will just see an empty space. Don't care. Was only there for the sake of discussion and I removed them when the discussion was over. Maybe I should look into Imgur (sp?) to host those "temporary" images, but can't say I'm really all that concerned, to be perfectly honest.

The "Build Process" would basically be a small GUI with a series of checkboxes (not in these colors per se) --

lol I did say "I can only speak for myself" I do think that the MSFN XP-user and the MSFN Vista-user and the MSFN 7-User, et cetera, really doesn't speak for the population-at-large. This community is a "rare breed" no matter which OS we run. We flocked here because we are "birds of a different feather". My view was "trying" (but failed) to speak towards the non-MSFN type of Win7-user. The vast majority of which, in my view, have never heard of MSFN. But then again, until XP started seeing the light at the end of the tunnel, I guess I never really heard of MSFN either. And now look at me, I'm here a dozen times a day, lol.

<delete>

<delete>

I kinda don't see that happening but only time will tell. Strictly my view, but since you asked... The XP Die-Hards are "book-ended" by two of the absolute worst operating systems Microsoft has ever released -- Windows Me and Windows Vista. I know we have some very respectable Vista users so please don't shoot the messenger and it is "opinion" (popular opinion, but opinion nonetheless) -- https://www.computerworld.com/article/3575332/the-worst-version-of-windows-ever-released.html https://www.howtogeek.com/720504/the-6-worst-versions-of-windows-ranked/ https://www.pcworld.com/article/528411/worst_operating_system.html https://www.makeuseof.com/tag/hated-windows-versions/ I can only speak for myself and others are welcome to chime in to agree or disagree. The way that I see it, most XP Die-Hards are die-hards because they evolved into it, not because their first computer ran XP and they just resist change. We remember Windows 3.1, we remember Windows 95, we remember Windows NT, we remember Windows 98, we remember Windows 2000. We witnessed the "marketing lies" of Windows Me and Vista. We witnessed Microsoft admit how "terrible" Vista was that they gave away free "upgrades" to XP to people that were trying to return brand new computers with immense hatred for Vista instability that came with that new computer. We witnessed driver support (primarily wireless printers) with 10 - that repeated each and every "update Tuesday" for 4 to 6 months after "upgrading" to 10. XP Die-Hards weren't "born", we were kinda "created through an evolutionary process". I don't see that "evolution" in the Win7 community, that community (from my experience) "loves" Win10 and is "looking forward" to 11.

A "Build...One" release would have all four (six if you include XP SP2) share one profile. The only problems that could arise is if you have an extension that doesn't work in all four (six) releases [I've personally not encountered any extension that doesn't work in all four].

Would take some time and I still need to complete my dark theme, but here is what I am thinking for my next major release - a "Build Your Own All-in-One". Right now, I offer ten different downloads. A "Build...One" would be one download and that one download would contain several compressed "data files". Then end user would only need to execute the "Build Process" once (or whenever they wish to switch "modes"). By executing the "Build Process", the "data files" that pertain to what you wish to build is extracted and you are up-and-running. Future launches are just launched as they always have been, direct from the "360Loader" executable. If you want to change "modes", you just run the "Build Process" again.