GHOST ERROR CODES

Below is a list of the more common errors that GHOST may report. Make sure you are running the latest version as many errors have been fixed through GHOST revisions.

-----

10000
Incorrect path/file syntax. Ensure path and filename are correct and complete. Also make sure you have the proper user rights if trying to create an image file on the network.

10030
Your Multicast Client is incorrectly configured. Please check your configuration or see our GHOST Operation page at http://www.ghosthelp.com.

10060
Bad read from resource.
Network - Due to traffic or collisions.
CDROM - Due to media problem.

10082
The Demo version of GHOST has timed out. It's time to buy!

10170
Use GHOST -OR to override the check or update to the latest version which resolves this problem.

10180
Hard drive is not responding. Check cabling, power connections, jumpers and BIOS setup. Make sure your system recognizes the hard drive by running FDISK.

10210
Invalid extended partition information probably due to the use of disk overlay software like  EZ-Drive. GHOST cannot address drives entirely if they are being controlled by this type of driver.

10220
Most commonly associated with running GHOST in a Windows DOS box. Run GHOST from a DOS prompt, preferably from a DOS boot diskette.

10600
GHOST cannot continue properly due to lack of memory. See the 15040 error below for more information.

12075
Cylinder translation problem most commonly fixed by executing GHOST.EXE -FNX. This could also be caused by the absence of LBA support on drives larger than 528 mb.

12080
Commonly associated with attempting to clone disk-to-disk over a network. GHOST will only clone disk-to-disk on a network via the NetBIOS (peer to peer) convention.

12090
A physical read or write error from or to the hard drive. Try Scandisking with a full sector scan. You may have to low-level format the drive if the problem persists.

14030
An unregistered version of GHOST has encountered a file with a date beyond its expiration date. Scan your system for files beyond this date and temporarily remove them from the system to allow GHOST to continue. You can locate the offender by looking at the drive:\path\filename at the bottom of the GHOST window when this error occurs.

15010 - 15020 - 15030 - 15050
Usually due to problems dealing with the EA DATA. SF file. Run GHOST.EXE -E to get around this error.

15040
GHOST cannot execute properly due to lack of conventional memory. Make sure you're loading upper memory drivers in your config.sys or preferably upgrade to v4.x. Below is an example of a possible config.sys configuration:

device=himem.sys
device=emm386.exe noems i=b000-b7ff
dos=high,umb
devicehigh=(your device driver)
devicehigh=(your device driver) etc.

Below are devices you DO NOT need. They will not benefit GHOST's performance.

setver.exe
smartdrv.exe or any other disk cache utility
mouse.com or any other mouse driver

15100
Use GHOST -OR to override the check or update to the latest version which resolves this problem.

15150 - 15160
Probable corrupt image file. Run the "Check image file integrity..." option from the Local/Server menu. Most commonly evident following an image "Drag and Drop" copy. When copying images, open up a DOS window and use the "copy /v x:\image.gho y:\image.gho" to force verification of the copy.

15165
GHOST came across a marginal file usually located in an Internet Browser's cache directory. You can locate the offender by looking at the drive:\path\filename at the bottom of the GHOST window when this error occurs. Update to the latest version which resolves this problem.

15170
Due to an unformatted or invalid partition on the source hard drive. Make certain the source drive is completely allocated as GHOST looks for 100% viable media.

15175
Older error associated with the Compaq diagnostic paritition. Update to the latest version.

16040
Too many partitions on your drive. Resolved in GHOST v3.x.

19080
Most likely GHOST came accross a directoryname or filename that is corrupt.

19320
GHOST cannot continue properly due to lack of memory. See the 15040 error above for more information.

19330
Due to the incorrect FAT type in your Master Boot Record. Most commonly occurs when your partition is NTFS but the partition information is still configured as FAT16. You will need to call Technical Support to solve this problem.

19900
Unable to start Multicasting. Please follow the troubleshooting procedure below.

1. Check that the Network Interface Card (NIC) and cables are correctly installed and connected.

2. Check that the NIC has been set up correctly using the setup program included with the NIC.

3. Check the setup of the driver. Read the documentation for the driver you are using, and note if there any special options needed to be used for your network setup.

3.a. For a NDIS2 Driver, review the documentation or example PROTOCOL.INI file included with the NIC's NDIS2 driver and add in any required additional parameters into the PROTOCOL.INI files PC_CARD section on the boot disk. Check and note any errors reported when the drivers are loaded. An inability to bind usually means the parameters specified for the NIC in the PROTOCOL.INI PC_CARD section are incomplete or incorrect.

3.b. For a Packet Driver, review the documentation and command line options for the packet driver and add any additional switches and values. Check and note any errors reported when the drivers are loaded.

4. Check the WATTCP.CFG file and/or DHCP/BOOTP Settings.

5. Check that the WATTCP.CFG file is located in directory where ghost is being run from. For example, if GHOST is located at c:\ghost\ghost.exe and you are running ghost from c:\, the WATTCP.CFG file should be located in c:\.

6. Check all TCP/IP configuration settings. Ensure both the server and clients have valid IP addresses and associated subnet masks.

7. If routers are present between the client and server, ensure the gateway is set up on the local subnet and it is specified in the WATTCP.CFG file or the BOOTP/DHCP response.

8. If this continues to fail, try an alternative packet driver set-up for the NIC. For example, If you are trying to use the NIC's packet driver, then set up the NDIS2 DOS driver with the GHOST supplied NDIS to Packet Driver shim. Repeat the above check list.

9. Start the GHOST Multicast Client with full Multicast logging (ALL logging setting). For details on how to do this, refer to the GHOST User Guide Appendix G. These logs will assist Technical Support in further diagnosing the problem.

25002 - 25004 - 25007 - 27063
NTFS contiguity errors in GHOST versions prior to v5.x. GHOST had a problem replicating the fragmentation which is inherent to NTFS. You can overcome this problem by defragmenting the source drive with an application such as Diskeeper (available at http://www.diskeeper.com) prior to cloning or execute your older GHOST.EXE with the -NTC switch.