
■
You must use a mapped network boot package created from the Ghost Boot
Wizard.
■
If the boot package contains Ghost.exe then you cannot save the package to a
floppy disk set. You can save the package to a USB flash drive or an ISO image.
■
If you run Ghost.exe from any location other than A: then you must reset the
environment variable to the correct location of Wattcp.cfg before you start
Ghost.
■
DOS drivers cannot handle large files over a mapped network drive. Therefore,
Ghost sets a 2 GB split limit when writing to a mapped network drive. Before
you access a large image file over a mapped network drive you should split the
image file into spans that are no greater than 2 GB.
See
“About image file spans”
on page 47.
If you have restarted the computer with a boot package that does not contain
Ghost. exe then the computer restarts to a command prompt, for example D:\.
You must reset the Wattcp environment variable to D:\net\wattcp.cfg. You can
then start Ghost.exe from the mapped network drive.
If you have restarted the computer with a boot package that contains Ghost.exe
then Ghost starts after the computer has restarted. If GhostCasting or peer-to-peer
services are not available from the menu then ensure that Ghost is reading a
Wattcp.cfg that has SHARE_MODE=1. Exit Ghost and then at the command prompt,
reset the Wattcp environment variable. For example, if you are at the command
prompt D:\, then reset the Wattcp environment variable to D:\net\wattcp.cfg,
ensuring that D:\net\wattcp.cfg has SHARE_MODE=1. You can then restart Ghost
from either D:\ or from a mapped network drive.
To reset the environment variable to the correct location of Wattcp.cfg
1
On the command line, type the following:
set wattcp=<drive>\net\wattcp.cfg
2
Press Enter.
Establishing a peer-to-peer connection with Ghost.exe
Note:
The Linux version of Ghost supports peer to peer connections over TCP
only. It does not support LPT or USB connections.
If you are using an LPT, USB, or TCP peer-to-peer connection, then you must set
up the connection between computers before a clone, backup, or restore operation.
The computers must be physically connected using one of the following:
Using Symantec Ghost as a stand-alone program
Establishing a peer-to-peer connection with Ghost.exe
16
Summary of Contents for GHOST IMAGING FOUNDATION 7.1
Page 1: ...Symantec Ghost Imaging Foundation 7 1...
Page 3: ...Symantec Corporation 20330 Stevens Creek Blvd Cupertino CA 95014 http www symantec com...
Page 78: ...Managing partitions using GDisk Support for large hard disks 78...
Page 100: ...Editing registry keys and values using GhRegEdit Using GhRegEdit 100...
Page 116: ...Using GhostCasting to create and restore images Running Ghost exe on a client computer 116...
Page 122: ...GhostCasting from the command line GhostCast Server command line options 122...
Page 130: ...GDisk disk wipe specifications Determining disk size 130...
Page 166: ...Ghost for Linux Symantec Ghost utility support 166...
Page 170: ...Configuring firewalls Symantec Ghost port configuration 170...
Page 180: ...Troubleshooting Problems running Symantec Ghost 180...