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
    Do not waste your time. It is much easier for a fifth-grader to understand college calculus than it is to understand the topic matter you are seeking to understand.
  2. NotHereToPlayGames
    Already have. Win 10 is never going to start up as fast as Win XP.
  3. NotHereToPlayGames
    ZERO effect. Minor fluctuation is to be expected and the "Balanced" power plan and the "High performance" power plan are statistically identical. It can be argued that MAX minus MIN (for my SMALL sample size) is narrower for "High performance" than it is for "Balanced" (but what are a few hundred milliseconds when it takes the OS a full MINUTE to boot?). But it can also be argued that this sample size demonstrated an AVERAGE boot time for "Balanced" at 57.35 seconds, 0.09 seconds FASTER than the AVERAGE boot time for "High performance" at 57.44 seconds. Granted, I chose not to log dozens upon dozens of reboots with each. But this seems more than enough to demonstrate ZERO effect. Boot time is the best "performance" indicator that I can think of because a "hundred" different processes are all fighting for CPU cylces in rapid succession.
  4. NotHereToPlayGames
    Same here, to be honest. I actually prefer to see "squares" when non-Latin folks try to force non-Latin "characters".
  5. NotHereToPlayGames
    All good here. Especially the "Configure PopMenu.exe" note because I missed this when trying to set everything up without reading any documentation first (which is my normal default, I don't read an owner's manual before test driving a car, lol).
  6. NotHereToPlayGames
    I'll try this later (edit - uninstalled 10 and put XP back on the laptop, now installing 10 again). In the past, this has made ZERO effect, but I'll check again.
  7. NotHereToPlayGames
    Not a dual-boot. I removed Win10 and put XP x64 on the same exact laptop. Boot time decreased from 58 - 62 seconds all the way down to 19.3 to 20.3 seconds. Win10 takes three times as long to boot as XP on the same exact laptop.
  8. NotHereToPlayGames
    H#LL NO! I firmly boycott any-and-all AV! They only KILL performance and throw nothing but FALSE ALARMS and NEVER prevent "zero-day" vulnerabilities.
  9. NotHereToPlayGames
    I'm "new" to Win10 (outside of "default" LTSB install on work computer). (edit - can't really call it "default" due to corporate IT "stuff" also on the work computer, but I don't have that on my Win10 reference home laptop.) The "pandemic" has enabled me the opportunity to install work's LTSB on one of my home laptops. I'm still in-process of tweaking, but so far I can barely beat ONE MINUTE for boot time - that is an ETERNITY when all of my XP machines boot between 18 and 34 SECONDS! My boot time ranges from 58 seconds to 62 seconds. Basically double that of my XP boot times.
  10. NotHereToPlayGames
    I can "tolerate" Win10. But only the LTSB version and not the XBox / Candy Crush / Metro App b#llcr@p "normal" version.
  11. NotHereToPlayGames
    Depends on your line in the sand. I tinker and optimize and do my thing. And when one of the brothers is over and I boot up a machine, I kinda enjoy that they think we need to walk away from the computer and "wait" for it to boot up because they think computers need three minutes to boot up but mine boots in twenty seconds. And I just laugh and laugh and laugh when they throw out, "No way! That thing is like 15 years old and mine is brand new, why is mine so SLOW?" Because you installed using "defaults". "It's not rocket science." But I draw the line at chasing my tail like a dog on some things I see folks around here do that I don't see any benefit to - but to each their own.
  12. NotHereToPlayGames
    Everything working. XP x64 and XP x86.
  13. NotHereToPlayGames
    No prob, lol. The version you sent me just now WORKS even with SPACES in the path names
  14. NotHereToPlayGames
    Please revisit the PM. You gave me the same EXACT link for both versions - so it appears that I never got the updated version.
  15. NotHereToPlayGames
    Redownloading from second PM link.
  16. NotHereToPlayGames
    Yes, I have replaced them. Multiple times.
  17. NotHereToPlayGames
    Changing it to C:\Prox HTTPS Proxy\ProxHTTPSProxy_noUPX\PopMenu does not work either. The ONLY way for me to get it to work is to NOT have any spaces in the ROOT folder .
  18. NotHereToPlayGames
    And it is NOT path link size. Even C:\Prox HTTPS Proxy does not work! Where the PopMenu folder is then at C:\Prox HTTPS Proxy\ProxHTTPSProxy_REV3e_PopMenu_3V1_noUPX\PopMenu
  19. NotHereToPlayGames
    Working here. But I have to use a folder with NO SPACES.
  20. NotHereToPlayGames
    At least three 404's (out of only six attempted downloads). Didn't track which files were 404's.
  21. NotHereToPlayGames
    Was just "thinking out loud".
  22. NotHereToPlayGames
    I haven't gotten that far yet - but here is the vision I have for this project -- spoof specific browser engines! Not sure if that is even possible, but I see that as being what the future really needs. Doesn't matter if you are running NM27, NM28, St52, St55, 360Chrome v11, v12, v13, v13.5, Pale Moon, Official Chrome, Official Firefox - be able to trick Cloudfare servers into thinking we are on anything we want to spoof. Because the end user USED TO be able to do that just by changing their User Agent - this no longer works with the "modern web".
  23. NotHereToPlayGames
    Yep, it is working with and without spaces using the second set of files. My tests have been somewhat limited so far. Correction - see PM.
  24. NotHereToPlayGames
    I have most of my VM's set up to access a "shared" .vdi "hard drive". So my VM x86 was seeing everything at "E:\ProxHTTPSProxy_REV3e_PopMenu_3V1" whereas my host machine (x64) was seeing everything at "C:\Documents and Settings\Admin\Desktop\ProxHTTPSProxy_REV3e_PopMenu_3V1". I think we can all be on one PM. That way none of us report something we find that somebody else already found.
  25. NotHereToPlayGames
    Dave-H beat me to the punch. I knew it wasn't working in my x64 and that it was working in my x86 VM - didn't narrow it down to path names though. Good catch.
×
×
  • Create New...