Before I go back to the Staples guy...
Jul. 15th, 2010 01:07 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
gozerEdited for the solution: WOOT!
I tried a few things, but this seems to have fixed my problem: when I got my computer back on Monday, I had originally changed the DPI setting to Large (120 DPI) and slid the slider on the Display Properties: Setting box one over to the left. That made my screen images nice & big & viewable.
To fix the problem, I reset the DPI setting back to 96 DPI (normal, which is the default.) Then I pushed the slider on the Display Properties: Setting box over to the left once more to embiggen everything on the screen to make up for losing the Large DPI. Currently, my screen resolution is 1024 by 768 pixels. I've rebooted a few times and let the computer/monitor go to screensaver a few times and it hasn't gone to "Input Not Supported" even once!
Can anyone in the hivemind of LJ or DW help me with a computer problem? (Also, apologies for not replying to the lovely commenters on my previous posts -- I've been playing computer catch-up and will make time to do that tonight.)
Since I got my baby back on Monday, I have had a small problem. When the computer went to screensaver, the screensaver would be on for a few minutes, but after those minutes, the screen would go entirely black. If I then moved the mouse to bring the desktop back into focus and pop out of screensaver mode, instead I would get a box bouncing around that said "Input Not Supported" -- the box around those words had "HP" for Hewlett Packard (the make of my computer) on it. The only way to get the desktop (or whatever I had on the screen) back on the monitor would be to unscrew and then reseat and re-screw-in the DPI cable that attaches the monitor to the computer. Then, the monitor would work perfectly, like nothing had happened. But this happened over a dozen times over the next few days.
I did a google check and found there were a few others who had this problem, but none of their suggests were overly helpful. Some of the queries people made on tech sites went unanswered, others had people telling them to go into "safe" mode to do lines of type, which is something I don't feel comfortable doing.
I called the Staples repair guy and he had me do a right-click on the desktop to get into "Display Properties" on the Screensaver tab, then click the "Power" button. You get another box for Power Options, and he had me pick "NEVER" for all four of the choices you get there. Basically, he felt that after a few minutes of being in "screensaver" mode, the computer was slipping into "sleep" mode and that was... I don't know, doing something to cause the monitor to not understand and give me the Input Not Supported box. Now, when my computer screen rests, the computer itself never goes into sleep mode. Which begs the question, is it okay for a computer to never go into sleep mode?
SO, this actually did fix the problem -- I can walk away and go take a shower or go out to a store and when I come back, the screensaver image is on, not the "Input Not Supported" image.
Except that now when I turn on and boot up or restart the computer, it doesn't go to my desktop, it goes directly from loading Windows into "Input Not Suported". So every time I turn on the computer, I have to pull it out, unscrew the cable, reseat said cable and rescrew it in. Then the computer is fine and I can see my desktop.
I got the Input Not Supported box bopping about on my monitor when I turned on the computer for the first time after I got home on Monday night and put the system together -- I assumed that I simply hadn't screwed in the monitor cable properly and reseated it as a matter of course, so I didn't think anything of it at the time. For the next couple of days, I had to reboot the computer quite often (due to downloading over a dozen software packages and executing them), and I never had this problem once. But now that I've told the computer NOT to go to sleep mode when at rest, it's doing this when it starts instead.
Any ideas? Have any of you heard of this? No fear, I'm gonna called that guy at Staples in a bit, but I thought maybe one of you might have an idea first. This is the guy who assured me that my computer not going into sleep mode, ever, would not be a problem, so I'd love some feedback on whether or not I can trust him on this even if you don't know how to fix the DPI cable/monitor problem.
I tried a few things, but this seems to have fixed my problem: when I got my computer back on Monday, I had originally changed the DPI setting to Large (120 DPI) and slid the slider on the Display Properties: Setting box one over to the left. That made my screen images nice & big & viewable.
To fix the problem, I reset the DPI setting back to 96 DPI (normal, which is the default.) Then I pushed the slider on the Display Properties: Setting box over to the left once more to embiggen everything on the screen to make up for losing the Large DPI. Currently, my screen resolution is 1024 by 768 pixels. I've rebooted a few times and let the computer/monitor go to screensaver a few times and it hasn't gone to "Input Not Supported" even once!
Can anyone in the hivemind of LJ or DW help me with a computer problem? (Also, apologies for not replying to the lovely commenters on my previous posts -- I've been playing computer catch-up and will make time to do that tonight.)
Since I got my baby back on Monday, I have had a small problem. When the computer went to screensaver, the screensaver would be on for a few minutes, but after those minutes, the screen would go entirely black. If I then moved the mouse to bring the desktop back into focus and pop out of screensaver mode, instead I would get a box bouncing around that said "Input Not Supported" -- the box around those words had "HP" for Hewlett Packard (the make of my computer) on it. The only way to get the desktop (or whatever I had on the screen) back on the monitor would be to unscrew and then reseat and re-screw-in the DPI cable that attaches the monitor to the computer. Then, the monitor would work perfectly, like nothing had happened. But this happened over a dozen times over the next few days.
I did a google check and found there were a few others who had this problem, but none of their suggests were overly helpful. Some of the queries people made on tech sites went unanswered, others had people telling them to go into "safe" mode to do lines of type, which is something I don't feel comfortable doing.
I called the Staples repair guy and he had me do a right-click on the desktop to get into "Display Properties" on the Screensaver tab, then click the "Power" button. You get another box for Power Options, and he had me pick "NEVER" for all four of the choices you get there. Basically, he felt that after a few minutes of being in "screensaver" mode, the computer was slipping into "sleep" mode and that was... I don't know, doing something to cause the monitor to not understand and give me the Input Not Supported box. Now, when my computer screen rests, the computer itself never goes into sleep mode. Which begs the question, is it okay for a computer to never go into sleep mode?
SO, this actually did fix the problem -- I can walk away and go take a shower or go out to a store and when I come back, the screensaver image is on, not the "Input Not Supported" image.
Except that now when I turn on and boot up or restart the computer, it doesn't go to my desktop, it goes directly from loading Windows into "Input Not Suported". So every time I turn on the computer, I have to pull it out, unscrew the cable, reseat said cable and rescrew it in. Then the computer is fine and I can see my desktop.
I got the Input Not Supported box bopping about on my monitor when I turned on the computer for the first time after I got home on Monday night and put the system together -- I assumed that I simply hadn't screwed in the monitor cable properly and reseated it as a matter of course, so I didn't think anything of it at the time. For the next couple of days, I had to reboot the computer quite often (due to downloading over a dozen software packages and executing them), and I never had this problem once. But now that I've told the computer NOT to go to sleep mode when at rest, it's doing this when it starts instead.
Any ideas? Have any of you heard of this? No fear, I'm gonna called that guy at Staples in a bit, but I thought maybe one of you might have an idea first. This is the guy who assured me that my computer not going into sleep mode, ever, would not be a problem, so I'd love some feedback on whether or not I can trust him on this even if you don't know how to fix the DPI cable/monitor problem.
