• rd23

    rd23

    @rd23

    Viewing 15 replies - 31 through 45 (of 71 total)
    Author
    Replies
    • in reply to: How to Retain Restore Points? #2251937

      To @Linda2019, my question about your original question, is why you would want restore points that are 30 days old?

      By that time, so much would’ve happened to the computer, that they would be useless to restore from.

      In other words, if one has close to daily restore points, only the last few would be useful for a recovery from some problem. (Sort of like that joke about how fast one has to run to outrun a bear.)

      E.g., right now, on 4-18, I have restore points for 4-1, 4-7, 4-8, 4-9, 4-10, 4-13, 4-14, 4-16, 4-17. And that is far enough back for me. Anything older wouldn’t be of any use.

       

      • This reply was modified 5 years, 1 month ago by rd23.
    • in reply to: Screen Brightness #2233489

      There are 3rd party utilities for that. E.g. ScreenBright.

      See “10 Free Tools to Adjust Screen Brightness, Contrast, Gamma or Temperature” at https://www.raymond.cc/blog/software-to-adjust-monitor-brightness-and-contrast-for-dell-studio-one-desktop/

       

       

      • This reply was modified 5 years, 1 month ago by rd23.
      1 user thanked author for this post.
    • in reply to: How to Retain Restore Points? #2232648

      Where is that PowerShell script posted?

      I have your Version No: 1.4  from July 2011, but don’t know where to look for updates.

      • This reply was modified 5 years, 1 month ago by rd23.
    • in reply to: Want to Reply to a post? Hit Reply twice. #2214166

      (This is via “Reply” while other posts were with via “Submit” to avoid being nested.)

      Adding to the confusion of where the problems may be, I just upgraded from Windows 7 (Home) to Windows 10 (Home) in late February, so in some ways my computer is the same, but different.

    • in reply to: Want to Reply to a post? Hit Reply twice. #2214141

      E.g., I just filled out a support form on NetZero, and upon attempting to submit it, I got:

      “There was an error processing your request.  Please try again in a few moments.”

      Almost every where I go and fill out a web form, it bombs somehow.

       

      • This reply was modified 5 years, 1 month ago by rd23.
      • This reply was modified 5 years, 1 month ago by rd23.
      1 user thanked author for this post.
    • in reply to: Want to Reply to a post? Hit Reply twice. #2214132

      I only had to hit Submit once, so it appears to be fixed, like stated above.

      Now if Woody’s devs could just fix the rest of the Internet.

      1 user thanked author for this post.
    • in reply to: Want to Reply to a post? Hit Reply twice. #2214112

      Lately I’ve had a lot of web pages (on the Internet in general) that I’ve had to make two attempts to load.

      And many other things simply acting “funny” (on the Internet in general).

    • in reply to: traditional file manager/windows explorer #2124232

      When I upgraded from XP to Windows 7 I paid the $80 for the Lifetime Pro License, and still feel it was money well spent.

      2 users thanked author for this post.
    • in reply to: traditional file manager/windows explorer #2124020

      Try XYplorer. It is worth paying for.

      2 users thanked author for this post.
    • That’s what I’ll try if there is a next time.

      (Though I am still curious what is happening “under the hood.”)

    • All the “usual suspects” aren’t guilty, which makes it harder to pin down the real ones.

    • Once booted back into Windows, if I see the red X, letting Windows try to repair the problem always fails.
      Going back to a restore point always fixes it, which is why I’ve gotten lazy.
      I have lots of diagnostic programs, and viruses are not the problem.

      I have had faulty drivers cause crashes, so am very careful what drivers get updated, using something like the same caution the the Patch Watch column here uses. (Which is why I got the idea of asking my problem here, as every newsletter has those wonderful examples of Lounge posts solving a variety of problems.)

      The problem happens very rarely, and when it does, I’m usually in a hurry to get up and running again, having had to boot into Safe Mode to be able to get back to the restore point.

      When I have taken time to turn on my other computer (an older Dell running XP) to do searches for the problem, I haven’t found any advice that actually helps. I was wondering if anyone here has had the same problem, and has found a more pinpointed solution.

    • I should add that that these crashes are where something got out of control, and I had to power cycle the machine to regain control.

      Some times I rebuilt the page file out of habit, since it might have been corrupted, but that didn’t seem to help, so I just re-boot now, to try my luck, in case it does boot OK. But, if not, then LKG can’t be used, and i have to use the last restore point, which i now save daily.

    • The system is a Dell with sound built into the motherboard, and came with Win7 64-bit HP installed already.

      I am not using sound when the crash happens, and most of the discussions I’ve seen revolve around the sound not working, which is not the actual problem. The red X not disappearing is a sign that something is wrong with the system, that also prevents other programs from working.

      In the “old days” (NT4 era) I would use the Last Known Good item upon re-booting, or maybe re-build the page file, in case it got corrupted.

      This problem happens rarely, and going back to a restore point, which I now save daily, fixes it.
      And once back up, I’m in a hurry to get back to what I was doing.
      I’d like to know what got fixed, so that maybe I could do just that, instead.

    • in reply to: Bsod #1300466

      After some discussion with a Dell tech on their support forum, they sent me some replacement RAM, which seems to have solved my problems. I learned that Dell machines are finicky about RAM, and that I should have spent time when I first got the machine to test everything on a hardware level before proceeding to the OS and sofware usage.
      A lesson also learned is that it is not necessarily what the BSOD shows for the reason, but that if it is due to hardware, whether you get BSODs or not is the issue.

    Viewing 15 replies - 31 through 45 (of 71 total)