NotHereToPlayGames
Content Type
Profiles
Forums
Events
Everything posted by NotHereToPlayGames
-
Agreed, not really worth "following".
-
Can't. End users will have to install Tampermonkey then install that userscript.
-
Okay, this works to block all of the search engines that you cited.
-
I'm not finding anything that will block Infinity Search, Okeano, and Swisscows. I'm sticking with this for now -- https://greasyfork.org/en/scripts/375216-block-opensearch-descriptions/code
-
This userscript now replaces my old and it will block Time.is -- https://greasyfork.org/en/scripts/375216-block-opensearch-descriptions/code But does not block Infinity Search, Okeano, and Swisscows.
-
The userscript I was using did not block Time.is. Investigating...
-
Those search engines are being added by a Chrome/Chromium "feature" called OpenSearch (Firefox, Safari, and Edge all do this also) -- https://en.wikipedia.org/wiki/OpenSearch Previously discussed here on MSFN -- https://msfn.org/board/topic/182876-360-extreme-explorer-modified-version/?do=findComment&comment=1203764 I personally disable this "feature" through the use of a Tampermonkey userscript -- https://greasyfork.org/en/scripts/37186-disable-opensearch/code
-
What I am seeing, based solely on your information, is that Humming Owl's releases broke some javascript and then displayed it as text instead of performing the "function" that the javascript was intended to perform. But that mine did not break the javascript so the broken code was not displayed as text. Or, the broken javascript code is simply "dropped" / "ignored" by my builds but Humming Owl's doesn't know what to do with it so it displays it as text. Not sure what you think needs "fixed" here. If it sets your mind at ease, I opened that link and clicked the gigantic YOU in Dixel's v13 360Chrome, Humming Owl's v13 360Chrome, and my v12 360Chrome both in XP x64 SP2 and in Win7 x86 and all three gave me the EXACT results, letter for letter. So then I installed Chrome v94.0.4606.71 in Win7 and it too gave me the same EXACT results. Mozilla-based browser will give an entirely different view. Maybe that "test page" is intentionally 'coded' to only work on Firefox and not on Chrome - who knows.
-
Can you post a screencap? I'm showing the exact same thing for both mine and Humming Owl's. Is this possibly an XP x86 SP2 issue?
-
Yes, but what am I looking for? The Thursday, April 21, 2011 4:41 AM ???
-
Different "how" for whoownsmyavailability? I get a gigantic "YOU" in six different browsers that I opened that link in. You can only change the Power Save setting when running on BATTERY via a LAPTOP.
-
v11 is the way a "dark theme" SHOULD BE. v12 and higher approach is just Google being a MONOPOLY. But I digress...
-
That's SP3, not SP2. I have zero problems getting SP3 to run - 7 out of 8 of my computers are running XP x86 SP3, the remaining 1 out of 8 of my computers is running XP x64 SP2.
-
Same here! But for x86 SP3! I do have a VANILLA x86 SP2 "installed and running" on an old Compaq Presario - but I cannot get ANY web browser to WORK on it! I really think that what you have (and the other x86 SP2 users frequenting MSFN) is NOT a "vanilla" version of x86 SP2 - I think you have "patched the crap out of it" in order to get it to WORK. By "vanilla", I took my original retail XP install disk, installed XP untouched/unmodified, all default settings. Then I installed SP2 carried to the POS (no affiliation with POSReady) via memory stick and installed SP2. So my XP x86 SP2 is VANILLA, PURE, SNOW-WHITE, VIRGIN, UNADULTERATED, IMMACULATE, PRISTINE, UNBLEMISHED, IN MINT CONDITION, UNPOLLUTED, et cetera. And I cannot get ANY web browser to WORK on it!
-
@CIACIACIACIACIACIA - seems to me that your system should be capable of all of the 360Chrome builds. I have no experience with Greek XP and also no experience with KB2584577-x86-enu.exe, unsure if my install has it or not.
-
Does that mean you don't "like" XP x86 SP2? I thought you "preferred" it over x86 SP3? (I personally do not, I remember doing HUNDREDS of performance metrics back when SP3 was "new" and I concluded ZERO reason to stay with SP2 and never looked back [until 360Chrome kinda created a temporary curiosity].)
-
Added new links (first post of this thread) for my new v11 rebuilds for XP x86 SP2 based on @we3fan's and @Humming Owl's experimental x86 SP2 tests. Regular and Ungoogled. Please note that I have not tested these and I have abandoned installing XP x86 SP2 on an old machine worth more to me gathering dust than getting x86 SP2 up and running.
-
Being off by one hour seems very minor to me. I have to "deal with" that 6 months each and every year because the "gubberment" falsely thinks that "daylight savings" is a 'good idea'. Spring Forward, Fall Back -- most retarded idea the "gubberment" has ever come up with in my (not so humble) opinion!
-
Noted. @we3fan assisted @Humming Owl in an XP x86 SP2 set of modifications that I have not ported to my release(s) yet. I should be able to get to that later this week and upload a set of XP x86 SP2 releases. I need to catch up on that list of modifications but if memory servers, it only pertains to v9 and v11. Since I don't release a v9 (at least yet, not sure if that is down the road or not), I think I only need to rebuild my v11. Will visit as time permits...
-
Doesn't download from the download link in Post #1 of this thread? Or downloads from the download link in Post #1 but when you open a website from it and that website has a download link, that download isn't downloading?
-
Updated links (first post of this thread) for my v11, v12, and v13 rebuilds. Regular and Ungoogled.
-
When you open your XP's Task Manager and go to the Performance tab, how many Processes are reported in the lower left corner and what is displayed as Available for Physical Memory?
-
Your profile reports "XP Pro x86". So are you running SP2 or SP3?
-
Internet Archive Wayforward machine
NotHereToPlayGames replied to Nokiamies's topic in General Discussion
Looks like nothing but Section 230 propaganda to me. -
You may also want to try this. For me, the registry key that Humming Owl found points to a Tahoma font. For my system, I intentionally set Tahoma and I no longer recall what XP uses as its default. Right-click on top of empty space on your desktop, select Properties in the context menu, select the Appearance tab, click the Advanced button, go to the Item dropdown and select Menu, change that font setting and please report back if this worked or not.