No Page files.

[EricV]

I am getting "your system has no paging file" error.

Installed fresh windows 2000 on on pc with all the patches and updates.

I ghosted the hard disk drive into another similar pc now here is the error
that I get in safe mode or normal and can not pass it even if I enter goes
or o.k. or anything.

"Limited Virtual Memory"

Your system has no paging file, or the paging files is too small"

Please help.



Thanks.

 

[Dan Seur]

Create a properly sized page file.
See Start/Help/Search if you don't know how.
Apparently the 2 systems weren't quite similar enough.
Sys1 has the pagefile on a drive that doesn't exist on Sys2 methink.

I am getting "your system has no paging file" error.

Installed fresh windows 2000 on on pc with all the patches and updates.

I ghosted the hard disk drive into another similar pc now here is the error
that I get in safe mode or normal and can not pass it even if I enter goes
or o.k. or anything.

"Limited Virtual Memory"

Your system has no paging file, or the paging files is too small"

Please help.



Thanks.




---
avast! Antivirus: Inbound message clean.
Virus Database (VPS): 0616-2, 04/18/2006
Tested on: 4/19/2006 12:14:57 PM
avast! - copyright (c) 1988-2004 ALWIL Software.
http://www.avast.com

---
avast! Antivirus: Outbound message clean.
Virus Database (VPS): 0616-2, 04/18/2006
Tested on: 4/19/2006 12:19:22 PM
avast! - copyright (c) 1988-2004 ALWIL Software.
http://www.avast.com

 

[John John]

His system doesn't boot, Dan. It's a known issue when ghosting drives
without taking proper steps or precautions before creating the ghost image.

Most likely the system/boot volume letters at
HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices don't match or were changed
during the cloning process. It can be changed by network access or
mounting the drive in another Windows 2000 machine and changing the
value. One of the MVPs will certainly come by and tell the OP how to do
it. If not I'll dig up the relevant KB articles for the OP latter on.
It's usually not that hard to fix but there may be other issues that pop
up when you try to fix this so I would prefer that one of the MVPs take
it up, so that proper follow up can be given to the OP if needed.

John

 

[Dan Seur]

Oops - missed that, thanks JJ

His system doesn't boot, Dan. It's a known issue when ghosting drives
without taking proper steps or precautions before creating the ghost image.

Most likely the system/boot volume letters at
HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices don't match or were changed
during the cloning process. It can be changed by network access or
mounting the drive in another Windows 2000 machine and changing the
value. One of the MVPs will certainly come by and tell the OP how to do
it. If not I'll dig up the relevant KB articles for the OP latter on.
It's usually not that hard to fix but there may be other issues that pop
up when you try to fix this so I would prefer that one of the MVPs take
it up, so that proper follow up can be given to the OP if needed.

John





---
avast! Antivirus: Inbound message clean.
Virus Database (VPS): 0616-2, 04/18/2006
Tested on: 4/19/2006 2:59:02 PM
avast! - copyright (c) 1988-2004 ALWIL Software.
http://www.avast.com

---
avast! Antivirus: Outbound message clean.
Virus Database (VPS): 0616-2, 04/18/2006
Tested on: 4/19/2006 3:00:19 PM
avast! - copyright (c) 1988-2004 ALWIL Software.
http://www.avast.com

 

[John John]

You should be able to resolve this by following these instructions:

Unable to log on if the boot partition drive letter has changed
http://support.microsoft.com/kb/249321

You will have to access the drive over a network, or slave it in another
Windows 2000/XP machine and use Regedt32 to do the changes.

These other articles may also be helpful:

"Limited Virtual Memory" Error Message When You Start Your Computer
After You Install Or Remove a Hard Disk
http://support.microsoft.com/kb/812448

How to restore the system/boot drive letter in Windows
http://support.microsoft.com/kb/223188

John