Re: MISSING PAGEFILE.SYS FILE

Sorry for the fog. Boot.ini is in c:\. No pagefile.sys anywhere. All boxes
are checked on the Everyone group. As you already surmised, reveal of
properties for the C drive shows it as an NTFS file system. I'm at a loss.

"George Hester" wrote:

OK I do not know why you are doing this C:\root. What you mean is the root
C: I hope. Not a folder on C drive called root. Again where is your
boot.ini? If you do not see it then you have not enabled viewing all files
correctly like I suggested you do earlier. Or you are not using NTFS but if
you can set permissions you must be.

There is no need to have a seperate permissions set for the System account
on the root. The Everyone Group is sufficient with Full NTFS permissions -
Everything checked allow Full Control | Modify... and so on. Nothing else.

--

George Hester
_________________________________
"Blake" <blaketexas(no_spam)@aol.com> wrote in message
news:EC75070B-6CA8-460F-93B4-6414CF46EAFB@xxxxxxxxxxxxxxxx
Hello, George...

Thanks for riding along.

Agree that there's a permissions problem. Have gone into properties for
the
c:\ root and killed all permission groups except Everyone Group and
System.
Am still not getting apagefile.sys file created. I can make changes all
day
long in the GUI or registry, and they'll save, but no file is created. No
pagefile.sys exists, although boot.ini does reside in the c:\ root.

All permission options are checked for both Everyone and System.

BTW, have uninstalled and reinstalled Norton AV 2005. Am having a problem
there with Liveupdatehandling properly.

Am beginning to wonder if I have a partial SP-2 installation problem. I'm
running out of things to do to allow Windows to write the pagefile.sys.

Blake


"George Hester" wrote:

The issue is a NTFS Permissions problem. You still should have a 25MB
pagefile.sys somewhere most likely in C:\Windows but it should be on the
root C:.

You had said this, "[I] Believe all permissions are properly set for
both
the Administrator and my own user account..." There should be nothing
more
or less than the Everyone Group having Full NTFS permssions on the root
C:
And you must set those permissions using the Admin account. Is your
boot.ini also on the root C:?

--

George Hester
_________________________________
"Blake" <blaketexas(no_spam)@aol.com> wrote in message
news:2D173F79-B9ED-43D3-A817-D7EFEE56F63F@xxxxxxxxxxxxxxxx
"Everyone" is set for full permission. All settings are continuing to
register (I can see them on the virtual memory page accessed by using
control
sysdm.cpl or going to the Registry and viewing the setting under
"Memory
Management") But no pagefile.sys is apparently being created.

I can't believe I'm the only person who has followed all the
directions
and
not been able to get pagefile to work <G!>.

I started to install SP2 and believe I stopped it before it actually
installed (got cold feet about the quality of my backup at the time).
Could
this be a part of the problem? Seems likely not.

Interestingly, I also cannot rollback and use any previous restore
point --
that was one of my earlier attempts at solving the problem. The
system
says
it can't be done and that no changes have been made.

"George Hester" wrote:

The article says this at the end:

However, the Everyone group includes the System account. Removing
the
Everyone group without adding the System account as an individual
account
renders the paging file unusable

You need to make sure that Everyone has FULL permissions on the Root
of
the
drive where pagefile.sys resides. Everyone does not mean everyone
in
the
world. What it means is Everyone that has permissions to log into
the
system. Set the NTFS permissions on the Root to haveFULL permissions
and
do
not reset the permissions to propagate to all subfolders subobjects.

--

George Hester
_________________________________
"Blake" <blaketexas(no_spam)@aol.com> wrote in message
news:6F29B2DD-1396-4A7E-B753-5842628E7A1F@xxxxxxxxxxxxxxxx
Have read a number of posts about pagefile.sys problems, and been
through
<much, most?> of the excellent aumha.org content, the Microsoft
Knowledge
Base and this user group, and am still baffled.

I can reset the min./max. size of the pagefile in either the GUI
panel
or
in
the registry. In either case, it shows the changes as having been
accepted,
but I continue to get the missing pagefile error message when
restarting
XP.> > > Believe all permissions are properly set for both the
Administrator and my
own user account, following instructions in the XP KB file
(315270).
I have tried to make the change in both the Administrator and user
account

One other rub -- I cannot find pagefile.sys in the C:\ (root)
directory,
even though that's where the system says the pagefile is located.
I
have
set folder options to show hidden files/folders and to not hide
protected
files.



I believe the fact I can't see a pagefile.sys is a critical part
of
the
story. Am running under SP-1, Symantec is disabled (for now).

Any thoughts?






.

Relevant Pages

  • Re: MISSING PAGEFILE.SYS FILE
    ... Agree that there's a permissions problem. ... c:\ root and killed all permission groups except Everyone Group and System. ... "George Hester" wrote: ... the Everyone group includes the System account. ...
    (microsoft.public.windowsxp.general)
  • Re: MISSING PAGEFILE.SYS FILE
    ... I want you to go to the root of each of your ... first and if you have other drives I want you to do the same thing on each. ... "George Hester" wrote: ... There is no need to have a seperate permissions set for the System ...
    (microsoft.public.windowsxp.general)
  • Re: MISSING PAGEFILE.SYS FILE
    ... "George Hester" wrote: ... I want you to go to the root of each of your ... drives do this and paste back here the results of each file you will make. ... There is no need to have a seperate permissions set for the System ...
    (microsoft.public.windowsxp.general)
  • Re: Use SilverKeeper until time machine ships
    ... Knowledgeable unix administrators will know if and how it should be ... The 'root' permissions should only be needed when the core UNIX ... installation needs to be altered, ...
    (comp.sys.mac.system)
  • Re: Modifying sudoers
    ... >> Right now it seems that 'sudo' gives the same permissions as root. ... >> want any user to do admin work. ... damage to the systems installation. ...
    (comp.sys.mac.system)