Symantec 11859262 Datasheet Page 202

  • Download
  • Add to my manuals
  • Print
  • Page
    / 228
  • Table of contents
  • TROUBLESHOOTING
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 201
ACPI: Single processor
MPS: Multi processor
APIC: Single processor HAL that is used on older systems
If the recovery point is taken from a system with a single processor, you might
expect the recovery point to have an AACPI, ACPI, or APIC HAL. You can check
the HAL on the restored machine by copying the new HAL and then checking the
properties. If the new machine has multiple processors, you might expect the HAL
to be changed by Restore Anyware. You can replace the HAL by using a command
prompt.
In most cases, a multi processor will run even if a single processor HAL is used,
although it might not run at full capacity.
The HAL might not be replaced correctly if the CAB files are missing from the
original system.
To determine the version of the HAL.dll
1
Use the Recovery Point Browser to restore the system32\HAL.dll to a different
location.
2
Right-click the HAL.dll, and then click Properties.
3
Click Version, and then look for Internal Name.
This is the version of the HAL.dll.
The system blue screens during the boot up
The most probable cause for a blue screen error when you use Restore Anyware
is an incorrect or conflicting mass storage controller driver.
Restore Anyware has a special database that contains mass storage controller
drivers. You can verify whether a driver is present by checking the database
directory. It is located on the CD in the i386\shell\v2i\DDB directory.
If Restore Anyware detects a mass storage controller such as a SCSI controller on
the new system and it does not have the driver, it prompts you to add the other
driver. Do not ignore this prompt. If you do not add the driver, a blue screen occurs
later in the process. The only time when ignoring this prompt does not cause a
blue screen is if there are multiple mass storage controllers in the system. Also,
the driver it is prompting for is not the controller being used for the boot partition.
For example, if a system has a SCSI card that contains the boot volume (C:\) and
a Fiber card, the option can be skipped and the customer can load the Fiber drivers
once in Windows.
Troubleshooting Backup Exec System Recovery
Troubleshooting Restore Anyware
202
Page view 201
1 2 ... 197 198 199 200 201 202 203 204 205 206 207 ... 227 228

Comments to this Manuals

No comments