Robert in CA wrote:
I gave it a try
https://postimg.cc/8FbGsJbB
https://postimg.cc/gxFbDqSH
https://postimg.cc/34bPDg0p
https://postimg.cc/4nD0k46J
https://postimg.cc/zbLx643b
I still have half a dozen older 2019 Mrimgs that we could
try if you wanted to. I wish there was a way to tell if they
were good or not without going through the process.
I'm now also thinking how messed up the 8500 might be
but one thing at a time. It might be OK.
Robert
All looks normal there.
Nothing so far looks anomalous.
*******
When you're doing a backup, you go to that list
of backup definitions and select one.
It's a file by that name, which you'd need to search for
on C: that would be the XML file, and you need to look in
the file with Notepad or Wordpad. You saw my sample of
lines I copied out, which is the section of the file
that picks what to back up.
!-- The source of the backup --
source
!-- The following applies to Disk Images only --
image_entry id="1"
!-- disk is the 1 based index of the disk to be imaged --
!-- id is the disk signature and is used in place of the disk index if specified --
disk id="13796CED"1/disk
!-- partition is the 1 based index of the partition on the disk --
partition1/partition
/image_entry
image_entry id="2"
disk id="13796CED"1/disk
partition2/partition
/image_entry
image_entry id="3"
disk id="13796CED"1/disk
partition3/partition
/image_entry
image_entry id="4"
disk id="13796CED"1/disk
partition4/partition
/image_entry
The disk would not be selected, if the "disk id"
did not match. The "13796CED" number is stored in
the MBR sector, and it's an identifier that applies
to the whole disk.
I'm sure if you find that file, something is going to
stand out as a mistake :-)
Paul