Installing Drive Image

Drive Image System Requirements Installing Drive Image Testing the PQRE Activating Drive Image
Drive Image System Requirements
Operating system Processor RAM Windows 2000 Professional, Windows XP Home, Windows XP Professional Pentium 150 or faster 128 MB for Drive Image running from Windows 2000 or Windows XP 256 MB for PQRE, the recovery environment from the bootable CD Hard drive free space 45 MB for program files (and an additional 40 MB for the Microsoft.NET Framework if it is not already installed) Storage space for your backup images, unless you choose to store them to a network or on removable media CD or DVD drive Any speed
See supported drives. See I cant boot from the CD. on page 67.

Software

When you install Drive Image, you will be prompted to install the Microsoft.NET Framework, if it has not already been installed on the machine.
Drive Image 7.0 is compatible with dynamic disks. You can back up dynamic disks, and you can store backup images on dynamic disks.
Supported File Systems and Removable Media

File Systems

Drive Image is fully supported on FAT16, FAT16X, FAT32, FAT32X, NTFS, Linux Ext2, Linux Ext3, and Linux swap partitions. Drive Image supports the saving of backup image files locally (that is, backup image files are created and saved on the same machine where the console is installed) to most CD-R, CD-RW, DVD-R(W), DVD+RW, and DVD-RAM recorders on the market today. For an updated list of supported drivers, See supported recorders. It also supports saving backup image files to most USB devices, 1394 FireWire devices, JAZ, Zip, SuperDisk, and magneto-optical devices.

IMPORTANT! Drive

Removable Media
Image does not support RAM drives.
Windows 9x, Windows Me, and Windows NT Workstation 4.0
Drive Image 7.0 does not run under Windows 9x, Windows Me, or Windows NT Workstation 4.0. If you have one of these operating systems, you can use Drive Image 2002, which is included in the box with Drive Image 7.0. Drive Image 2002 requires a Pentium-compatible processor or higher, 32 MB RAM, 35 MB of hard drive space, a CD drive (any speed), and a high-density floppy disk drive. Drive Image 2002 can also run under Windows 2000 Professional with 64 MB RAM and Windows XP Professional or Home with 128 MB RAM.
Insert the Drive Image CD. If the CD browser screen does not appear automatically, browse the CD and double-click AUTORUN.EXE. The Drive Image CD will immediately scan the hard disk and prompt you to install the.NET Framework if it does not exist on the machine. Following the installation of the.NET Framework, you can continue with the installation of Drive Image. From the CD browser screen, click Install. At the welcome screen, click Next. Read the license agreement. Select I accept the terms in the license agreement, then click Next. (Optional) Click Change if you want to change the default location for the Drive Image program files. Click Next. Click Yes or No to specify whether you will use Drive Image with a network. If you have a network, type a user name, domain or computer name, and password that will give Drive Image read-write access to the network for saving and restoring backups. Then click Next. If you specified that you do not have a network, the Agent Setup screen will not display.

(Optional) Type a description that you want associated with the backup images created by this backup job. The backup image file size and creation date are automatically appended to the description, so you do not need to enter this information.
(Optional) Click Advanced for additional options. Advanced Option Ignore bad sectors during copy Description If you want the ability to create a backup even if there are bad sectors on the hard drive, select this option. Although most drives do not have bad sectors, the potential for problems increases during the lifetime of the hard drive. SmartSector technology speeds up the copying process by only copying clusters and sectors that contain data. However, in some cases, such as high-security environments, it may be desirable to copy all clusters and sectors in their original layout, whether or not they contain data. If you want to copy both used and unused clusters and sectors, select Disable SmartSector Copying. Deselecting this option increases processing time and usually results in a larger backup image file size. Use password If you select this option, you can specify a password for the backup image. Passwords can use standard characters, not extended characters or symbols. (Use characters with an ASCII value of 128 or lower.) A user must type this password before restoring a backup or opening it in the Backup Image Browser.
Click Next. click Finish.
Tips for Creating Backup Images
You may find it helpful to test a backups. If a backup is successful and the backup image is stored in the location you want, you can use the Create Backup Job feature to create subsequent backups at regular intervals.
To test a backup job, click the Backup Jobs tab in the advanced view, then select the backup job you just created. Click Tools > Run Job Now. As each new backup is created, information is added to each tab (Drive, Backup Jobs, Backup History, Events) in the advanced view. Click the Backup History or Backup Jobs tab to get a detailed look at when the last backup images occurred, where the backup images are stored, their compression level, and any description you may have entered. All backup jobs are saved, so you can edit or run them later. If an NTFS volume uses EFS (Encrypted File System), the security remains intact on the volume when you mount the volume using the Backup Image Browser tool. If, however, you are simply viewing folders and files inside the backup image file using the Backup Image Browser tool (that is, the.V2i or.PQI file is not mounted), there is no security on the volume, folders, or files. Do not run a disk defragmentation program while a backup image is being created. Doing so will cause unexpected results.

(Optional) Select Use password to assign a password to the backup image file. A user must type this password before restoring a backup or opening it in the Backup Image Browser. To remove a password for a backup image file, repeat steps 1 and 2 above, then deselect Use password.

Click OK.

Restoring Files and Folders
Methods for Restoring Files and Folders Restoring Files from a Backup Image Mounting a V2i Drive Dismounting a V2i Drive Restoring Files from a Backup Image Using the PQRE Viewing the Properties of a Backup Image (Backup Image Browser) Viewing Drive Properties of a Backup Image (Backup Image Browser) Viewing a File within a Backup Image (Backup Image Browser)
Methods for Restoring Files and Folders
There are two different methods you can use to restore files and folders on a machine. Each restore method, as described in the table below, takes into account the functionality that is or is not available on the machine. In many instances, you do not need to take the machine down to complete a restoration.

IMPORTANT! Before

you can restore a machine, you must have a backup image already created. You cannot restore data on a machine if a backup image of that machine does not exist. Restore method Restore selected files and folders from a backup image using Backup Image Browser within Windows. See Restoring Files from a Backup Image on page 36. Requires reboot? No. Restore selected files and folders from inside a backup image using Backup Image Browser from the PowerQuest Recovery Environment (PQRE) on the bootable V2i Protector CD. See Restoring Files from a Backup Image Using the PQRE on page 39. For tips and troubleshooting information when you are restoring from the PQRE, see Tips and Troubleshooting When Restoring from the PQRE on page 56. For information about the using the advanced support utilities under the PQRE, see Using the Support Utilities under PQRE on page 54.
Problem You can boot into the operating system on the machine but you have lost data, programs, or hardware files on a drive (excluding operating system files). You cannot boot into the operating system, and you have lost hardware, data, or program files on a drive.
Restoring Files from a Backup Image
If you are able to run the OS (operating system) on a troubled machine, you can use the Backup Image Browser to restore individual files or folders from a backup imageall with zero downtime to the machine. This method of recovery, sometimes known as a hot restore, is useful if you have traced the cause of a machine failure to a certain file or folder of files, or you have simply lost important data files and do not want to restore an entire backup image using the Restore Drive wizard.

