Image Software & Virtual Memory

  • Thread starter Thread starter JCO
  • Start date Start date
J

JCO

Ghost Image or True
One situation I have & can't figure out how to handle is this:
I went from a large partition to a smaller one. The computer won't boot
because of the Virtual Memory is too small. I can't make changes since it
won't let me boot. Safe Mode won't work either. I don't want to run into
this situation when it really
matters. How do I resolve this.

Also;
After this happened, I thought it was some limitation of TrueImage Software.
It seems that Ghost did the same thing. I'm running Ghost from a disk that
was created from Norton 2004 Pro. It is, therefore, Ghost 2003 (not sure
what version this is)?

Anyway, the real issue I have is how to handle the Virtual Memory being to
small. Any other way to fix this without having access in windows?
 
Ghost Image or True
One situation I have & can't figure out how to handle is this:
I went from a large partition to a smaller one. The computer won't boot
because of the Virtual Memory is too small. I can't make changes since it
won't let me boot. Safe Mode won't work either. I don't want to run into
this situation when it really
matters. How do I resolve this.

Also;
After this happened, I thought it was some limitation of TrueImage Software.
It seems that Ghost did the same thing. I'm running Ghost from a disk that
was created from Norton 2004 Pro. It is, therefore, Ghost 2003 (not sure
what version this is)?

Anyway, the real issue I have is how to handle the Virtual Memory being to
small. Any other way to fix this without having access in windows?
Click to expand...

Usually when you restore an image, you restore to the same sized partition
as what the image originally came from. If you want to resize that
partition and make it smaller, do it after the restore is complete.
 
I suppose that is the usual thing to do. However, you should be able to
restore to a smaller or lager partition too. However, the data going on
this partition is less than 1/3 of the disk space that I'm going too.
That is what makes the situation strange. That is what brings up the
question ... how would you correct/change the Virtual Memory without booting
into Windows (which I can't do).
 
I suppose that is the usual thing to do. However, you should be able to
restore to a smaller or lager partition too. However, the data going on
this partition is less than 1/3 of the disk space that I'm going too.
That is what makes the situation strange. That is what brings up the
question ... how would you correct/change the Virtual Memory without booting
into Windows (which I can't do).
Click to expand...

I don't understand all of the technical details or terminology about how
images are restored but have read quite a bit about it. From what I
understand, on a 10GB partition with only 4GB of data, important file
system data may or may not reside at the end of that partition. It's the
"may exist" scenario that makes restoring to the same size partition or
larger, standard procedure.

While the 4GB of data can easily fit, say onto a smaller 6GB partition, the
bit by bit image restoration will not be able to place that necessary
marker at the end of the 10GB partition that it still expects to exist. The
restore will fail.

Resizing the partition after the restore will properly handle that last
little bit at the end of the partition and place it within the boundaries
of the new one.

As far as juggling the size of virtual memory before restoring an existing
image, you would have to consult tech support for your imaging program to
find out if it is possible with their program.

Virtual memory is comprised of RAM and pagefile.sys. You only have control
over pagefile.sys to a degree. Some image programs can be configured to
skip this file (it will be created at first boot by Windows so there still
may be some stumbling blocks to deal with if the partition is too small to
accommodate it) - or - you can move it before creating the image (this is
what I do). Doesn't help much at the moment but may want to give virtual
memory a little more attention when creating future images.
 
Thanks for the information and time you took to respond.
This is what I'm doing now:
I'm resizing the current partition smaller. I will then re-Image. After
the image is done, I will move it to the other HD (which should be bigger in
size).

I will let you know the outcome. I expect it should work fine.
 
Thanks for the information and time you took to respond.
This is what I'm doing now:
I'm resizing the current partition smaller. I will then re-Image. After
the image is done, I will move it to the other HD (which should be bigger in
size).

I will let you know the outcome. I expect it should work fine.
Click to expand...

You're welcome and good luck!
 
Resizing the current drive (1.5gig info on 10gig partition) down to a 5Gig
Partition using Partition Magic was successfull. I then made an image using
TrueImage Software. This image was used to put on another Hardrive, that
was larger than the 5GiG partion it came from. Everything was succefull.

The trick must be ... that it is safer to image to larger drive.

Thanks again.
 
Resizing the current drive (1.5gig info on 10gig partition) down to a 5Gig
Partition using Partition Magic was successfull. I then made an image using
TrueImage Software. This image was used to put on another Hardrive, that
was larger than the 5GiG partion it came from. Everything was succefull.

The trick must be ... that it is safer to image to larger drive.

Thanks again.
Click to expand...

That's great news and you're welcome again.
 
Back
Top