Jump to content

NotHereToPlayGames

Member
  • Posts

    2,547
  • Joined

  • Last visited

  • Days Won

    63
  • Donations

    $0.00 
  • Country

    United States

Everything posted by NotHereToPlayGames

  1. I do not work in IT. This is just a hobby. I've spent DECADES tweaking XP. I am only roughly two months in on testing Win7 and Win10. Had to NTLite them both very heavily and it's still a work in progress.
  2. This is what my Win7 is showing. I wouldn't call this "everything" that I do, but I'll still axe these logs now that I know about them.
  3. Do you know if you use hibernate or sleep? I have less then 15 seconds when coming out of hibernate (which is all I do 95% of the time). But a full MINUTE for "restart" (ie, full shutdown).
  4. Win10 has basically become my "backup plan". I prefer XP for everything. But there will come a day that I won't be able to access my online banking so I went on a quest for an alternative OS. I have Win7 on a different laptop but so far I'm liking Win10 LTSB better.
  5. The only entry my LTSB has under that key is a DWORD named "Status" with a value of 0.
  6. All I get is - 'logman' is not recognized as an internal or external command, operable program or batch file. My Win10 is LTSB. Corporate OS. My hunch is that my Win10 doesn't do "as much" logging as non-LTSB. I can't clain it doesn't to "any" logging. Still "new to me" as far as tweaking/optimizing.
  7. Agreed! That's why I never enable Fast Startup. My computer does a full RESTART in 58 to 62 seconds. "Restart" recreates all RAM, nothing is saved to be restored with the next power-up. What Fast Startup is for is the "shutdown" option from your Start menu. A "shutdown" with Fast Startup enabled writes the kernel to the hard drive and puts that back into RAM on the next power-up. A "shutdown" with Fast Startup enabled still takes 58 to 62 seconds! A *true* hibernate writes the entire contents of RAM to the hard drive then puts that back into RAM on the next power-up. My computer comes out of a *true* hibernate in 8 to 12 seconds.
  8. "Fast startup" is definitely a marketing ploy based on my tiny test --
  9. How do you measure your startup time? BootRacer is the best thing I've been able to find.
  10. Agreed. When I was big into overclocking, I would actually run my CPU at reduced frequencies and the CPU would run 10-15 degrees C cooler. Overclocking would only kick in when demand required it (like stepping on the gas and the car downshifts to pass grandma).
  11. The "Fast startup" setting says "restart is not affected".
  12. "Fast startup" is nothing but a 'hybrid hibernation' state. I use full hibernation when I want to hibernate and full shutdown when I want to shutdown. So the "fast startup" is disabled on purpose.
  13. I'm personally of the opinion that the MAT Drama is a "toxic environment" that should probably be "limited" to its own dedicated area here at MSFN. It's like Court Room TV or Soap Operas - I know they "exist", but my life is better off not spending ANY of my time to tune into them
  14. 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.
  15. Already have. Win 10 is never going to start up as fast as Win XP.
  16. 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.
  17. Same here, to be honest. I actually prefer to see "squares" when non-Latin folks try to force non-Latin "characters".
  18. 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).
  19. 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.
  20. 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.
  21. 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.
  22. 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.
  23. I can "tolerate" Win10. But only the LTSB version and not the XBox / Candy Crush / Metro App b#llcr@p "normal" version.


×
×
  • Create New...