Jump to content

NotHereToPlayGames

Member
 View Profile  See their activity

  • Posts

    6,856

  • Joined

  • Last visited

  • Days Won

    87

  • Donations

    0.00 USD 

  • Country

    United States

 Content Type 

Everything posted by NotHereToPlayGames

  1. NotHereToPlayGames
    They could have just been "click here for more details" types of Chinese search engine links. Regardless, something I have no use for.
  2. 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".
  3. 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.
  4. 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.
  5. 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]).
  6. NotHereToPlayGames
    I tell everyone that my '55 Dodge is a hybrid. Because it has downswoop trim from a '56 Dodge.
  7. 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.
  8. NotHereToPlayGames
    Agreed. I'm still quite dependent on the caveman that invented the wheel some 5500 years ago.
  9. 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 ).
  10. 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?
  11. 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".
  12. 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.
  13. NotHereToPlayGames
    Ah, I'll take your word for it.
  14. NotHereToPlayGames
    You're only showing the player's "start screen", does the video also PLAY for you?
  15. 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.
  16. NotHereToPlayGames
    The .com works perfectly fine.
  17. 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/
  18. NotHereToPlayGames
    My builds spoof Win10 but do not spoof away from v86. My builds use - Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.198 Safari/537.36
  19. NotHereToPlayGames
    Again, I have never heard of an "accelerate discharge battery" option in Win10. Please provide why you think such a thing exists. You could just have a NEAR-DEAD battery and you are blaming Win10 when it is really your NEAR-DEAD battery.
  20. NotHereToPlayGames
    Works for me. Did you disable your beloved uBO or try in Incognito before reporting?
  21. NotHereToPlayGames
    Agreed. But I think Windows has a way to "restore" Registry edits that Windows itself doesn't think you should be editing. I could be thinking of only Windows Defender and not Windows Updates.
  22. NotHereToPlayGames
    Not so sure that would work. Windows has a way of using its "system32" folder to bring back anything that Windows itself thinks you "didn't really intend to delete" even though you knew exactly why you were deleting it.
  23. NotHereToPlayGames
    Ok. But that wasn't a "question", it ends with a "." and not a "?" But yes, if NTLite was part of MSFN, then I guess there is no reason that WinReducerEX can't be. Though it sounds like it was because the author of NTLite was an MSFN Member whereas the author of WinReducerEX is not.
  24. NotHereToPlayGames
    What questions did I ask? I don't recall "asking" any.
  25. NotHereToPlayGames
    One of my tricks, I will unpack ALL of my extensions and REMOVE the "description" line because I don't want it displayed on my chrome://extensions page, then repack them before drag-and-drop (Developer mode NOT needed, I've actually NEVER used "Developer mode"). This also CHANGES the extension's 32-digit "string" to something that would never match anything at CWS.
×
×
  • Create New...