Jump to content

NotHereToPlayGames

Member
 View Profile  See their activity

  • Posts

    6,714

  • Joined

  • Last visited

  • Days Won

    83

  • Donations

    0.00 USD 

  • Country

    United States

 Content Type 

Everything posted by NotHereToPlayGames

  1. NotHereToPlayGames
    Russian repack does have the 360 Doctor module. The Russian repack also kept the 360base.dll and the skin file .srx's also contained portions of the 360 Doctor module. I think they did set a flag in the skin file .srx which prevents the icon from showing - that prevents a user from clicking the icon but does not prevent underlying code from launching 360 Doctor. But we have beat this dead horse sufficiently. Followers of the thread can decide for themselves if restoring error code content pane introduces unintended risks or not. We have both made our points and the reader can take it from here.
  2. NotHereToPlayGames
    Because certain error codes cause a javascript event to be "true" that then results in connecting to Chinese IP Addresses. In the file you attached, follow the javascript code for things labeled as "first aid kit", that "first aid" is part of "360 Doctor" which was intentionally removed/disabled from my builds. I guess technically what we need, but I don't know of a good way to obtain, is a URL that results in all three dozen or so "error codes". One URL per error code.
  3. NotHereToPlayGames
    "Upstream" has a feature called "360 Doctor" (I may have the name wrong). SOME of these error codes redirect to a "first aid kit" which is part of "360 Doctor". There are at least 3 dozen error codes. I am not claiming that all of them are tied to Chinese IP Addresses. Some of them are. Not sure why this is being HIT with such resistance. *I* am the one that mod'd the browser being discussed in this thread, am I not? "Oye", as my sister would say. (Unsure of proper spelling.)
  4. NotHereToPlayGames
    Not for me, per se, I don't want the error codes. Unless you (D.Draker) have updated, you're running Build 1030 and there were big changes between 1030 and 2022 then even more changes to 2036 (this thread). I'm just saying "don't assume because you make an arse out of u and me". There have been DOZENS of "issues" reported over the years that were later tracked down to "mixing and matching" and "making assumptions".
  5. NotHereToPlayGames
    Thanks. It is the "first aid kit" entries that will connect to Chinese search engines. We would need example URLs that "trigger" several of these "error codes" to fully confirm/deny that they connect to Chinese IP Addresses. I preferred to "play it safe" and just disable/remove the "possibility".
  6. NotHereToPlayGames
    You lost me. Wasn't really a "reaction". Was it the waving hand emoji that made it look like a "reaction"?
  7. NotHereToPlayGames
    Can't dig deeper from work computer. I will likely not dig into it from home computer either. I've shared the browser in the condition that I use it. End users are of course allowed to tweak to their own liking. Browser choice is always always always "personal preference". That's why we have HUNDREDS of browsers to choose from.
  8. NotHereToPlayGames
    If you go this route, be cautious of versions because some language translations are tied to an "index" number that do not match between my versions and Humming Owl versions. Humming Owl maintains good notes, I leave it to the end user to know what they are merging, just don't assume that they will walk hand-in-hand. Build 1030 language indexes do not match Build 2022. Build 2022 language indexes do not match Build 2036.
  9. NotHereToPlayGames
    They could have just been "click here for more details" types of Chinese search engine links. Regardless, something I have no use for.
  10. NotHereToPlayGames
    I would have to revisit (which would be so back-burner that it's the neghbor's neighbor's stove), but be cautious in restoring neterror.js - some error codes are tied to Chinese search engines. Very likely could be something they introduced in v13+ and may not be in v12. Do not recall, see no real justification to restore this "feature".
  11. NotHereToPlayGames
    I intentionally removed the error pages. One, they were all in Chinese. Two, the error code still exists in the URL and that 3-digit number is all we really need most of the time. Three, some error codes redirected to Chinese telemetry web sites.
  12. NotHereToPlayGames
    Agreed! I've been using a Win10 VM since 2017 (and a Win7 VM, for that matter) but only THIS YEAR migrated my installation that evolved many many times since as an OS onto real hardware.
  13. NotHereToPlayGames
    Generally speaking, I agree. But on the other hand, we really only have a FEW dozen folks that even follow MSFN. We really are a DYING BREED. I guess I also have the "advantage" of a USA flag by my name (population roughly 340,239,956) opposed to Germany (population roughly 83,289,087 [which is a lot higher than I would have guessed]).
  14. NotHereToPlayGames
    I tell everyone that my '55 Dodge is a hybrid. Because it has downswoop trim from a '56 Dodge.
  15. NotHereToPlayGames
    Us XP-users were just handed a new "definition". By this new definition, if you run ANY software on your computer that the CREATOR of that software used Win7 or Win10 in order to CREATE, then we can no longer label ourselves as a "real" XP user.
  16. NotHereToPlayGames
    Agreed. I'm still quite dependent on the caveman that invented the wheel some 5500 years ago.
  17. NotHereToPlayGames
    Since you say this often, are we allowed to ask if a certified board of education labels you as this, or is it just something you label yourself as? edit - and to make it fair, I dropped out of college after TEN YEARS, did not complete an actual degree, but still LABEL myself as an ENGINEER (but so does the company I work for ).
  18. NotHereToPlayGames
    Which does kind of make me wonder if Win 10 Pro could legally downgrade TWICE - once to Win7 Pro, the second to XP x64?
  19. NotHereToPlayGames
    Some also don't classify my i7-4770 to be "era-correct". It was launched in 2013 and came with Win7 which was released in 2009. Microsoft's own "downgrade rights" was still in effect as late as 2016 and perhaps even beyond. So YES, my hardware is "era-correct" per Microsoft's own "downgrade rights" licensing! But not "all" Win7 machines qualified for the FREE DOWNGRADE LICENSE (an UPGRADE to all of us that did it!). And the "downgrade rights" was only eligible if Microsoft provided support for the version of Windows that you were "downgrading" to. Extended support ended in 2014. So again, YES, my hardware is "era-correct".
  20. NotHereToPlayGames
    I consider myself a real XP user. Although some folks don't consider x64 XP to be as real as x86 XP. Was 360Chrome developed "upstream" using Win 10 SDK where XP support was merely an afterthought? No clue. But yes, I very highly suspect that 360Chrome would not exist without Win10 being used "upstream". But I also couldn't answer that for any of the roytam1 offerings or any of the feodor2 offerings. But again, I highly suspect that none of their offerings would exist without Win10 being used "upstream". Which reminds me, I have always wondered how the 1 and 2 came to be.
  21. NotHereToPlayGames
    Ah, I'll take your word for it.
  22. NotHereToPlayGames
    You're only showing the player's "start screen", does the video also PLAY for you?
  23. NotHereToPlayGames
    Depends on which "default" you are referring to. If he uses the "default" for running my releases as-is, then he's spoofing Win10 but maintaining v86. If he is not using my custom loader.ini, then his UA is his OS + v86.
  24. NotHereToPlayGames
    The .com works perfectly fine.
  25. NotHereToPlayGames
    https://en.wikipedia.org/wiki/History_of_general-purpose_CPUs https://siliconvlsi.com/why-does-32-bit-called-x86-while-64-bit-called-x64/
×
×
  • Create New...