Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
Can someone post a script or link or any advice so I would be able disable my screen saver when I open a certain program and re-enable it when I close it. The problem is I run this program daily and when the screen saver goes on it either slows the program or crashes it...don't know why. I know I could disable the screen saver completely but I'm looking for another way. Either a script or a batch. Thanks.

You could run a batch to rename the screen saver.
Seems mickey-mouse, but should work.
::== noSS.bat
ren c:\winnt\system32\scrnsave.scr scrnsave.sc-
myAPP.exe
ren c:\winnt\system32\scrnsave.sc- scrnsave.scr
If at first you don't succeed, you're about average.M2

"The problem is I run this program daily and when the screen saver goes on it either slows the program or crashes it...don't know why"
You probably need to just choose another screen saver - some screen savers are VERY CPU intensive.
Here's true story. As a "default" sys admin at a small company (default because I was the only one who knew anything about PCs) I added the company logo to one of the 3d rendering screen savers. I then proceeded to put it on all the computers in the building.
I started to get complaints from people that one of the applications they used was very slow and they said it happened after I put the screensaver on their computer. I said that it was impossible that the screensaver on their computer would slow down an application while they were using it.
This went on for a couple of weeks. Then I needed make a change on the server. When I saw that I had also put the screen saver on the server it hit me! The application they were having trouble with was hosted on the server! I quietly changed the server's screen saver to a blank screen. Everyone asked what I changed to speed up the program - I just said that I didn't do anything, it must have just worked itself out. LOL. Good times!
Michael J

Yeah,
Not to mention that modern monitora don't need saving.
That goes back to the days of DOS and crappy phosphor. The screen would spend half it's life showing:
c:\dbase_
So, not surprisingly, that image would eventually be burned into the screen.
If at first you don't succeed, you're about average.M2

![]() |
Inheritance and Type Conv...
|
Newb Programmer looking f...
|

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |