O&O Software DiskImage 5 Professional Edition Uživatelská příručka stáhnout pdf (Strana 76)

Frequently asked questions

O&O DiskImage-70

An incremental image normally has a smaller data volume as a base image. In addition, you can ascertain the dif-

ferences, more precisely, the changes made since the base image was created.

My incremental image is not smaller than my base image. Where does this file come from?

This can occur if you have, for example, defragmented your computer in the meantime. The newly structured file

segments will then be recognized as “changes” and imaged as new files.

What does "Drive cannot be locked" mean? Does this affect the data imaging?

Because of the constantly running system processes, your system partitions cannot normally be locked. You get

this notification even when you want to image a data drive and this is directly integrated into the system processes.

The notification doesn’t generally have an effect on the imaging process; this is still able to be run without a prob-

lem. To be totally sure, shut down all running system applications, e.g. defragmentation or cloning processes,

before imaging.

While imaging, O&O DiskImage reports that the target volume is too small although the source drive is smaller

than the target disk. What is the reason for this?

Make sure you haven’t selected the entire hard disk as your source. Example:

You have a hard disk with 100GB that is divided into two partitions:

l System partition (20GB)

l Data partition (80GB)

l While trying to save the system partitions on an external 40GB hard disk, O&O DiskImage reports that the

target volume is too small.

By just making a check, you can select the system partitions as your only source, and not the entire hard disk.

What do I do if O&O DiskImage takes very long to start, or doesn't even start at all?

Please read the note about System requirements and make sure you're using the latest versions of your drivers.

During restoration, O&O DiskImage created a new temporary file on my hard disk. Where does this file come

from?

Before creating an image, O&O DiskImage normally deposits a number of metadata in a local file. This data is

needed by O&O DiskImage in order to create the image. The file will be included in the imaging to assure con-

sistency in the image. This file will normally be automatically removed during restoration.

Under certain circumstances, it's possible that another action of the operating system or the user will prevent this

temporary file from being deleted. This will then result in the file remaining undeleted in the system. You can, how-

ever, delete this temporary file without any risk.

Why are partitions that weren't imaged displayed when mounting an image in Explorer?

In addition to saving data from the partition being imaged, O&O DiskImage also needs to save information about

the disk on which that partition was originally located. All of this is required for mounting an image, converting it

into a virtual disk, or performing any future restoration. Of course, there will also be information included about par-

titions that were not imaged. When mounting an image, just as when using a virtual hard disk after conversion from

an image, Microsoft Windows uses this information to recognize that there were originally multiple partitions on the

disk, and attempts to integrate them into the system. Because information/data about these partitions is missing,

it's not possible to assign them to any file system. As a result, partitions that weren't imaged will be displayed as

RAW, i.e., non-formatted.

1 2 ... 71 72 73 74 75 76 77 78 79 80 81 ... 95 96

Žádné komentáře

O&O Software DiskImage 5 Professional Edition Uživatelská příručka Strana 76