From the tree pane of Backup Image Browser, double-click the backup image file (.V2i or.pqi) that contains the drive with the folders or files you want to restore.
To open the Backup Image Browser, see Opening the PowerQuest Backup Image Browser on page 11.
Double-click the desired drive. Select the files or folders you want to restore. Press <Ctrl+A> to select all items. To select a group of files that are next to each other, click the top file, then hold down <Shift> and click the last file in the list. To select a group of files that are not next to each other, hold down <Ctrl> while selecting the files you want.
Click File > Restore. Where possible, the Restore Items dialog will automatically fill in the Restore to this folder text field with the original path when the backup image was created. If the original location does not include a drive letter (because the drive was hidden when you created the backup image), you must enter a drive letter for the drive before you can restore any files or folders. If the original path is unknown, or you want to restore the selected files to a different location, click Browse to locate the destination.
Click Restore to begin restoring the files. When file restoration is complete, you are returned to the Backup Image Browser main window.
Modifying Files within a Backup
You can open files from within a backup image. However, you must restore a file from within a backup before making modifications to it, or your changes will be lost.

Mounting a V2i Drive

You can mount a drive within a backup image file (.V2i or.pqi) by assigning it a drive letter that is visible from Backup Image Browser and Windows Explorer. You can perform a variety of tasks on the drive such as run ScanDisk (or CHKDSK), perform a virus check, defragment files, copy folders or files to an alternate location, or simply view disk information about the drive such as used space and free space. You may also be able to run executable programs that exist within the mounted backup image. When a drive is mounted, you can set it up as a shared drive. Users on a network can connect to the shared drive and restore files and folders from within the backup image. You can mount one or more backup images at a time. The drives will remain mounted until you dismount them or restart the machine. Mounted drives do not take up extra hard disk space.
If an NTFS volume uses EFS (Encrypted File System), the security remains intact on the volume when it is mounted. It is not necessary to mount a drive to restore files or folders from within a backup image. Folders and files in a mounted drive are marked as read-only.

IMPORTANT! When

IMPORTANT! The

PQRE requires a minimum of 256 MB of RAM to run.
Insert the PowerQuest Drive Image CD into the media drive of the machine. Immediately reboot the machine. You may need to modify your system to make it bootable from the CD. See I cant boot from the CD. on page 67.
(Optional) If necessary, you can install special RAID or SCSI drivers for the machines hard disk subsystem by pressing <F6> when prompted during the boot into PQRE.
See I cant access the local drive where my backups are saved. on page 67.
Watch the computer screen. When the prompt Press any key to boot from CD appears, you have approximately five seconds to press a key to begin booting into the PQRE from the CD. (Optional) From the Time Zone drop-down list of the PQRE main window, select the time zone location you are in relative to the location of the backup image store. (Optional) Select the language in which you want the SystemRestore wizards and Backup Image Browser to display. Click Backup Image Browser.
From the Open dialog, open the backup image file (.V2i or.PQI) that contains the backup image folders or files you want to restore.
letters under the PQRE may not match those in the Windows environment.
From the tree view pane of Backup Image Browser, double-click the desired drive. You can also click File > Open to locate the backup image file you want. If you are unable to see or browse the network from the Open dialog, type the name of the server and share that holds your backup images, in the File name text box (syntax example: \\server_name\share_name), then press <Enter>. Select a backup image file, then click Open to add it to the tree view pane of the Backup Image Browser. Double-click the backup image filename to display the available drives. If you are still unable to see your network after typing the server name and share name, you may need to map a drive to see and browse the network. See Network Connectivity During a Restore from the PQRE on page 56 for more information.
From the content pane of the Backup Image Browser, select the files or folders you want to restore. Press <Ctrl+A> to select all items. To select a group of files that are next to each other, click the top file, then hold down <Shift> and click the last file in the list. To select a group of files that are not next to each other, hold down <Ctrl> while selecting the files.

Click File > Restore. If you selected an image file that was created with an older version of Drive Image or Backup Image Browser, a progress bar displays while the Backup Image Browser expands the image index.
Where possible, the Restore Items dialog will automatically fill in the restore location with the original path when the backup image was created. If the original location does not include a drive letter (because the drive was hidden when you created the backup image), you must enter a drive letter for the drive before you can restore any files or folders. If the original path is unknown, or you want to restore the selected files to a different location, click Browse to locate the destination.
Click Restore to restore the files. When file restoration is complete, click OK. Click Close to return to the Backup Image Browser main window.
Viewing the Properties of a Backup Image (Backup Image Browser)
From the tree pane of Backup Image Browser, select the desired backup image file (.V2i or.PQI). Click File > Properties, or right-click the backup image file and click Properties.
Image Property Description
Specifies A user-assigned comment associated with the backup image. The description is entered during the Backup Drive wizard, Create Backup Job wizard, or when you use the Export Backup Image feature in the Backup Image Browser. The total size (in megabytes) of the backup image. The date and time that the backup image file was created. The compression level used in the backup image. Whether the entire backup image file is spanned over several files. Identifies whether or not the selected drive is password protected. The password is entered in the Advance Options area of the Backup Drive wizard and the Create Backup Job wizard, or when you use the Export Backup Image feature in the Backup Image Browser. The version number of the backup image file.
Size Created Compression Spanned Password protected

Version

Viewing Drive Properties of a Backup Image (Backup Image Browser)

There are two different methods you can use to restore a machine to full functionality. Each restore method, as described in the table below, takes into account the functionality that is or is not available on the machine. In many instances, you do not need to restart the machine to complete a restoration.
you can restore a machine, you must have a backup image already created. You cannot restore the operating system or data on a machine if a backup image of that drive does not exist. Restore method Restore a backup image. See Restoring a Backup Image on page 44. Requires reboot? No.
Problem You can boot into the operating system on the machine but you need to restore a drive (other than the operating system partition) from a recent backup image. The machine has suffered a catastrophic failure, or the software cannot lock a drive (definition of drive lock) to perform a restoration directly under Windows, or you cannot boot into the operating system, and you have lost hardware, data, or program files on a drive.
Restore the entire drive using the System Restore Wizard from the PowerQuest Recovery Environment (PQRE) on the bootable PowerQuest CD. See one of the following tasks based on your scenario: Restoring a Single Drive Using the PQRE on page 47. Restoring Multiple Drives Using the PQRE on page 51. Restoring Multiple Drives Using a System Index File Under the PQRE on page 53. Requires reboot? Yes.

Restoring a Backup Image

If you are able to access the operating system on a troubled machine, you can use the Restore Drive wizard to restore an entire backup image of a data driveall with zero downtime. This method of recovery, known as a hot restore, is useful if you have experienced the complete loss of a data drive.
From the basic view, click Restore a Drive.
Click Next. Select the backup location you are restoring from, then specify the path to the backup image file. Restore from Local file Description To restore a backup image that is located on the connected machine, click Local file, then specify a drive and folder (example, E:\Data_Backups\) where the backup image is stored. To restore a backup image that is located on disc media, browse to the CD or DVD drive and folder where the backup image is located. Make sure the media is in the drive before clicking Browse. Network file To restore a backup image that is located on the network, click Network file, then specify a UNC (Universal Naming Convention) path (example, \\machine\share\file) on the network where the backup image is stored, or click Browse to navigate to the network folder where the backup image is stored.

From the PQRE main window, click Utilities. Click the support utility you want to run. Support Utility Option Map Network Drive Configure IP Address PARTINNT.EXE Description See Network Connectivity During a Restore from the PQRE on page 56. See Getting a Static IP Address When Running the PQRE on page 57. Use PartitionInfo to create a report of the contents of your hard drive partition table. This report can help you diagnose and fix various disk partition problems. You can save the information to a text file, which can then be sent to technical support, if necessary.
Support Utility Option PQBOOT32.EXE
Description Use PQBoot to easily and quickly switch between bootable primary partitions. PQBoot is for users who only occasionally need to change the active partition.
Type the ID number of the partition (shown in the first column) you want to make the bootable primary partition, then press <Enter>. PQBoot makes the partition active and reboots the computer.

PTEDIT32.EXE

Use the PTEdit (Partition Table Editor) to read and allow manipulation of the partition table information found in the Master Boot Record and EPBR Boot record. PTEdit is useful for fixing partition table errors or boot sector problems. You can make changes to partition tables by using decimal values rather than hex values. You can also change the file system flag, set the active partition, hide and unhide partitions, and change CHS values, boot sector information, and the number of sectors in a partition. When you change the number of sectors, the final result must match the CHS values. PTEdit looks at partition table information in a relative fashion. Basically it finds the start sector of a primary partition by calculating the absolute value of the sector from the start of the drive to the boot sector of the partition.

RESTOREMBR.EXE

Use to save or restore critical MRB (Master Boot Record) information in the first sector of a hard drive. The contents of the first sector or entire first head of the hard drive are saved or restored to a file. Use to view, among other things, information about the hard drive on the machine. You can save the information to a text file (SMEDUMP.TXT) which can then be sent to technical support, if necessary.

SMEDUMP.EXE

Support Utility Option IPCONFIG.EXE
Description Use IP Configuration to view, among other things, network adapter information. You can also release or renew IP addresses from this utility. You can save the information to a text file (IPCONFIG.TXT) which can then be sent to technical support, if necessary.

PING.EXE

Use Ping to see if a machine you want to back up is operating and to see if the network connections to that machine are intact and functioning.
Type the IP address of the machine you want to check, then click OK.
Tips and Troubleshooting When Restoring from the PQRE

Error Messages

Backup Image Browser
Cannot initialize COM library.
The product was unable to initialize the COM subsystem. This can be caused by insufficient resources or corrupt DLLs. Reboot the system, and try to free system resources.
Cannot allocate V2i Protector mount manager instance.
The product was unable to allocate resources for the PowerQuest mount manager. This error is usually reported when the product is partially installed or some of the products COM objects are missing or incorrectly registered. To correct this condition, reinstall the product.
Cannot retrieve drive information.
The PowerQuest mount manager did not recognize the drive as a mounted backup image. This error is most commonly reported when another process is attempting to dismount the drive. The error may also occur if the drive is corrupt. Close all PowerQuest products, and retry the dismount operation. If the problem persists, reboot the computer to allow Windows to re-enumerate all mounted drives.
Cannot dismount drive. Please verify the drive is not locked by another process.
The PowerQuest mount manager was unable to dismount the drive. To resolve the error, make sure there are no open files on the drive and that the drive is not locked (definition of drive lock) by another application.

General Error Messages

Error EC8A0001:The engine has not been initialized
This error is caused by updated firmware on QLogic drives conflicting with the QLogic driver on the PowerQuest CD. In other cases it could also be caused by any SCSI conflict with particular drivers on the PowerQuest CD. Try loading the driver manually. See I cant access the local drive where my backups are saved. on page 67 for instructions on how to do this. If the error continues contact technical support with an SMEdump file, partinfo file, and system information file (if available). Additional log files may also be needed.

Error E0BC000A

The saved initial state for applying changes does not match the current system state.
Error E0B000C:Object BasicDisk SME~Computer~BgM896453 was in the saved state but is not in the current state. Error E0BC000C:Object MediaCommon:Sme~computer ~Pd1~M896453 was in the saved state but is not in the state.
The preceding two error messages could be caused by changes to the serial number. It could also be caused by the drive information reporting differently. If the restore was initially set up in Windows, but the entire system was rebooted with the PowerQuest CD, try going through the System Restore wizard on the PowerQuest CD rather than going through the restore from the console in Windows. There could be a change in the drive information in Windows 2000 versus the PQRE. If the error continues to occur during the use of the System Restore wizard from the PQRE, you should contact technical support.

E0710007 can not create a virtual volume image
Contact technical support with an SMEdump file, partinfo file, and system information file. Additional log files may also be needed.
WinBOM error when booting from PQRE
This is an issue with the NIC (Network Interface Card) driver not loading. If the backup image you want to restore is located on the network, then you will need to send the drivers and a system information file to technical support. PowerQuest will load the drivers for the customer.
The month and year are flopped on some international machines
This is an issue with some international servers. Send the.PQH files to technical support.
Getting Help for Volumes on Windows
For more information about basic and dynamic volumes, see the Microsoft Disk Management Help file (DISKMGMT.CHM). The default location for this Microsoft help file is \WINNT\HELP (under Windows 2000 Advanced, 2000, NT 4, or 2003 Server), or \WINDOWS\HELP (under Windows 2000 Professional or Windows XP Professional).
V2i Protector Agent and Windows Services Tool
The V2i Protector Agent runs as a service rather than as a desktop application. Running the Agent as a service allows scheduled backup jobs to run even if no one (or an unprivileged user) is logged on to the machine. The fact that the software runs as a service is also important when machines are being managed from a remote location; remote management is a feature of some PowerQuest products that use the V2i Technology. For example, V2i Protector Server Edition lets administrators back up servers throughout an enterprise from its centralized console. That would not be possible if the V2i Protector Agent ran as a simple desktop application. This flexibility lends power to V2i Technology. Because the Agent runs as a service, you can use the Services tool in Windows if you ever need to start, stop, configure the password, or troubleshoot the Agent. Checking the Agent in Services can be an invaluable tool to solving a problem with the software. If the Agent is not starting on a machine, you will have problems creating and restoring backups. Using the Services tool, you can manage the Agent in the following ways: Start, stop, or disable the Agent on local and remote computers. See Starting, Stopping, or Restarting the Agent Service on page 73. Configure the username and password used by the Agent. See Selecting an Account Under Which the Agent Will Run on page 72. (To give additional users access rights to the Agent, see Giving Additional Users the Ability to Back Up Machines on page 21.) Set up recovery actions to take place if the Agent fails to start. For example, you can restart the Agent automatically or restart the computer (on computers running Windows XP or Windows 2000 only). See Setting Up Recovery Actions When the Agent Fails to Start on page 74.

Opening Services

NIC Drivers Supported by the PQRE
1394 Net Adapter 3Com 10/100 LAN PCCard-Fast Ethernet 3Com 10/100 Mini PCI Ethernet Adapter 3Com 10/100 PCI NIC w/3XP (3CR990B-TX-M)
3Com 10/100 PCI NIC w/3XP (3CR990B-TX-M) 3Com 10/100 PCI NIC w/3XP (3CR990-TX-95) 3Com 10/100 PCI NIC w/3XP (3CR990-TX-97) 3Com 10/100 PCI Server NIC w/3XP (3C990BSVR) 3Com 10/100 PCI Server NIC w/3XP (3CR990B-TX-M) 3Com 10/100 PCI Server NIC w/3XP (3CR990SVR95) 3Com 10/100 PCI Server NIC w/3XP (3CR990SVR97) 3Com 3C450 Fast Ethernet Adapter 3Com 3C575TX-Based CardBus Fast Ethernet Adapter (Generic) 3Com 3C900B-COMBO Ethernet Adapter 3Com 3C900B-FL Ethernet Adapter 3Com 3C900B-TPC Ethernet Adapter 3Com 3C900B-TPO Ethernet Adapter 3Com 3C900COMBO-based Ethernet Adapter 3Com 3C900TPO-based Ethernet Adapter 3Com 3C905B-COMBO Fast Ethernet Adapter 3Com 3C905B-FX Fast Ethernet Adapter 3Com 3C905T4-based Ethernet Adapter 3Com 3C905TX-based Ethernet Adapter 3Com 3C918 Integrated Fast Ethernet Controller (3C905B-TX Compatible) 3Com 3C920 Integrated Fast Ethernet Controller (3C905C-TX Compatible) 3Com 3C985 Gigabit Ethernet Adapter 3Com 3CRWE62092A Wireless LAN PC Card 3Com 3CRWE737A AirConnect Wireless LAN PC Card 3Com 3CRWE777A AirConnect Wireless LAN PCI Card 3Com 3CSOHO Fast Ethernet Adapter 3Com 656C-Based PCCard Fast Ethernet Adapter 3Com EtherLink 10/100 PCI 3Com EtherLink III ISAPNP Ethernet Adapter (Generic 3C509b) 3Com EtherLink III LAN PC Card (3C589) (Ethernet) 3Com EtherLink III LAN PC Card (3C589B/3C589C) (Ethernet) 3Com EtherLink III LAN PC Card (3C589D) (Ethernet) 3Com EtherLink Server 10/100 Dual Port A 3Com EtherLink Server 10/100 Dual Port B 3Com EtherLink Server 10/100 PCI (3C980B-TX) 3Com EtherLink Server 10/100 PCI (3C980C-TXM) 3Com EtherLink XL 10/100 PCI For Complete PC Management NIC (3C905C-TX) 3Com EtherLink XL 10/100 PCI TX NIC (3C905B-TX) 3Com Fast Etherlink III ISAPNP Ethernet Adapter (Generic 3C515Tx) 3Com Fast Etherlink ISA 10/100BASE-T4 Network Card 3Com 3C574 TX Fast EtherLink PC Card 3Com Fast Etherlink ISA 10/100BASE-TX Network Card (3C515-TX) 3Com Fast EtherLink XL PC Card (3C575-TX) 3Com FEM656-Based CardBus Fast Ethernet Adapter (Generic) 3Com FEM656B-Based CardBus Fast Ethernet Adapter (Generic) 3Com Megahertz (B) 10-100 LAN + 56K Modem (Ethernet) 3Com Megahertz (BI) 10-100 LAN + 56K Modem (Ethernet) 3Com Megahertz 10/100 LAN CardBus PC Card 3Com Megahertz 10-100 LAN + 56K Modem (Ethernet) 3Com Megahertz LAN + 56K Modem PC Card (B) (Ethernet Interface) 3Com Megahertz LAN + 56K Modem PC Card (BI) (Ethernet Interface) 3Com Megahertz LAN + 56K Modem PC Card (Ethernet Interface) 3Com Megahertz LAN PC Card (589E) (Ethernet) 3Com OfficeConnect 3CXSH572BT 82557-based Integrated Ethernet with Wake on LAN

SysKonnect FDDI PCI Adapter SK-5541 (SK-NET FDDI-FP) SysKonnect FDDI PCI Adapter SK-5543 (SK-NET FDDI-LP) SysKonnect FDDI PCI Adapter SK-5544 (SK-NET FDDI-LP DAS) SysKonnect FDDI PCI Adapter SK-5821 (SK-NET FDDI-UP64) SysKonnect FDDI PCI Adapter SK-5822 (SK-NET FDDI-UP64 DAS) SysKonnect FDDI PCI Adapter SK-5841 (SK-NET FDDI-FP64) SysKonnect FDDI PCI Adapter SK-5843 (SK-NET FDDI-LP64) SysKonnect FDDI PCI Adapter SK-5844 (SK-NET FDDI-LP64 DAS) SysKonnect SK-9841 Gigabit Ethernet Server Adapter (SK-NET GE-LX) SysKonnect SK-9842 Gigabit Ethernet Server Adapter (SK-NET GE-LX dual link) SysKonnect SK-9843 Gigabit Ethernet Server Adapter (SK-NET GE-SX) SysKonnect SK-9844 Gigabit Ethernet Server Adapter (SK-NET GE-SX dual link) SysKonnect SK-984x-Based Gigabit Ethernet Adapter (Generic) TDK LAK-CB100BX for CardBus TDK LAK-CB100BX for CardBus Driver TDK LAK-CD031 for PCMCIA TDK Netflyer Cardbus Fast Ethernet Adapter Tiger Jet PCI 128K ISDN Adapter Tiger Jet PCI 128K ISDN-S/T (A) with POT Adapter Tiger Jet PCI 128K ISDN-S/T Adapter Tiger Jet PCI 128K ISDN-S/T Adapter Tiger Jet PCI 128K ISDN-U (K) Adapter Tiger Jet PCI 128K ISDN-U (K) with POT Adapter Tiger Jet PCI 128K ISDN-U Adapter Tiger Jet PCI 128K ISDN-U with POT Adapter Toshiba ATM Meteor 155 PCI Adapter Toshiba Fast Ethernet Cardbus LAN Card Toshiba Fast Ethernet PCI LAN Card (21142-PA) Toshiba IPC5008A 10/100 Ethernet PC Card Toshiba Modem+Ethernet PC Card Toshiba Wireless LAN Card Toshiba Wireless LAN Mini PCI Card USB HPNA 10 Mbps Network Adapter Driver VIA Compatable Fast Ethernet Adapter VIA PCI 10/100Mb Fast Ethernet Adapter VIA PCI 10/100Mb Fast Ethernet Adapter VIA PCI 10/100Mb Fast Ethernet Adapter VIA VT86C100A Fast Ethernet Adapter VIA VT86C100A-Based Fast Ethernet Adapter WebDav Client Redirector Winbond PCI Fast Ethernet Adapter (Generic W89C840) Winbond W89C840 PCI Fast Ethernet Adapter Winbond W89C926 Based PCMCIA Ethernet Adapter Winbond W89C940-Based Ethernet Adapter (Generic) Xircom CardBus Ethernet 10/100 Adapter Xircom CEII Performance Series PCMCIA Ethernet Adapter Xircom CreditCard Ethernet+Modem 28.8 (Ethernet) Xircom CreditCard Ethernet+Modem 33.6 (Ethernet) Xircom CreditCard ISDN Adapter Xircom Ethernet + Modem 56 Xircom Ethernet Adapter 10/100 Xircom RealPort2 Ethernet 10/100 Adapter
PowerQuest Technical Support
Technical Support Options Complimentary Technical Support Fee-Based Support

English

French

France

German

Germany

Fee-Based After-Hours Support
PowerQuest offers fee-based after-hours support by telephone only. After-hours support is designed for anyone who requires support outside of regular business hours (8:00 a.m. to 5:00 p.m. MST, Monday through Friday). The price is $95.00 USD per incident.

Glossary

Active Directory
The directory service that stores information about objects on a network and makes this information available to users and network administrators. Active Directory gives network users access to permitted resources anywhere on the network using a single logon process. It provides network administrators with an intuitive, hierarchical view of the network and a single point of adminitration for all network objects.

backup image

An exact copy of a drive (either containing data or the operating system) that is usually compressed and stored as a file. A backup image file has a.V2i (Virtual Volume Image) file extension. Backup images are what you use to restore files and folders or an entire drive. A backup image is also sometimes known as an image, or backup. You can view the contents of a backup image file using Backup Image Browser.

bare metal recovery

The complete recovery of a computer after a catastrophic hard disk failure. It includes the restoration of the operating system, file system, partitions, volumes, and data, from a complete backup image (such as a.V2i file made with V2i Protector or Drive Image).

cluster

The smallest allocation unit in the FAT, FAT32, and NTFS file systems. One cluster consists of a fixed number of disk sectors.

delayed apply

Restoring an operating system partition using the Restore Drive wizard from the V2i Protector management console or from Drive Image (as opposed to using the RecoveryWizard from the PQRE).

drive lock

A request by V2i Protector or Drive Image for exclusive use of a selected drive before making any modifications to the file system of the hard drive. By locking down a drive, you prevent other software programs from changing the file system while V2i Protector is trying to change it. This ensures that any data on the drive is current and accurate at the time of restoration.

extended partition

A special kind of primary partition that was developed to overcome the four- partition limit. The extended partition is a container inside of which you can create logical partitions. The extended partition itself does not hold any data, nor is it assigned a drive letter. But logical partitions inside the extended partition can hold applications and data and are assigned drive letters.

Troubleshooting

This document provides solutions to problems that you may encounter while using Drive Image. Included are the following:
Freeing Conventional Memory to Run Drive Image Resolving Check Errors Resolving Partition Table Errors Partition Tables and Viruses Error Messages and Solutions
Freeing Conventional Memory to Run Drive Image
The Drive Image executable running under DOS requires a minimum of 400KB of memory in the first 640KB of the computer's address space (conventional memory). If you try to run Drive Image from DOS and find you do not have enough free conventional memory, you can free enough additional memory in a number of ways.

Running MEMMAKER

MEMMAKER is a program that automatically configures your computer to save conventional memory (while still loading all of the device drivers and other programs you usually load when booting DOS). MEMMAKER frees conventional memory by moving as many programs as possible out of conventional memory into high memory. Run MEMMAKER by typing MEMMAKER at a DOS prompt. Follow the on-screen instructions. MEMMAKER is only available with DOS versions prior to DOS 6.0. {MEMMAKER is not available with Windows 95.
Using the F8 Key to Keep Programs From Loading
If running MEMMAKER does not free enough conventional memory, you can free more by pressing <F8> right after booting your computer (while DOS is booting). If you press <F8>, when DOS reads the commands from the CONFIG.SYS and AUTOEXEC.BAT files on your hard drive, DOS will ask you if you want it to execute each command. When you see commands that load device drivers or TSR programs that you will not need to run Drive Image, answer N (no) to tell DOS not to execute that command (not load that software into memory). This will conserve conventional memory.
Using an Operating System Boot Diskette
If running MEMMAKER and using <F8> does not free enough conventional memory, you can create a boot diskette that allows you to boot using a very minimal amount of conventional memory. You can create a boot diskette for any version of DOS by performing the following:
1 Place in your diskette drive (A:) any diskette that does not contain information you

want to keep.

2 Go to a DOS prompt, type FORMAT drive: /S (where drive is the drive letter of the

diskette drive).

3 Press <Enter>.
After the diskette is formatted and the operating system files are transferred, you will be able to boot the computer from the diskette. If you restart your computer with the diskette in the diskette drive, your computer boots using a minimal amount of conventional memory. After you boot from the diskette, you can run Drive Image from either the diskette or your hard drive. If you want to run create and restore images across a network, you will need to create a network boot diskette. See Creating DOS Boot Disks in Appendix A.
Creating a CONFIG.SYS File on the Boot Diskette
If making an ordinary boot diskette doesn't free enough conventional memory, you can create a customized boot diskette that will free even more conventional memory. (With the customized diskette, you will free more conventional memory by loading some of the DOS operating system into high memory.) To customize the diskette, you must create a CONFIG.SYS file in the root directory (C:\). To create a CONFIG.SYS in the root directory, perform the following:
1 At the DOS prompt, type drive: (where drive is the drive letter of the diskette drive),
then press <Enter>. Verify that you have changed to the diskette drive (you see the drive:\> prompt).
2 Type EDIT CONFIG.SYS, then press <Enter>.
This starts the DOS editor. (You will see a blank screen if no CONFIG.SYS currently exists.)
3 In the editor, type the following:
DEVICE=C:\DOS\HIMEM.SYS DEVICE=EMM386.EXE DOS=HIGH,UMB

IMPORTANT!

All lines must be entered in the order shown. Windows users, substitute DEVICE=C:\WINDOWS\HIMEM.SYS.
4 Click File Save to save the file. 5 Click File Exit to exit the editor.
You can now reboot your computer from the customized boot diskette. When DOS loads, much of it is loaded into high memory, saving a maximum amount of conventional memory.

PowerQuest Drive Image

Deleting Operating System Compression Files
If you use DOS 6.22 and your system doesn't have any compressed drives (for example, DriveSpace, DoubleSpace, or Stacker), you can delete the operating system compression files DRVSPACE.BIN or DBLSPACE.BIN from any boot diskette you create. This frees more conventional memory because DOS 6.22 loads the contents of these files into memory, regardless of what's in the CONFIG.SYS or AUTOEXEC.BAT. These files are hidden system files, so if you wish to delete them you will have to perform the following:

1 From the DOS prompt, type drive: (where drive is the drive letter of the diskette

drive).

2 Type ATTRIB -R -H -S *.BIN. 3 Type DEL *.BIN.

Resolving Check Errors

Drive Image checks the integrity of a partition thoroughly prior to creating an image file or copying a partition. These checks are substantially the same as those made by the operating system's CHKDSK, SCANDISK, or AUTOCHK utility.
1 If you receive a Check error message for any partition, after backing up your hard
drive, do the following: Operating System Windows 95, Windows 98, or MS-DOS 6.x Windows NT Instructions Run SCANDISK on the affected partition.
Run CHKDSK without the /F switch on the affected partition. Note that the DOS CHKDSK does not detect problems with Extended Attributes.
2 The check utility program usually shows the same problems as Drive Image. If that is
the case, run the utility again with the /F switch to fix the problem. If the check utility does not show the same errors that Drive Image shows, contact PowerQuest technical support. See Appendix D of the Drive Image user guide for contact information.
3 After running the utility with the /F switch, run it again without using the /F switch to
make sure the partition is free of errors. Under OS/2, you should perform this procedure twice before proceeding.
4 If Drive Image still reports a problem, reformat the partition and restore your files
from the backup copy to correct the error.
Check Errors Encountered After Restoring an Image
Drive Image also checks a partition after restoring it. If this check fails, report the problem to PowerQuest technical support. While data loss is possible, in this case it is not typical. The problem is usually a minor file system error that CHKDSK /F can correct without data loss. For more extensive errors, you may need to restore your files from a backup copy.
Resolving Partition Table Errors
To resolve partition table errors, you must create new, error-free partition tables. In some cases, PowerQuest technical support can help you fix partition table errors without data loss. Check with them first before proceeding with the following steps.

Creating New Partition Tables
1 Make sure you have no viruses.
See Partition Tables and Viruses on page 6.
2 Back up the data on the affected partitions. 3 Delete the partitions.
You may need to use the FDISK program from a recent DOS version because earlier versions of DOS may refuse to delete HPFS or hidden partitions. Under OS/2, the OS/2 FDISK program may recognize the partition's corruption and refuse to modify it. In this case, use the FDISK program from a recent DOS version.
4 Recreate the partitions. 5 Restore the contents of the partitions.
Partition Tables and Viruses
If partition changes made under one operating system are not reflected under the other, and vice versa, it is possible that a master boot record (MBR) virus is present. Use a virus check utility that can detect the latest viruses. If a virus is found, data loss is likely. If a virus is found, perform the following:
1 Before removing the virus, run ScanDisk, CHKDSK, or ffck under each of the
operating systems to evaluate the integrity of the partition.
2 Back up the files from any partition that passes the Check operation. 3 After backing up the files from all operating systems, remove the virus. 4 Run a thorough ScanDisk, CHKDSK, or ffck under each of the operating systems

again.

5 Delete and recreate any partitions that fail the check. 6 Reinstall the operating systems. 7 Restore the backup files as necessary.
Error Messages and Solutions
For a complete list of error messages and solutions, please visit the PowerQuest Knowledge Base at www.powerquest.com/support/primeun/id817.html.
Miscellaneous Errors (338)

#3 Not enough memory

The DOS Drive Image executable running under DOS requires a minimum of 400KB of memory in the first 640KB of the computer's address space (conventional memory) and 8MB of total memory. If you don't have enough conventional memory, see Freeing Conventional Memory to Run Drive Image on page 2 for possible solutions. The boot diskette (disk 1 of 2 Drive Image rescue disks) includes EMM386.EXE to help load network drivers in high memory. However, because this file limits extended memory to 32 MB, you may see error #3 when you run Drive Image from the rescue disks and work with large FAT32 and NTFS partitions. If you do not need EMM386.EXE, you can delete it from the bootable floppy to avoid this
error. If you delete the EMM386.EXE file, you must also REM or delete the following line in the CONFIG.SYS file on the boot floppy: DEVICE=EMM386.EXE.
#8 Could not allocate/deallocate DOS real mode memory
The DOS Drive Image executable running under DOS requires some memory in the first 1 MB of the computer's address space. (Drive Image uses a DOS extender.) If not enough memory is available, Drive Image cannot access the hard drive. If you don't have enough conventional memory, see Freeing Conventional Memory to Run Drive Image on pag e2 for possible solutions.

#23 Unsupported version of operating system
The operating system versions that are required to run Drive Image are listed in System Requirements in the Introduction page XX).
#34 This beta or evaluation version is no longer safe to use
PowerQuest occasionally releases beta versions and evaluation versions of Drive Image. Both versions are not as safe as released versions; therefore, PowerQuest builds an expiration date into each version. After a predetermined test period, the beta or evaluation version will no longer function.

#36 DPMI Server error

Drive Image DOS executables use a DOS extender. This error indicates a failure during a call made from Drive Image through the DOS extender (to DOS or to the BIOS). The DOS extender may be in conflict with other programs that use extended memory. DOS would load the conflicting programs from your CONFIG.SYS or AUTOEXEC.BAT file during the normal boot sequence. You may be able to resolve this problem by pressing <F8> while booting DOS. After DOS boots and starts to read the commands from your CONFIG.SYS and AUTOEXEC.BAT files, DOS will ask if you want to execute each command. When you see commands that load device drivers or TSR programs that you think might be conflicting with the Drive Image DOS extender, answer N (no) to tell DOS not to execute that command (not to load that software into memory). You will often be able to find a program configuration that will enable Drive Image (the DOS extender) to run without error.
Disk Access Errors (4056)
Errors 40-56 indicate that Drive Image cannot access your hard disk; these errors are often reflect hardware problems. Some problems have simple solutions; for other problems, the only solution is to replace the hard drive. When possible, Drive Image detects errors before any changes have been made, so you can back up your data before replacing the hard drive.
#49 #50 Write fault Read fault
Drive Image is unable to read or write from a specific sector on the hard drive. There are a number of possible causes of this error: If your PC beeps or displays a black box in the middle of the screen, virus protection is enabled in your computer's BIOS. Disable virus or boot sector protection in the BIOS. A virus protection application (which may be a TSR or DLL program) is in use. Disable the application before using Drive Image. There is a bad sector on the hard drive. (This is usually the case with only older hard drives.) Run a thorough SCANDISK on the hard drive to perform a surface scan to verify the existence of bad sectors. If your drive has bad sectors, we recommend you replace it. You may be able to use Drive Image, or you may need to back up your files using another method. You have set up disk mirroring with PC-Tools. Disable disk mirroring. Your caching controller card is not set up properly.

