Subject:
|
Re: Norton Ghost vs. Drive Image vs. ??
|
Newsgroups:
|
lugnet.off-topic.geek
|
Date:
|
Tue, 26 Feb 2002 04:53:58 GMT
|
Viewed:
|
136 times
|
| |
|
|
In lugnet.off-topic.geek, Larry Pieniazek writes:
> In lugnet.off-topic.geek, Brian Bacher writes:
> > Speaking as someone who has much experience with Norton's Ghost,
> > I have to say that I like it a lot. I haven't used Drive Image, so
> > I can't say anything about it. I haven't used the latest version,
> > so some of what I'm about to say may be irrelevant. It does support
> > NTFS, but there's a problem...you can't image to or from the partition
> > that you boot from. So if you boot from your current drive, you won't be
> > able to use it as a source drive, (or a target drive, not that you
> > care in this instance). If you boot from a DOS-type diskette, it won't
> > see the NTFS partition (and therefore Ghost won't see the drive). If you
> > have a second machine available, (with NT/2000 installed) that you can
> > place one or both of these drives into, it is pretty easy to work around
> > this limitation. Or a third, temporary drive would work in place of a
> > second machine. Like I said, they may have gotten around this somehow in
> > the newest version, I haven't used it yet.
>
> That helps a lot! Thanks!
>
> I guess I'm sort of stuck then as I only have one machine with only one
> internal drive and one external caddy (these are laptop drives). I HAD two
> machines as late as last week but turned one in. (however I did't have
> another bootable 2000 drive or another caddy either)
>
> I'm sensing that even if I had another network connected machine I could not
> safely copy from the boot drive of the first machine to the new drive, since
> the boot drive would be active. (that's why I think I would need two drive
> cradles, so that both machines would have a drive to boot from (the internal
> drive) and a drive to be source/destination for the imaging process)
>
> ++Lar
Dan's advice about installing from scratch is good. But I've also thought of
another work-around. A bit more time consuming, but it should work. If you boot
from the new drive, since it has 2000 on it, you could dump the contents of the
old drive to a file (on the new drive). This takes a *lot* more time than
cloning disk-to-disk, especially if you use compression. Then you can swap
drives around, reboot off of the old drive, copy/move the image file from the
new drive to the old drive (you may have to delete a bunch of stuff to make
room, but you should get it all back in the end), then dump the image onto the
new drive. When you swap drives back, all should be functional.
Alternatively, if you have a CD-R in this laptop, you can dump the image file
onto one or more CDs. Ghost 5.1 supports spanning; I'm sure that the new
version does also. Having an image file with all of the basic stuff installed
is quite handy if you tend to have to reload your machine on a semi-regular
basis.
A quick word about partion sizes, since Dan brought it up. With Ghost, as long
as you clone the *drive* and not the partition, and assuming that the drive has
only one partition and of maximum size, when you dump the file to a new, larger
drive, it should automagically expand the partion to fill the new drive. I have
done this before with desktop PCs when upgrading from, say, a 10GB to a 40GB,
and never had any trouble with this. If you have multiple partitions on the
source drive things don't always work this pretty; partition sizes change oddly.
Brian
|
|
Message is in Reply To:
 | | Re: Norton Ghost vs. Drive Image vs. ??
|
| (...) That helps a lot! Thanks! I guess I'm sort of stuck then as I only have one machine with only one internal drive and one external caddy (these are laptop drives). I HAD two machines as late as last week but turned one in. (however I did't have (...) (23 years ago, 25-Feb-02, to lugnet.off-topic.geek)
|
12 Messages in This Thread:
  
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
