PDA

View Full Version : No paging file on boot


Peter
April 21st 03, 06:05 PM
Hi,

Pls read the following messages from MS:

Problems with Virtual Memory

It may sometimes happen that the system gives "out of
memory" messages on trying to load a program, or gives a
message about Virtual Memory space being low. Possible
causes of this are The setting for Maximum size of the
page file is too low, or there is not enough disk space
free to expand it to that size.


The page file has become corrupt, possibly at a bad
shutdown. In the Virtual Memory settings, turn off Virtual
Memory (check box), exit, shut down the machine, then
reboot. Delete PAGEFILE.SYS (on each drive if it exists on
more than just C:), turn Virtual Memory on again, and then
reboot to bring it into use.


The page file has been put on a different drive without
leaving a minimal amount on C:.


There is trouble with third party software. In particular,
if the message happens at shutdown, suspect a problem with
Symantec's Norton Live update, for which there is a fix
posted here. If it happens at startup and the machine has
an Intel chipset, the message may be caused by an early
version (before version 2.1) of Intel's "Application
Accelerator."
Uninstall this and then get an up-to-date version from
Intel's web site.


Possibly there is trouble with the drivers for IDE hard
disks; in Device Manager, remove the IDE ATA/ATAPI
controllers (main controller) and reboot for Plug and Play
to start over.


With an NTFS file system, the permissions for the root
directory of the drive where the page file is must give
"full Control"to SYSTEM. If not, there is likely to be a
message at boot that the system is "unable to create a
page file."

Hope it helps.

Peter

>-----Original Message-----
>When booting up I get the error:
>Limited Virtual Memory.
>Your system has no paging file, or the paging file is too
>small.
>I enable the paging file and set it. But when I reboot,
>it locks up. So I have to go to last known good config.
>where there is no paging file.
>Is this a virus? If so, what virus? If not, what is
>causing this scenario?
>Thanks.
>.
>

Google