Partition Table Errors (100199)
Errors in the 100-199 number range are partition table errors. For general information about solving this type of error, see Resolving Partition Table Errors on pag e5.
#100 Partition table is bad
The master boot record (MBR) can contain, at most, one extended partition, and each extended partition boot record (EPBR) can contain, at most, one link to another EPBR. This error occurs when a partition table violates the foregoing rule. Since any modifications Drive Image makes may decrease the amount of data that is recoverable from the hard drive, Drive Image will not recognize any of the hard drive's partitions. You must create new, error-free partition tables to resolve your problem. See Partition Tables and Viruses on page 6.

No sectors in partition

No partition should contain zero sectors. Delete the partition before using Drive Image.
#105 Partition starts on wrong boundary
The hard-disk partition table contains erroneous values. Drive Image expects FAT, NTFS, and HPFS partitions to begin and end on the boundaries used by FDISK. If they do not, the disk may be partially corrupted. In this circumstance, if Drive Image were to make any modifications it might cause the loss of data. Therefore, Drive Image will refuse to recognize any of the hard drive's partitions. To resolve this problem, see Resolving Partition Table Errors on page 5.
#106 Partition doesn't start with sector one

See error #105.

#107 Partition begins after end of disk
This error can occur when you are running Drive Image on a hard drive that uses more than 1,024 cylinders. Under DOS, Drive Image is restricted by the BIOS 1,024 cylinder limit. If any partitions extend beyond the limit, Drive Image cannot safely operate on the hard drive. This error can also occur if a partition erroneously extends beyond the physical end of the hard drive. This may happen if the hard drive has been used on a different computer or with a different hard-disk controller or if BIOS settings have been changed. Be advised that the physical geometry of the hard drive may differ from the logical geometry assigned to the hard drive by the operating system.
#108 Partition doesn't end at end of cylinder
#109 Partition ends after end of disk

See error #107.

#110 Partition table number of sectors is inconsistent
The hard-disk partition table contains two inconsistent descriptions of the number of sectors on the hard drive. This error is serious if both DOS and another operating system use the hard drive. Because DOS uses one description and other operating systems may use the other, data loss is likely once the partition is almost full. To resolve this error, see Resolving Partition Table Errors on page 5.

Logical partition starts outside Extended
The hard-disk partition table contains erroneous values. All logical partitions must be totally contained within the extended partition. To resolve this error, see Resolving Partition Table Errors on page 5.
#112 Logical partition ends outside Extended

See error #111.

#113 Partitions overlap
The hard-disk partition table contains erroneous values. If data partitions overlap, writing to one may destroy data in another. This error is sometimes the result of an OS/2 FDISK bug. If free space exists within the extended partition, OS/2's FDISK program allows a primary partition to be created that overlaps the extended partition. A logical partition is subsequently created in the space occupied by the overlapping primary partition. If a primary partition overlaps the end of the extended partition, but does not overlap any logical partitions within the extended partition, the problem can be remedied by patching the partition table. Only qualified individuals should attempt this repair! An incorrect patch could destroy all data on the hard drive! In most instances, you should resolve the problem as explained in Resolving Partition Table Errors on page 5.
#116 Partition table Begin and Start inconsistent
The hard-disk partition table contains two inconsistent descriptions of the partition's starting sector. This error can occur if the operating system reports a hard-disk geometry that is different than the geometry in use when the partition table was written. Possible causes of the hard-disk geometry changing are: Different operating systems (for example, DOS and OS/2) report different hard-disk geometries. You boot from a diskette that loads a different driver than is loaded when you boot from the hard drive. Upgrading the operating system (for example, from OS/2 2.x to OS/2 Warp) causes a different driver to be used. The hard drive or controller has been changed. The BIOS has been upgraded. The BIOS LBA setting has been changed. There is a partition table virus present on the hard drive.
In most instances, you should resolve the problem as explained in Resolving Partition Table Errors on page 5. You can also use a virus scanning program to remove any partition table virus. Data loss is possible if the number of heads or sectors per track has changed since you first created your partitions.
#120 The logical drive chain is incompatible
This error occurs under some OSs when logical partitions are not chained together in the expected order. DOS, OS/2, Windows 95, and Windows NT require that logical partitions be chained together in ascending order. Some other operating systems do not require this. For example, some versions of the Linux FDISK utility chain logical partitions together in the order they are created.

WARNING!

This error message identifies a dangerous situation; using the DOS FDISK in this situation can cause loss of one or more partitions.
For solutions to this problem, see the instructions in Resolving Partition Table Errors on page 5. If you decide to back up your data and recreate your partitions, you may have to use the same partitioning program that you used to create the partitions to delete them.
#121 The first sector of the drive cannot be read
The first sector of the hard drive (cylinder 0, head 0, sector 1) contains the master boot record (MBR) and the primary partition table. Drive Image cannot make changes to this hard drive because an error occurred when it read the first sector. See error #50 for information on resolving this error.
#122 A bad sector was found in the current or new partition area
The partition cannot be moved safely because there is a bad sector in the new or current partition area. When you see this error message, the move operation will be aborted before any corruption can occur. Try moving the partition to a different place. If your hard drive has bad sectors, we recommend that you replace the hard drive.

Check Errors (500599)

