D
dcdon
Recently problems with pagefile.sys has caused many trepidatious momemts. I
have rebuilt my pagefile.sys several times and now it seems to be okay. The
last time, I used what I thought caused the problem in the first place. This
is what I did, and then my question. On a trustworthy site, (is there such a
thing), it was said that in some cases performance could be gained by
setting the applet to both zeros. On reboot, I was to reset the sizes in the
applet to RAM + 32Meg. When, reboot, 20 Meg was on the initial window (as if
it had created tempf.sys), but when I set the sizes and Ok'ed out, the
computer would boot (so I had the automatically reboot on BSOD). After
unchecking the auto reboot, I found that I could reset the size in the
registry, and I could make the initial adn max smaller, but each time I
tried to increase, BSOD.
I did finally make it small enough that it generated a temppf.sys. That's
when I used regedt32 to regenerate the pagefile, after changing the
extension on the original. This did okay, but something would cause the
squawk of a temppf.sys to be created. And I had to rebuild the pagefile
several times. One of those times, I had taken back "full control" from
NTAUTHORITY/system. After relenquishing the control again, I did get
pagefile.sys set. But it still has full control.
And now for the question. Does NTAUTHORITY need to retain "full control"
indefinitely, and if so, "will this cause a problem or vulnerability???""
Postscript: I did see the M$ article on setting a pagefile to zero, and
after boot, setting the size to a minimum of RAM+32Meg Minimum. I did that
and it works and it looks to be doing just fine. I believe all of this is
caused by some type of attack or infection, and believe me, I run a tight
ship. I have run every kind of fixtool imaginable exactly by the directions
from Symantec and other AVP vendors and have found no infection of any kind,
as if that was to make me feel better.
I've also had trouble with Event Viewers being visible. I believe one of the
first in this NG, rebuilt them and don't seem to have any further problem
there, but one can never tell the way clocks coded in and all manner of
variants, and growing. All that I have done has been with the generous help
of great people in here. Thanks guys.
thanks very much,
don
-------
have rebuilt my pagefile.sys several times and now it seems to be okay. The
last time, I used what I thought caused the problem in the first place. This
is what I did, and then my question. On a trustworthy site, (is there such a
thing), it was said that in some cases performance could be gained by
setting the applet to both zeros. On reboot, I was to reset the sizes in the
applet to RAM + 32Meg. When, reboot, 20 Meg was on the initial window (as if
it had created tempf.sys), but when I set the sizes and Ok'ed out, the
computer would boot (so I had the automatically reboot on BSOD). After
unchecking the auto reboot, I found that I could reset the size in the
registry, and I could make the initial adn max smaller, but each time I
tried to increase, BSOD.
I did finally make it small enough that it generated a temppf.sys. That's
when I used regedt32 to regenerate the pagefile, after changing the
extension on the original. This did okay, but something would cause the
squawk of a temppf.sys to be created. And I had to rebuild the pagefile
several times. One of those times, I had taken back "full control" from
NTAUTHORITY/system. After relenquishing the control again, I did get
pagefile.sys set. But it still has full control.
And now for the question. Does NTAUTHORITY need to retain "full control"
indefinitely, and if so, "will this cause a problem or vulnerability???""
Postscript: I did see the M$ article on setting a pagefile to zero, and
after boot, setting the size to a minimum of RAM+32Meg Minimum. I did that
and it works and it looks to be doing just fine. I believe all of this is
caused by some type of attack or infection, and believe me, I run a tight
ship. I have run every kind of fixtool imaginable exactly by the directions
from Symantec and other AVP vendors and have found no infection of any kind,
as if that was to make me feel better.
I've also had trouble with Event Viewers being visible. I believe one of the
first in this NG, rebuilt them and don't seem to have any further problem
there, but one can never tell the way clocks coded in and all manner of
variants, and growing. All that I have done has been with the generous help
of great people in here. Thanks guys.
thanks very much,
don
-------