NotHereToPlayGames

The 360Chrome XP Skin is 61 KB.

I learned the speed-up-then-coast back when "hypermiling" was a big thing. One of my "favorite" things to do is see a RED LIGHT over half a mile up the road and take my foot off the gas and coast the entire half mile.

Not really. Will depend largely on what version of Win10 you use. I prefer 2016 LTSB and WinReducerEX100. Other versiosn of Win10 will require much more, things like PowerShell scripts to get rid of "metro" bloat. I'm technically only about 90% in on my Win10 migration as I have encountered a small snag with .net frameworks being enabled out-of-the-box directly after install.

How often do you see the "Win2k-basic-gray"? How often is the 360Chrome styling/skinning "above" versus "below"? Do you know the height of the "Win2k-basic-gray" title bar and did you decrease this height? Just curious in case I revisit a possible Win2k Theme.

Perfect example of why I never allow/enable ANY of my software to "update" itself.

Have you used this to compare rebuild 6 to rebuild 8?

I think you might be right. With very limited testing, rebuild 6 is HALF A POINT "faster" than rebuild 8 per Speedometer 2.1.

The not rebased will launch faster after a hibernate or reboot (first and only first launch, every consecutive launch is not affected). Web site rendering speed is not affected.

It has other changes.

Reserving first 2 pages of thread for creation notes and future changelogs. Folder Structure -- completed 360chrome.exe -- completed en_skin.srx -- to-do completed iframe.srx -- completed jisu9.srx -- to-do XP Theme completed, 10 Theme delayed for now, 2k Theme undecided skin.srx -- to-do completed en-us.pak -- to-do completed resources.pak -- to-do completed options.zip -- to-do partially completed completed chrome_100_percent.pak -- to-do completed chrome.dll -- to-do completed 360Loader.ini -- completed

<reserved>

<reserved>

<reserved>

<reserved>

<reserved>

<reserved>

<reserved>

<reserved>

<reserved>

<reserved>

<reserved>

<reserved>

<reserved>

<reserved>

Have you verified if the rebase was causing the issues you were having with your other programs?