Zaidy036 wrote:
On 1/4/2019 7:42 PM, Bill in Co wrote:
Paul wrote:
Bill in Co wrote:
J. P. Gilliver (John) wrote:
In message , Char Jackson
writes:
[]
I'm probably in the minority but I'm one who doesn't make a rescue CD
(actually USB) until I actually need it. Then I use it and promptly
toss the thumb drive back in the pile to be recycled for other uses.
Someone who has a single PC is probably better off creating and
storing a rescue disc but that's not my situation here.

That's my point - "when I actually need it" is too late for a
single-PC user, if "need it" means the PC won't boot, for whatever
reason (hardware drive failure, you've done something silly, or
malware). You can't then _make_ the CD (or USB).

+1

That's one of the benefits of buying an image program already
containing a boot CD as part of its package, like Acronis True Image
(ATI), and you can make a bootable flash drive too. The only problem
I've had with Acronis True Image is that it's become more bloated and
less straightforward in its interface with each succeeding generation.

Well, that, and the fact that when I try to use a flash drive ATI boot
loader on my laptop to do a restore image operation, it wants to
restore the image to D: instead of C:, since it seems to see its own
boot Linux OS as C: - which is very annoying.

That's probably a WinPE disc. The boot drive on those
is normally a RAMdrive at X: .

Linux doesn't use Windows lettering as a rule. A typical
Linux might use /media/mount/partition_label or
/media/mount/hex_string_of letters as names when
auto-mounting.

The Bash shell in Windows 10 might use /mnt/c/windows/system32
as their style. Kasperksy rescue disc might use /mnt/c:
but that's about as close as they get to a Windows name
as such.

Whereas WinPE command prompt will use regular drive
letters, and it peeks into a randomly selected
Windows registry to decide how to do the naming.
If you have two boot OSes, what will it do ?
It's either that, or name the partitions in order
of hardware discovery during boot.

Paul

So you mean I'm kinda stuck with that behavior? It's a bit problematic,
because when I tried it on the Win 7 laptop, even though it did the
restore operation mostly ok, there was at least one weird issue that
remained as a consequence of this "mislabeling" (and I can't recall what
ths anomoly was now).

So I just checked this out again with my Win 7 laptop: That laptop has
one hard drive, which is partitioned into C: for Windows and my
programs, and D: which stores the backup image files (and some other
stuff). When I boot up using the ATI flash drive ISO, it comes up using
C: for
itself, and showing D: for my C: hard drive, and E: for the partition
storing the image. However, as mentioned, it will restore the C:
partition mostly ok, but with at least one weird issue remaining (as a
consequence of the legacy of thinking it's restoring to D:, instead of
C My only possible clean "workaround" to "bypassing that anomaly" would
be
to restore a previous day's registry (if that were usable and
available), which would completely set the record straight as to it
being C:
Sorry to stick my thoughts in here but I think that the problem is using
Acronis or Macrium with an internal drive for their output. These
programs are meant to make a safety image or copy(clone) to another
place that is NOT part of the sources. That means another physical
location such as a second HDD, USB HDD or NAS. In fact an image stored
inside the machine used as a source is frequently worthless since it
will not be accessible for use under several failure situations.

--
Zaidy036

Yes, I'm aware it's only a half measure in the system backup department, but
I just use it for when I'm experimenting with some software programs, and
need to be able to get everything back to ship shape in case something went
awry.