NotHereToPlayGames
Content Type
Profiles
Forums
Events
Everything posted by NotHereToPlayGames
-
Agreed. I was 100% XP (some x86, some x64) just a few months ago on eight of all nine of my computers (with that one exception being Win7). The Win7 laptop is still on 7. But four of the eight that were on XP all now run a WinReducerEX'd and NTLite'd Win10 LTSB. I could get an LTSC from work but so far I prefer LTSB. I'm still "testing" Firefox versus Chrome/Chromium versions (I do not support "newer is better" and run older if they perform better). So far each and every time I test a Firefox version, it suffers miserably compared to Chrome/Chromium - I feel like I keep wasting my time even trying them. But agreed, we should not let one browser/engine take over the entire web.
-
If you read through this entire thread, Humming Owl posted that he will no longer be updating any of these and there's been at least a dozen, if not two dozen, of these types of comments since. None of them have been replied to by Humming Owl. So keep on hoping until you turn blue, but these have been abandoned. The instructions have been provided for somebody else to pick up the torch and carry it. But I'm with Humming Owl on this, there are way too FEW of people that use these browsers for us to spend such a large amount of time on them. I think also that too many folks around here don't really fully understand what me and Humming Owl did with these browsers - we did not recompile the "engine", so that needs done by the original developer which has also (seemingly) abandoned these browsers.
-
DCBrowser is "abandonware".
-
I can hit "infinity" if I keep my Proxomitron enabled. But I generally run tests like these wtihout Proxomitron and without NoScript or uMatrix.
-
My hunch is that you've only been able to trick the RESULT. But the amount of TIME that the test takes should still tell you something for one browser versus another.
-
Fair enough. Do find it odd that the same exact computer, same exact browser, scores 140 here at home but breaks 300 at work. At any rate, even the 140 is the HIGHEST that I've ever seen ANY browser score here at home.
-
The tests I've used in the past are Speedometer 1.0, Speedometer 2.0, Basemark Web 3.0, Kraken 1.1, and SunSpider 1.0.2. I know they all correlate to each other as far as scores go. A browser that "wins" in one will also "win" in another. A browser that "loses" in one will also "lose" in another.
-
I know there used to be (or still is?) something called a "Just In Time Debugger" that could be enabled/disabled.
-
Sweet! Please let us know if you can track down the browser settings.
-
My Win10 laptop scores 140 both on direct-connect and on wireless.
-
I max the needle at 140 with the same exact laptop here at home. But it does break 300 at work. Perhaps the scale is different on different types of networks?
-
I use Ungoogled Chromium v97 on my Win10 and it scores 300 plus. It's the only browser I've ever seen break 300! Newer Chrome/Chromium's score lower so I've stayed with v97. My spreadsheets reference Speedometer 2.0, I did not know there was a 2.1 until just this week.
-
lol, was given to me for free when a neighbor installed WIN10 on it and then complained how slow it was. Works fine for XP, relatively speaking.
-
I'm over 12 minutes in (separate computer) and the test is still running on NM28. Yikes!
-
My oldest (without running to the garage and putting old parts together) is only 14 years old. eMachines T3656.
-
2.66 !!!??? Holy cow, Batman! It should be noted that the "Speedometer" test takes several things into account. I will get one result when running "fast" wi-fi, another result when connected directly to LAN.
-
This needs corrected to include a missing QUOTE (") at the very end of the user-agent line. Should read -- Parameters=--user-data-dir="%Profile%" --disable-logging --no-default-browser-check --disable-component-update --disable-background-networking --allow-outdated-plugins --kiosk-printing --disable-print-preview --cipher-suite-blacklist=0xe013 --disable-webgl --js-flags=--noexpose_wasm --user-agent="Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/107.0.5304.88 Safari/537.36"
-
Spoofing the useragent is old school. Some "modern" websites do not use your useragent but still know that you are using an "older" web browser. Etsy is using a "simple" user agent test - see next post for fix.
-
How well does Serpent 52, Serpent 55, BNavigator, New Moon 27, and New Moon 28 compare on your computer?
-
My Browser Builds (Part 4)
NotHereToPlayGames replied to roytam1's topic in Browsers working on Older NT-Family OSes
Chrome variants cannot set the backspace via about:config. I am not familar enough with Serpent 52 and offered the solution I use in 360Chrome. Good do know there's an about:config solution for Mozilla variants. -
Aside from THIS is how this "argument" started in the first place. I obviously "failed", but the ONLY thing I was TRYING to do is to demonstrate that DcBrowser uses more RAM than 360Chrome. Nobody else seems interested in "that" for some reason. We all know that Chrome variants use a lot of RAM, no new "news" there.