Check errors occur when Drive Image checks the integrity of a partition. For useful general information about resolving these errors, see Resolving Check Errors on page 4.
Subdirectory is corrupted
This error message reveals the name of the corrupted subdirectory. Back up the contents of that directory and its subdirectories. You can then delete the corrupted subdirectory.
#501 Cross-linked files were found
ScanDisk or CHKDSK should be able to find these errors and correct them.
#506 Not enough free space on partition to shrink
Some free space (which is dependent on the hard drive's current contents) is required to resize a partition smaller. Delete unneeded and duplicate files in the partition, then attempt the operation again.
#508 As specified, the operation does not change the partition
You have entered a value that is the same as or (when rounded to the required cylinder boundary) rounds to the same as the partition's present value. Enter a larger change.
#509 A bad sector was detected in the current or new FS area
In order to perform the resize operation that you requested, Drive Image attempted to expand the file system area. However, the program found a bad sector in the new area. Try moving the partition before you resize it. No corruption will occur when you encounter this error.

#510 The version of the file system is not supported
An updated version of Drive Image is required to operate on this new version of the file system. Visit www.powerquest.com/updates for information about updated versions of Drive Image.
HPFS Check Errors (10001500)
#1015 System sector not marked unavailable
This error may indicate that there are open files on the hard drive. Shut down and restart OS/2, booting from diskettes. If this does not resolve the problem, run OS/2's CHKDSK program. This error message may also indicate that a file is listed with a file length of zero. OS/2's CHKDSK program will not fix this problem. As a last resort, delete the offending file.
#1027 Could not account for all sectors
This error may be resolved in one or more of the following ways: If you are working with an HPFS386 partition, check the technical support area of PowerQuest's web site (www.powerquest.com) for more information. If CHKDSK has created any FOUND.000 or *.CHK files, delete them. If the error message indicates the name of the offending file, delete it. Turn off the disk-mirroring option in PC-Tools. If none of the above solutions works, back up the partition, delete it, recreate it, and restore the data.
#1045 Stac volume detected deleteStac volume before converting
This error message occurs when you attempt to convert a partition to HPFS, and the existing partition contains a STAC volume. Stacker cannot access a STAC volume that is on an HPFS partition. Delete the STAC volume from the partition before converting to HPFS.
NTFS Check Errors (15001699)
Errors 1500-1699 are NTFS-specific error messages. In this context, attribute does not mean read-only, hidden, system, and so on. Rather, attribute means one of a files data streams. Check errors occur when Drive Image checks the integrity of a partition. For useful general information about resolving these errors, see Resolving Check Errors on page 4.
#1501 Wrong version of NTFS
The partition was created using a version of the NTFS file format that Drive Image cannot work with.

#1503 Bad NTFS cluster size
The NTFS cluster size must be 512, 1,024, 2,048, or 4,096 bytes.
#1512 Restart record mismatch
The two restart entries in the journal file are different. This may happen if Windows NT is not properly shut down. To fix this problem, restart Windows NT and shut it down using the Shut Down command.
#1516 Partition improperly dismounted
The partition dirty flag is set in a restart record in the journal file. This error may have been caused by a power failure or system crash while the Windows NT operating system was writing the partition. Reboot Windows NT and execute CHKDSK /F to repair the damage.
#1527 Bad update sequence number
A buffer contains mismatched update sequence numbers. This error may have been caused by a power failure or system crash while the Windows NT operating system was writing to the partition. Reboot Windows NT and execute CHKDSK /F to repair the damage.
#1529 Information mismatch in directory entry
A file attribute stored in a file record is different from the attribute stored in its directory entry. If this error is in a system file (file 0-10), Windows NT's CHKDSK program will not fix it, but Windows NT will rebuild the root directory on the partition the next time the operating system is started.
#1538 Can't find contiguous space to move
The partition does not contain enough contiguous free space to hold the new copy of a file that must be contiguous. You will normally encounter this error when you use the Resize option to resize a partition smaller.

#1539 File size mismatch

The size of a system file (file 0-10) recorded in its file record does not match either the size recorded in its directory entry in the root directory or the size of its data stream.
#1544 External attribute list in external attribute
An external file record has an external attribute list.
#1545 File attributes out of order
The attributes in a file must appear in order of increasing numeric type.
#1546 Attribute neither resident nor nonresident
The attribute resident flag has a value other than resident or nonresident.

#1547 Wrong run limits

A run has more clusters than the difference between its highest and lowest cluster.
#1548 File table has fewer than 16 entries
The file table must have at least 16 entries.
#1549 File table has more than 4 billion entries
The file table must have fewer than 4 billion entries.
#1644 Bad system file sequence number
A system file has a bad sequence number. System files must have a sequence number from 0 to 10. A partition with this problem may pass a run of Windows NT's CHKDSK program, but Windows NT will not mount the partition the next time the operating system is started.
#1647 Error in root directory index
There is an error in the root directory's index. Running Windows NT's CHKDSK program will not fix this problem, but the Windows NT operating system will automatically rebuild the root directory on the partition the next time it is started.

#1654 File system smaller than partition
This is an informational message only that indicates there may be wasted space on your hard disk. However, your data is not in danger, and you do not need to do anything to correct the error.
Miscellaneous Drive Image Error Messages

#1701 Err disk not empty

Used in scripting. The DELETE ALL command failed to delete all the partitions on the drive.
#1800 Err partition not open
Attempted operation on a partition in an improperly opened image file.
#1801 Err partition not found
Did not find requested partition in image file.

#1802 Err corrupt bundle

Image file header information is not valid.
#1803 Err bundle read only
Attempted to delete or write to a partition in the image file which was opened in Read Only mode.
#1804 Err no bitmap Image
File contains no partition bitmap.

#1805 Err write failed

Error encountered while writing image to file. This error usually occurs when Drive Image runs out of space in the partition to which it is writing an image file.

#1806 Err out of memory

Out of Memory.

#1807 Err compression

Error encountered while compressing or decompressing image file data.
#1808 Err buffer too small
Buffer too small to read in partition bitmap.
#1809 Err no more free space
No more free space available to process remaining partitions.

#1810 Err open failed

Could not open image file.

#1811 Err read failed

Could not read from image file.
#1900 Err invalid drive number
Used in scripting. The script contains an invalid drive number.
FAT Check Errors (20002099)
#2001 FAT copies are not identical
Run SCANDISK to fix this error. This problem may also be caused by a virus. Run a virus checker and remove the virus if possible.
#2005 One or more lost clusters were found
Run SCANDISK or CHKDSK to fix this error.
#2012 Formatted FAT file system too big for partition
This error can be caused by the following circumstances: The number of sectors in the partition is larger than 65,536, and the bsHugeSects field of the boot sector (Big total number of sectors in Norton's DISKEDIT utility) shows that there are more sectors in the partition than the partition table shows. The number of sectors in the partition is less than 65,536, and the bsSects field of the boot sector (Total sectors on disk in Norton's DISKEDIT utility) shows that there are more sectors in the partition than the partition table shows. This situation can result in data loss when the FAT file system tries to use space outside the partition that does not exist or that belongs to another partition. Since file data may exist outside the partition boundary, you cannot fix the problem by simply patching the boot sector. To correct the error, back up all data on the partition, delete the partition, recreate the partition, and restore the data. Alternately, it has been reported that you can use Norton Disk Doctor to fix this problem.

#2013 A component of FAT geometry is bad
This error can be caused by the following circumstances: The number of clusters on the hard drive is greater than the FAT limits allow. This can result from bad values in the boot sector for the number of sectors, FATs, root entries, reserved sectors, and sectors per cluster. The number of sectors in the FAT is not large enough to hold the number of clusters present on the hard drive. A qualified consultant may be able to fix the hard drive by performing simple patches. Alternately, you can back up the data on the partition, delete the partition, recreate the partition, and restore the files.
#2024 The OS/2 Extended Attribute file is corrupt
This error is caused by any program that mistakenly writes to or overwrites the OS/2 Extended Attribute file. If this error occurs, you should back up your data, delete the partition, recreate the partition, and restore your data.