254
Files included in a Ghost package
The following files are required to run Ghost.exe and are included in a boot
package:
The Ghost executable that is run from DOS.
Note: Mapped Network Drive packages might not include
Ghost.exe.
Ghost.exe
PC-DOS is supplied for the purpose of creating Ghost boot
packages. The DOS files are installed automatically when
you create the boot package using the Ghost Boot Wizard.
DOS system files
This includes CD-R/RW drivers, network protocol files, or
network interface card (NIC) drivers, or any other files for
external storage access.
Note: For best performance , you should use the latest
version of the NIC driver. You might need to download the
driver from the manufacturer.
Any files and drivers
required to access the
selected hardware
Note: In versions previous to 8.0 of Symantec Ghost, MSCDEX was required to
read an image from a CD. If you created a bootable CD using any version of
Symantec Ghost you do not need to include MSCDEX in the boot package. If you
created a bootable CD with another utility, MSCDEX must be included.
When to include a network card driver
If the boot package includes network support, the Universal Packet Driver (UNDI
driver) enables detection of network cards in most computers without a specific
network card driver. If the boot package does not work on a computer, then a new
boot package must be created that uses the correct network card driver.
The UNDI driver can replace a specific driver in most of the following situations:
■ If the computer has been manufactured within the last two or three years
■ If the computer supports network booting using PXE (version 2.1)
Note: Symantec Ghost supports any version of PXE when booting a computer
over a network from a PXE server.
The UNDI drivers support multiple network interface cards (NIC) in a computer.
If you have more than one NIC in your computer, and you do not use the UNDI
Creating boot packages with the Ghost Boot Wizard 255
Files included in a Ghost package
driver, then it is possible that Ghost might not select the correct card. If you do
not want to use the UNDI driver, then you should edit the Protocol.ini file to select
the correct card.
See “Symantec Ghost support for multiple network interface cards ” on page 286.
The UNDI driver installation loads a driver from the option ROM of a network
card. If any one of the following is disabled in the BIOS, you must enable the option
in the BIOS before using the UNDI driver:
■ Option ROM
■ PXE
■ UNDI
Symantec provides a Universal Packet Driver, but to create a mapped network
boot package, you must provide a Universal NDIS Driver. You can download this
from the 3Com Site at the following URL:
http://support.3com.com/infodeli/tools/nic/mba.htm
When creating the mapped network boot package you are prompted for the location
of the Universal NDIS Driver.
When to include MS-DOS in a boot package
By default, Symantec Ghost includes PC-DOS in a Ghost boot package. However,
some computer models may not start from a Ghost boot package that contains
PC-DOS. If your computer does not start from a Ghost boot package, you should
create a new Ghost boot package from the Ghost Boot Wizard and include Windows
95/98 MS-DOS.
Before you create an MS-DOS Ghost boot package, you must provide Windows
95/98 MS-DOS for the computer that is running the Ghost Boot Wizard.
See “Providing MS-DOS” on page 284.
Opening the Ghost Boot Wizard
After you start the Ghost Boot Wizard, you can create boot packages.
To open the Ghost Boot Wizard
■ on the Windows taskbar, click Start > Programs > Symantec Ghost > Ghost
Boot Wizard.
Creating boot packages with the Ghost Boot Wizard
Opening the Ghost Boot Wizard
256
Selecting which boot package to create
You can include any of the following features in a boot package:
■ Support for CD-R/RW, DVD, LPT, USB, and FireWire
■ Network support for TCP/IP peer-to-peer connections and GhostCasting
■ Support for reading and writing an image to and from CD/DVD
■ Support for mapping network drives
■ An image of the Console Boot Partition.
■ RIS boot packages that support Microsoft Remote Installation Service (RIS)
with Symantec Ghost
■ TCP/IP network boot images that use 3Com DynamicAccess Boot Services to
allow access to Symantec Ghost without a boot disk
Table 11-1 provides information about the types of boot packages that you can
make and how they can be used.
Table 11-1 Boot package types
Intended use Ghost Boot Wizard options
You can use either of the following
options:
■ Standard Ghost Boot Package
See “Standard boot packages”
on page 259.
■ Network Boot Package
See “Boot packages with network
support” on page 264.
Local use of Ghost.exe:
■ Disk-to-disk
■ Partition-to-partition
■ Disk or partition to and from local JAZ or ZIP
drive
Standard Ghost Boot Package
See “Standard boot packages”
on page 259.
■ Clone, back up, or restore over peer-to-peer
connection between two computers using LPT,
FireWire, or USB cable.
Creating boot packages with the Ghost Boot Wizard 257
Selecting which boot package to create
Table 11-1 Boot package types (continued)
Intended use Ghost Boot Wizard options
You can use either of the following
options:
■ Network Boot Package
See “Boot packages with network
support” on page 264.
■ Drive Mapping Boot Package
See “Creating a boot package that
supports mapped network drives”
on page 265.
Note: A Drive Mapping Boot Package
supports NDIS drivers but does not
support using packet drivers. To use
Ghost.exe with network support using
packet drivers, you should create a
Network Boot Package.
■ Clone, back up, or restore over TCP/IP
peer-to-peer connection with network support
between two computers.
Standard Ghost Boot Package
See “Standard boot packages”
on page 259.
■ Back up or restore a computer onto an image
file on a CD/DVD that is on a CD/DVD writer
supported by Symantec Ghost.
CD/DVD Startup Boot Package with
Ghost
See “Boot packages with CD and DVD
support” on page 268.
■ Restore a computer from a Ghost image file
on a CD that is on a CD-R/RW drive not
supported by Symantec Ghost. The image file
was not stored on the CD using Symantec
Ghost. Contains generic CD drivers.
■ Access files other than a Ghost image file on
a CD.
Drive Mapping Boot Package
See “Creating a boot package that
supports mapped network drives”
on page 265.
■ Map a drive on a workstation to a shared
resource on a server and use Symantec Ghost
to clone, back up, or restore.
Console Boot Partition
See “Creating a boot image containing
the Console boot partition” on page 269.
■ Install the Console boot partition on a client
computer.
TCP/IP Network Boot Image
See “Starting client computers in
Ghost.exe from the network” on page 273.
■ Start Ghost.exe on a client computer from the
network (without a boot disk).
Creating boot packages with the Ghost Boot Wizard
Selecting which boot package to create
258
Table 11-1 Boot package types (continued)
Intended use Ghost Boot Wizard options
TCP/IP Network Ghost Client Boot
Image
See “Starting client computers from the
network to connect with the Symantec
Ghost Console” on page 274.
■ Start a client computer from the network to
connect to the Symantec Ghost Console.
Microsoft RIS Boot Option
See “Boot packages that support
Remote Installation Service (RIS)”
on page 271.
■ Create an entry in the RIS menu on a client
computer to start the computer from the
network.
Creating boot packages
After you have decided which boot which boot package to create you can create
it.
Standard boot packages
The Ghost Boot Wizard creates a boot package that does the following:
■ Runs Ghost.exe for local operations.
■ Writes Ghost images directly to media on a CD/DVD writer supported by
Symantec Ghost. The media must be supported by the CD/DVD writer.
■ Runs Ghost.exe on two computers that are connected by either an LPT or USB
cable.
■ Runs Ghost.exe to back up to or restore from an external device that is
connected by USB or FireWire.
To create standard boot package
1 In the Ghost Boot Wizard window, click Standard Ghost Boot Package.
2 Click Next.
Creating boot packages with the Ghost Boot Wizard 259
Creating boot packages
3 Select one or more of the following:
USB support To add support for USB peer-to-peer to the boot package.
To set the USB peer-to-peer drivers.
See “Setting the USB peer-to-peer drivers” on page 261.
Advanced
To add support for LPT peer-to-peer to the boot package.
See “Setting the LPT port or mode” on page 261.
LPT support
Advanced To change the LPT mode or port.
To add Adaptec ASPI drivers to the boot package.
These drivers are required to write an image directly to a SCSI
CD-R that is supported by Symantec Ghost.
Include Adaptec
ASPI drivers
4 Select one of the following:
■ Use PC-DOS
■ Use MS-DOS
See “Providing MS-DOS” on page 284.
5 Click Next.
6 In the Ghost.exe field, type the correct path if the executable has been moved
or you want to use a different version of Symantec Ghost.
The default path to Ghost.exe appears in the Ghost.exe field.
7 In the Parameters field, type any required command-line parameters.
See “Adding command-line parameters to a boot package” on page 282.
8 Click Next.
9 If you want to move control of USB devices from the BIOS to Ghost, check
Override BIOS USB control.
This option is unavailable if you have previously included USB support in the
boot package.
Do not select this option if you are creating a bootable USB device.
10 If you want to move control of FireWire devices from the BIOS to Ghost, check
Override BIOS FireWire control.
11 Click Next.
Creating boot packages with the Ghost Boot Wizard
Creating boot packages
260
12 Select a destination for the boot package.
See “Selecting a destination drive” on page 262.
13 Review the boot package details and click Next to start creating the boot
package.
Follow the prompts to create a boot package.
Setting the USB peer-to-peer drivers
You can select USB peer-to-peer drivers to include in the boot package. In most
cases, you do not need to change the default driver setting. If you have problems
connecting using peer-to-peer, then select another option and try again.
To set USB peer-to-peer drivers
1 In the Load USB drivers dialog box, select one of the following:
Includes All drivers all USB peer-to-peer drivers in the boot package
UHCI driver Includes only UHCI drivers in the boot package
OHCI driver Includes only OHCI drivers in the boot package
2 Click OK.
Setting the LPT port or mode
The default mode for an LPT connection is ECP/EPP. If you are having problems
with your LPT connection, set the mode to Bidirectional 8bit or Bidirectional 4bit.
The next time that you create a boot package, the mode is reset to the default,
ECP/EPP High Speed.
If you have multiple parallel ports and want to connect using a port other than
the default LPT1, use the LPT port option to specify the port into which your cable
is plugged.
To set the LPT port or mode
1 In the LPT configuration dialog box, under Mode, select one of the following:
■ ECP/EPP High Speed
■ Bidirectional 8bit
■ Bidirectional 4bit
2 Under Port, select one of the following:
■ Default
Creating boot packages with the Ghost Boot Wizard 261
Creating boot packages
■ LPT1
■ LPT2
■ LPT3
3 Click OK.
Selecting a destination drive
You can select one of the following destinations for the boot package:
This option is unavailable if you are creating a Drive Mapping Boot
Package that includes Ghost.exe.
Floppy disk set
This option lets you create an ISO image that you can write to a CD
or DVD using third-party software.
This option is unavailable if you use a Multicard template.
ISO image
Symantec fully supports USB flash drives as a removable device;
however, other devices also work with this options. The client
computer must support starting from the device and be configured
correctly. For example, the BIOS must support the option to start from
the device.
For a list of supported devices, see the Knowledgebase article at the
following URL:
http://service1.symantec.com/SUPPORT/ghost.nsf/docid/2006081110304125
A 2 GB partition is created on the device, and any remaining space on
the device becomes unavailable. The device is reformatted, and any
existing data is overwritten.
Removable and
unremovable
devices
Warning: All information on the selected device is deleted. The device is
automatically formatted before use.
Creating boot packages with the Ghost Boot Wizard
Creating boot packages
262
To select a package type
1 In the Destination Drive window, select one of the following:
Format floppy disk Lets you create a floppy disk boot set
set
Create ISO image Lets you create an ISO image to write to a CD/DVD
Lets you create a boot package on a removable or unremovable
device
Format Disk
2 Select one of the following destination options for the selected package type:
Format floppy disk See “To set floppy disk options” on page 263.
set
Create ISO image See “To set ISO image options” on page 263.
Format Disk See “To set removable or unremovable disk options” on page 264.
To set floppy disk options
1 In the Destination Drive window, in the Floppy Disk Drive field, select the
appropriate drive letter.
2 In the Number of disk sets to create field, select the number that you want
to create.
3 Ensure that Format disk(s) First is checked to format the disks before disk
creation.
Ensure that this option is checked unless you are creating a custom boot disk
with custom system files. If this option is unchecked, the boot disk is not
bootable.
4 Ensure that Quick Format is checked to perform a quick format.
5 Click Next.
To set ISO image options
1 In the Destination Drive window, click Browse and select a location and file
name for the image file.
2 Click Next.
Creating boot packages with the Ghost Boot Wizard 263
Creating boot packages
To set removable or unremovable disk options
1 In the Destination Drive window, under Available Devices, click the down
arrow, and select one of the devices listed.
2 If you want to display unremovable devices, uncheck Show only removable
devices.
3 If you want to add support for creating a bootable CD/DVD, click Support for
creating bootable CD/DVDs.
This option adds an image of a bootable floppy disk to the boot package. If
you are using Ghost to write an image directly to a CD or DVD, this option
adds support for making the CD or DVD bootable.
4 Click Next.
Boot packages with network support
The Ghost Boot Wizard helps you create boot packages that provide network
support for GhostCasting and TCP/IP peer-to-peer connections.
To create a boot package with network support
1 In the Ghost Boot Wizard window, click Network Boot Package.
2 Click Next.
3 In the Network Interface Card window, do one of the following:
■ Select the Universal Packet Driver, and then click Next.
See “When to include a network card driver” on page 255.
■ Click Show all drivers, select or add a network driver, and then click Next.
See “Selecting and adding a network driver” on page 276.
4 Select one of the following:
■ Use PC-DOS
■ Use MS-DOS
See “Providing MS-DOS” on page 284.
5 Click Next.
6 Click Symantec Ghost to create a boot package for the client that loads
Symantec Ghost. You can connect to a running GhostCast Server to transfer
image files to and from the client.
The default path to Ghost.exe is entered in the Ghost.exe field. If the
executable has been moved, or you want to use a different version of Ghost.exe,
type the correct path.
Creating boot packages with the Ghost Boot Wizard
Creating boot packages
264
7 In the Parameters field, type any required command-line parameters.
See “Adding command-line parameters to a boot package” on page 282.
8 Click Next.
9 If you want to move control of USB devices from the BIOS to Ghost, check
Override BIOS USB control.
This option is unavailable if you have previously included USB support in the
boot package.
Do not select this option if you are creating a bootable USB device.
10 If you want to move control of FireWire devices from the BIOS to Ghost, check
Override BIOS FireWire control.
11 Click Next.
12 Do one of the following:
■ Click DHCP will assign the IP settings if your network contains a DHCP
server.
■ Click The IP settings will be statically defined and complete the fields
below this option if your network does not contain a DHCP server.
If you create more than one boot package, then the static IP address
incrementally increases as each boot package is created.
13 If you want to alter the number of router hops then select the correct number
in Router Hops.
This specifies how many routers the client searches across when attempting
to find the Multicast Server. The default value of 16 lets Ghost find the server
as long as it is not more than 16 router hops away. This is sufficient for most
networks.
14 Click Next.
15 Select a destination for the boot package.
See “Selecting a destination drive” on page 262.
16 Review the boot package details and click Next to start creating the boot
package.
Follow the prompts to create a boot package.
Creating a boot package that supports mapped network drives
You can use the Ghost Boot Wizard to create boot packages that map a drive letter
to a shared resource on a network server. This drive mapping lets you access a
network drive from Ghost.exe.
Creating boot packages with the Ghost Boot Wizard 265
Creating boot packages
You can choose to include Ghost.exe in the boot package. If you do not include
Ghost.exe, you must run Ghost from the network drive. If you include Ghost.exe
in the boot package, you cannot create a boot package on a floppy disk set. You
can save the package to a USB flash drive or an to an ISO image.
Note: A Drive Mapping Boot Package supports NDIS drivers but does not support
using packet drivers. If you want to run Ghost.exe with network support and you
want to use packet drivers, you should create a Network Boot Package.
Note: If you do not run Ghost.exe from the A drive, then you must reset the
environment variable WATTCP to provide the location of the Wattcp.cfg file.
See “To reset the environment variable to the correct location of Wattcp.cfg”
on page 326.
To create a boot package that supports mapped network drives
1 In the Ghost Boot Wizard window, click Drive Mapping Boot Package.
2 Click Next.
3 In the Network Interface Card window, do one of the following:
■ In the driver list, double-click the Universal NDIS Driver, browse to the
location of the Universal NDIS Driver files, and then click OK.
See “When to include a network card driver” on page 255.
■ In the driver list, select or add a network driver, and then click Next.
See “Selecting and adding a network driver” on page 276.
4 Select one of the following:
■ Use PC-DOS
■ Use MS-DOS
See “Providing MS-DOS” on page 284.
5 Click Get MS Client and browse to the MS-DOS Client files to include if you
are using MS-DOS.
If you are using MS-DOS, you must include the Microsoft DOS Client files.
You must install the files on the Ghost Boot Wizard computer before you can
include them in the boot package.
See “Installing MS-DOS Client files” on page 285.
6 Click Next.
Creating boot packages with the Ghost Boot Wizard
Creating boot packages
266
7 In the Client type dialog box, check Do not include any Ghost executables if
you do not want to include Ghost.exe in the boot package.
If you do not include Ghost.exe in the package, you must run Ghost from a
network drive. If you do not include Ghost.exe in the package, then the
remaining Client Type boxes are unavailable.
8 Click Symantec Ghost to create a boot package for the client that loads
Symantec Ghost. You can connect to a GhostCast Server to transfer image
files to and from the client.
The default path to Ghost.exe is entered in the Ghost.exe field. If the
executable has been moved, or you want to use a different version of Ghost.exe,
type the correct path.
9 In the Parameters field, type any required command-line parameters.
See “Adding command-line parameters to a boot package” on page 282.
10 Click Next.
11 If you want to move control of USB devices from the BIOS to Ghost, check
Override BIOS USB control.
This option is unavailable if you have previously included USB support in the
boot package or if you have selected not to include Ghost.exe in the boot
package.
Do not select this option if you are creating a bootable USB device.
12 If you want to move control of FireWire devices from the BIOS to Ghost, check
Override BIOS FireWire control.
This option is unavailable if you have selected not to include Ghost.exe in the
boot package.
13 Click Next.
14 In the Client Computer Name field, type the name of the client computer.
This specifies the name of the computer after it starts from the package and
does not have to be the same name given to the computer in Windows. If you
create more than one package, a number is added to the computer name so
that the names for subsequent packages are unique.
15 In the User Name field, type the user name that the boot package will use to
log on to the network.
This user must exist on the network and have sufficient access rights to the
mapped network drive, files, and directories that you want to use.
16 In the Domain field, type the domain to which the user belongs.
Creating boot packages with the Ghost Boot Wizard 267
Creating boot packages
17 In the Drive Letter field, select a drive letter to access a network share through
a mapped drive.
Select a drive letter greater than any existing drive letter.
18 If you want to prevent the boot package from mapping a drive when the
computer starts, click None.
In this case, map a drive from the DOS prompt after the computer has started.
19 In the Maps To field, type the complete UNC path to the network share.
For example, to access a shared folder named Ghost on a computer named
Boss, the UNC path is \\Boss\Ghost.
20 Click Next.
21 Do one of the following:
DHCP will assign the IP If your network contains a DHCP server
settings
Complete the fields below this option if your network
does not contain a DHCP server. Your network
administrator can provide the values for these fields.
The IP settings will be
statically defined
22 Click Next.
23 Select a destination for the boot package.
If you have selected to include Ghost.exe in the boot package then you cannot
create a floppy disk set.
See “Selecting a destination drive” on page 262.
24 Review the boot package details and click Next to start creating the boot
package.
Follow the prompts to create a boot package.
Boot packages with CD and DVD support
A boot package with CD/DVD support lets you access images and other files stored
on CD-R/RW and DVD drives that are not supported by Symantec Ghost.
This kind of package also contains the DOS system files and Ghost.exe.
To create a boot package with CD-ROM and DVD support
1 In the Ghost Boot Wizard window, click CD/DVD Startup Package with Ghost.
2 Click Next.
Creating boot packages with the Ghost Boot Wizard
Creating boot packages
268
3 Select one of the following:
■ Use PC-DOS
■ Use MS-DOS
See “Providing MS-DOS” on page 284.
4 Click Next.
5 In the Ghost.exe field, type the correct path if the executable has been moved
or you want to use a different version of Ghost.exe.
The default path to the Ghost.exe appears in the Ghost.exe field.
6 In the Parameters field, type any required command-line parameters.
See “Adding command-line parameters to a boot package” on page 282.
7 Click Next.
8 If you want to move control of USB devices from the BIOS to Ghost, check
Override BIOS USB control.
Do not select this option if you are creating a bootable USB device.
9 If you want to move control of FireWire devices from the BIOS to Ghost, check
Override BIOS FireWire control.
10 Click Next.
11 Select a destination for the boot package.
See “Selecting a destination drive” on page 262.
12 Review the boot package details and click Next to start creating the boot
package.
Follow the prompts to create a boot package.
Creating a boot image containing the Console boot partition
You can create an image that contains the Console boot partition. Install this
image on client computers to allow remote control by the Console.
See “Installing the Console client” on page 58.
To create a boot image that contains a Console boot partition
1 In the Ghost Boot Wizard window, click Console Boot Partition.
2 Click Next.
3 In the Network Interface Card window, do one of the following:
■ Select the Universal Packet Driver and click Next.
See “When to include a network card driver” on page 255.
Creating boot packages with the Ghost Boot Wizard 269
Creating boot packages
■ Click Show all drivers, select or add a network driver and then click Next.
See “Selecting and adding a network driver” on page 276.
4 Select one of the following:
■ Use PC-DOS
■ Use MS-DOS
See “Providing MS-DOS” on page 284.
5 Click Next.
6 Type the correct path in the Ghost.exe field if the executable has been moved,
or you want to use a different version of Ghost.exe.
The default path to Ghost.exe appears in the Ghost.exe field.
7 Type the correct path in the Ngctdos.exe field if the executable has been
moved, or you want to use a different version.
The default path to the Ghost DOS client executable appears in the Ngctdos.exe
field.
8 Type the correct path in the Ghstwalk.exe field if the executable has been
moved, or you want to use a different version.
The default path to the Ghost Walker executable is entered in the Ghstwalk.exe
field.
9 In the Machine Group field, type the computer group folder, if required.
When a Console Client is first discovered on the network, the Console creates
an icon for it in the Machine Group section of the Default folder. When DOS
Console Client computers are discovered, they are identified by Adapter
Address only. Specifying a group folder makes identification of the computer
easier.
10 Click Next.
11 Do one of the following:
DHCP will assign the IP If your network contains a DHCP server
settings
Complete the fields below this option if your network
does not contain a DHCP server. Your network
administrator can provide the values for these fields.
The IP settings will be
statically defined
Creating boot packages with the Ghost Boot Wizard
Creating boot packages
270
12 If you want to alter the number of router hops then select the correct number
in Router Hops.
This specifies how many routers the client searches across when attempting
to find the Multicast Server. The default value of 16 lets Ghost find the server
as long as it is not more than 16 router hops away. This is sufficient for most
networks.
13 Click Next.
14 In the Image File field, type a name for the image file.
15 In the Description field, type a description for the image file.
16 To execute creation of the image file, click Next.
Boot packages that support Remote Installation Service (RIS)
Ghost Boot Wizard Remote Installation Service (RIS) leverages the Preboot
Execution Environment (PXE) feature of PC-98 specified computers to provide a
remote installation service for Windows 2000. Symantec Ghost provides a cloning
solution suitable for deployment or migration of any computer operating system
with specific support for Microsoft Windows. Symantec Ghost also works with
Windows systems prepared with the Microsoft SysPrep tool.
You can create a RIS boot package in the Symantec Ghost Boot Wizard only when
running on a Windows 2000/2003/XP server with RIS installed. An entry for the
boot package appears in the RIS menu.
Note: This option only appears if Microsoft Remote Installation Service is installed
on your computer.
To create a boot package that supports RIS
1 In the Ghost Boot Wizard window, click Microsoft RIS Boot Option.
2 Select the generic PXE packet driver template.
3 Click Next.
4 Select one of the following:
■ Use PC-DOS
■ Use MS-DOS
See “Providing MS-DOS” on page 284.
5 Click Next.
Creating boot packages with the Ghost Boot Wizard 271
Creating boot packages
6 Click Symantec Ghost to create a boot package that loads Symantec Ghost.
You can connect to a running GhostCast Server to transfer image files to and
from the client.
The default path to Ghost.exe is entered in the Ghost.exe field. If the
executable has been moved, or you want to use a different version of Ghost.exe,
type the correct path.
7 In the Parameters field, type any required command-line parameters.
See “Adding command-line parameters to a boot package” on page 282.
8 Click Next.
9 If you want to move control of USB devices from the BIOS to Ghost, check
Override BIOS USB control.
Do not select this option if you are creating a bootable USB device.
10 If you want to move control of FireWire devices from the BIOS to Ghost, check
Override BIOS FireWire control.
11 Click Next.
12 Do one of the following:
DHCP will assign the IP If your network contains a DHCP server
settings
Complete the fields below this option if your network
does not contain a DHCP server. Your network
administrator can provide the values for these fields.
The IP settings will be
statically defined
13 If you want to alter the number of router hops then select the correct number
in Router Hops.
This specifies how many routers the client searches across when attempting
to find the Multicast Server. The default value of 16 lets Ghost find the server
as long as it is not more than 16 router hops away. This is sufficient for most
networks.
14 Click Next.
15 In the RIS Boot Menu Name field, type the name that will appear on the RIS
Boot menu.
When you select this menu item, the client computer starts from the network
card.
Creating boot packages with the Ghost Boot Wizard
Creating boot packages
272
16 In the RIS Boot Description field, type a description for the boot package.
This text appears as a help message when the menu option is selected.
In the RIS Boot directory field, the name of the directory under the main RIS
tree in which the boot package is installed is displayed.
The contents of this field are generated from the text you type for the RIS
menu name. You should not change the text in this field from the default.
17 Click Next.
18 Select a language if there is more than one.
19 Click Next.
20 Review the boot package details and click Next to start creating the image
file.
Starting client computers in Ghost.exe from the network
You can create an image file that lets you start client computers in Ghost.exe,
from the network, using 3Com DynamicAccess Boot Services software.
To create an image file to start client computers from the network
1 In the Ghost Boot Wizard window, click TCP/IP Network Boot Image.
2 Click Next.
3 In the Network Interface Card window, do one of the following:
■ Select the Universal Packet Driver, and click Next.
See “When to include a network card driver” on page 255.
■ Click Show all drivers, select or add a network driver, and then click Next.
See “Selecting and adding a network driver” on page 276.
4 Select one of the following:
■ Use PC-DOS
■ Use MS-DOS
See “Providing MS-DOS” on page 284.
5 Click Next.
6 Click Symantec Ghost to include the Ghost client in the boot package.
The default path to Ghost.exe is entered in the Ghost.exe field. If the
executable has been moved, or you want to use a different version of Ghost.exe,
type the correct path.
Creating boot packages with the Ghost Boot Wizard 273
Creating boot packages
7 In the Parameters field, type any required command-line parameters.
See “Adding command-line parameters to a boot package” on page 282.
8 Click Next.
9 If you want to move control of USB devices from the BIOS to Ghost, check
Override BIOS USB control.
Do not select this option if you are creating a bootable USB device.
10 If you want to move control of FireWire devices from the BIOS to Ghost, check
Override BIOS FireWire control.
11 Click Next.
12 Do one of the following:
DHCP will assign the IP If your network contains a DHCP server
settings
Complete the fields below this option if your network
does not contain a DHCP server. Your network
administrator can provide the values for these fields.
The IP settings will be
statically defined
13 If you want to alter the number of router hops then select the correct number
in Router Hops.
This specifies how many routers the client searches across when attempting
to find the Multicast Server. The default value of 16 lets Ghost find the server
as long as it is not more than 16 router hops away. This is sufficient for most
networks.
14 Click Next.
15 In the Image File field, type a file name for the image file.
This image can be used with any BOOTP/TFTP server.
16 Click Next.
17 Review the boot package details and click Next to start creating the image
file.
Starting client computers from the network to connect with the
Symantec Ghost Console
You can create an image file that lets you start client computers from the network
and connect to the Symantec Ghost Console, using 3Com DynamicAccess Boot
Services software.
Creating boot packages with the Ghost Boot Wizard
Creating boot packages
274
To create an image file to start client computers from the network
1 In the Ghost Boot Wizard window, click TCP/IP Network Ghost Client Boot
Image.
2 Click Next.
3 In the Network Interface Card window, do one of the following:
■ Select the Universal Packet Driver, and click Next.
See “When to include a network card driver” on page 255.
■ Click Show all drivers, select or add a network driver, and then click Next.
See “Selecting and adding a network driver” on page 276.
4 Select one of the following:
■ Use PC-DOS
■ Use MS-DOS
See “Providing MS-DOS” on page 284.
5 Click Next.
6 Type the correct path in the Ghost.exe field if the executable has been moved,
or you want to use a different version of Ghost.exe.
The default path to Ghost.exe appears in the Ghost.exe field.
7 Type the correct path in the Ngctdos.exe field if the executable has been
moved, or you want to use a different version.
The default path to the Ghost DOS client executable appears in the Ngctdos.exe
field.
8 Type the correct path in the Ghstwalk.exe field if the executable has been
moved, or you want to use a different version.
The default path to the Ghost Walker executable is entered in the Ghstwalk.exe
field.
9 In the Machine Group field, type the computer group folder, if required.
When a Console Client is first discovered on the network, the Console creates
an icon for it in the Machine Group section of the Default folder. When DOS
Console Client computers are discovered, they are identified by Adapter
Address only. Specifying a group folder makes identification of the computer
easier.
10 Click Next.
Creating boot packages with the Ghost Boot Wizard 275
Creating boot packages
11 Do one of the following:
DHCP will assign the IP If your network contains a DHCP server
settings
Complete the fields below this option if your network
does not contain a DHCP server. Your network
administrator can provide the values for these fields.
The IP settings will be
statically defined
12 If you want to alter the number of router hops then select the correct number
in Router Hops.
This specifies how many routers the client searches across when attempting
to find the Multicast Server. The default value of 16 lets Ghost find the server
as long as it is not more than 16 router hops away. This is sufficient for most
networks.
13 Click Next.
14 In the Image File field, type a file name for the image file.
This image can be used with any BOOTP/TFTP server.
15 Click Next.
16 Review the boot package details and click Next to start creating the image
file.
Selecting and adding a network driver
If the Universal Network Driver cannot access the network interface card installed
in the target computer then you must either select or add a driver.
Unless you use the multicard template, you must create a boot package for each
network card.
To select or add a network driver
■ In the Network Interface Card window, do one of the following:
■ Select the network driver for the make and model of the network card
installed on the client computer.
See “Selecting a template” on page 277.
■ If the correct driver is not in the list, add the driver.
See “Adding network drivers to the Ghost Boot Wizard” on page 279.
You can add more than one driver to the boot package.
See “Creating a multicard template” on page 278.
Creating boot packages with the Ghost Boot Wizard
Selecting and adding a network driver
276
Selecting a template
For the boot package to work correctly, it is important that you select the correct
template. When you create a boot package for client computers, the template that
you select must be suitable for the network cards installed in the computers that
are to start from the package. You can use the Ghost Console to check the client
computer's network interface card in the Ghost Console.
See “Viewing Symantec Ghost Console resource properties” on page 84.
If the client computer is not installed with the Console client, then you can find
the name of the driver from Network Properties within Windows. This must be
done on the client computer for which you are preparing the boot package. The
name of the network interface card as shown in Windows may not exactly match
the name of the correct template in the Ghost Boot Wizard. For example, Windows
might list the card as 3Com Fast EtherLink XL 10/100Mb TX Ethernet NIC
(3C905B-TX). In this case, 3C905B-TX is the model number of the card. Therefore,
you can use the Ghost Boot Wizard template that is named 3COM 3C90X. This
template works for all 3C90- cards.
In some cases, you might have a choice between an NDIS2 driver and a packet
driver version of the same template. Both templates should work, but you might
find that one gives better performance. You can experiment to determine which
one works better.
It is possible that there is no existing template in the Ghost Boot Wizard that is
suitable for the network interface card installed in your computer. In this case,
obtain the DOS drivers for the network interface card either from the disk supplied
with the card or from the manufacturer’s Web site, and add a new template to the
Ghost Boot Wizard.
See “Adding network drivers to the Ghost Boot Wizard” on page 279.
If you have different network interface cards installed in client computers, then
you may be able to use the multicard template to create a single boot package that
works on each of your computers without modification.
To determine which network interface card is installed on a Windows 98 computer
1 on the Windows taskbar, click Start > Settings > Control Panel.
2 Double-click System.
3 Click Device Manager.
4 Expand Network Adapter.
The make and model of the installed network interface card are listed.
Creating boot packages with the Ghost Boot Wizard 277
Selecting a template
To determine which network interface card is installed on a Windows NT 4 computer
1 on the Windows taskbar, click Start > Settings > Control Panel.
2 Double-click Network.
The make and model of the installed network interface card are listed on the
Adapters tab.
To determine which network interface card is installed on a Windows 2000 computer
1 on the Windows taskbar, click Start > Settings > Control Panel.
2 Double-click System.
3 on the Hardware tab, click Device Manager.
4 Expand Network adapters.
The make and model of the installed network interface card are listed.
To determine which network interface card is installed on a Windows XP computer
1 on the Windows taskbar, click Start > Control Panel > System.
2 on the Hardware tab, click Device Manager.
3 Expand Network adapters.
The make and model of the installed network interface card are listed.
Creating a multicard template
You can use multicard templates to create a boot package containing several
NDIS2 drivers. When the computer starts from the boot package, a special
multicard driver checks the computer’s hardware to see if any of the NDIS2 drivers
can be used to access the installed network card.
Multicard templates are useful because several makes and models of network
cards are often used in a single LAN. You can create a single boot package for use
with all of your computers without modification.
Note: Multicard templates are not supported for ISO images.
Refer to the Software License Agreement for use restrictions.
Creating boot packages with the Ghost Boot Wizard
Creating a multicard template
278
To create a multicard template
1 In the Network Interface Card window, ensure that Show All Drivers is
checked.
The Network Interface Card window appears when you create a boot package
that requires a NIC. It is the second window in the Ghost Boot Wizard.
2 Click Multicard Template.
3 Click Next.
4 In the list of NDIS2 drivers, select the required drivers.
If you create a floppy disk set you should select no more than four or five
drivers. The space is limited on a floppy disk.
5 Click Next, and then follow the on-screen prompts to create the boot package.
Adding network drivers to the Ghost Boot Wizard
The Ghost Boot Wizard includes drivers for over 130 network interface cards. If
your driver is not in the list, you can add it to the wizard so that it is set up the
next time that you need it.
To begin adding a network driver to the Ghost Boot Wizard
1 In the Network Interface window, click Add.
2 In the Template Type dialog box, select one of the following:
■ Packet Driver
■ NDIS2 Driver
Many manufacturers ship both drivers with their network cards so you have
a choice of which one to use.
3 Click OK.
You can then complete the details to add a packet driver or NDIS2 driver.
See “Adding packet drivers to the Ghost Boot Wizard” on page 279.
See “Adding NDIS2 drivers to the Ghost Boot Wizard” on page 280.
Adding packet drivers to the Ghost Boot Wizard
Packet drivers are usually DOS executables (with .com or .exe file extensions) that
load from the Autoexec.bat file before Symantec Ghost loads. Symantec Ghost
communicates directly with the packet driver to use the services provided by the
network card.
Creating boot packages with the Ghost Boot Wizard 279
Adding network drivers to the Ghost Boot Wizard
To add a packet driver to the Ghost Boot Wizard
1 In the Template Properties window, on the Packet Driver tab, in the Driver
Executable field, click Browse to locate the packet driver so that the Ghost
Boot Wizard can copy the file to the current template.
Packet drivers are usually included on the driver disk supplied with the
network card. If you are installing the packet driver from the original disks
that came with your network interface card, the packet driver should be in a
directory called Packet or Pktdrv. The driver date lets you check whether you
have the latest driver.
2 In the Parameters field, type the command-line parameters if the network
card requires them.
These parameters vary from driver to driver and are usually optional with
plug-and-play network cards. Consult the documentation that came with the
network card. This is often in the form of a Readme.txt file in the same
directory as the driver itself.
3 In the Mode drop-down list, click Select Automatically to let Ghost determine
the best multicasting mode based on the information in the packet driver.
If the Select Automatically mode does not work, try Receive Mode 5. If that
does not work, try Receive Mode 6.
4 Click OK to continue creating the boot package.
You can also add additional drivers or programs or customize the Autoexec.bat
and Config.sys files of the resulting boot package. If you are creating a floppy disk
set and you edit Autoexec.bat you should ensure that the same changes are made
to Autoexec.bat on both disks in the floppy disk set.
See “Customizing the template” on page 281.
Adding NDIS2 drivers to the Ghost Boot Wizard
NDIS2 drivers work with the Microsoft Network Client. Symantec Ghost also uses
them for GhostCasting. NDIS2 drivers are DOS drivers that load from the DOS
Config.sys file.
You can also to add additional drivers or programs or customize the Autoexec.bat
and Config.sys files of the resulting boot package. If you are creating a floppy disk
set and you edit Autoexec.bat, you should ensure that the same changes are made
to Autoexec.bat on both disks in the floppy disk set.
See “Customizing the template” on page 281.
Creating boot packages with the Ghost Boot Wizard
Adding network drivers to the Ghost Boot Wizard
280
To add an NDIS2 driver to the Ghost Boot Wizard
1 In the Template Properties window, on the NDIS Driver tab, click Setup.
2 Locate the NDIS2 driver.
In many cases Ghost can automatically determine the other parameters for
your network. When locating the directory that contains the driver, look for
a folder named Ndis or Ndis2. If you have a choice between DOS and OS2
folders, select DOS. The driver date lets you check whether you have the latest
driver.
3 Click OK.
If the setup fails to complete the driver properties, then complete the following
fields manually:
Filename Type the DOS file name for the NDIS2 driver.
Type the internal name of the driver.
The internal name of the driver is used when generating the
Protocol.ini configuration file and must always end with a $
character. Read the sample Protocol.ini file in the same directory
as the driver itself to find the internal driver name.
The internal name of the driver is often the DOS file name with
the file name extension replaced with a $. For example, the
internal name of Mydriver.dos is Mydriver$.
Driver Name
Type the parameters for the Protocol.ini configuration file.
If you use Setup to automatically fill in this page, you will see
the parameters that you need to adjust. For the majority of
plug-and-play cards, all of the parameters are optional, so you
can either accept the defaults or leave this field empty.
Parameters
4 In the Mode drop-down list, click Select Automatically to let Ghost determine
the best multicasting mode based on the information in the NDIS driver.
If the Select Automatically mode does not work, try Receive Mode 5. If that
does not work, try Receive Mode 6.
5 Click OK to continue creating the boot package.
Customizing the template
You may require additional drivers and programs in order to use the network
device attached to your computer. For example, many USB network devices must
load an extra driver for the USB port before the driver for the network device.
Creating boot packages with the Ghost Boot Wizard 281
Adding network drivers to the Ghost Boot Wizard
You can add files to the template and customize the Autoexec.bat and Config.sys
files of the resulting boot package. Usually these are either DOS drivers or
executable programs, but you can add any type of file. Files added to the template
appear in the list to the right of the button.
Note: If you are creating a floppy disk set and you edit Autoexec.bat, you should
ensure that the same changes are made to Autoexec.bat on both disks in the floppy
disk set.
If this template is used as a multicard template, then any additional files or
modifications are overridden by its settings.
To modify a template
1 In the Template Properties window, on the Advanced tab, do any of the
following:
■ Click New and select a file to add to the template.
■ Click Delete to delete the selected file from the list.
■ In the Autoexec.bat field, type any additional Autoexec.bat entries for the
driver.
The entries appear before any network-related commands, such as
Netbind.com or the packet driver executable.
■ In the Config.sys field, type any additional Config.sys entries for the driver.
The entries appear before any driver-related devices to ensure that the
enabling drivers load before the main network device drivers specified on
the network driver page.
2 Click OK to continue creating the boot package.
Adding command-line parameters to a boot package
You can add command-line parameters to a boot package to instruct Symantec
Ghost to perform certain actions.
Command-line parameters can be added while creating a Standard Boot Package,
Network Boot Package, CD/DVD Startup Package with Ghost, TCP/IP Network
Boot Image, or boot package in the Client Type window.
In the following example, the parameters instruct Symantec Ghost to connect to
the GhostCast session called test and restore the disk image to the first drive:
Creating boot packages with the Ghost Boot Wizard
Adding command-line parameters to a boot package
282
Table 11-2 Command parameters
Switch Description
-sure Removes the need to confirm the specified details.
Causes a restart immediately after the cloning
operation.
-rb
Used with the parameter src=@mctest and dst=1.
@mc indicates the GhostCast session name. In this
case, the session name is test.
The session name must match on the client and
server.
dst=1 refers to the destination being fixed disk 1.
-clone
In the following example, the parameters instruct Symantec Ghost to back up
your main disk to an image on another drive:
-clone,mode=create,src=1,dst=D:\backups\maindrv.gho
Table 11-3 Command parameters
Clone parameters Description
mode=create Creates an image file
Creating boot packages with the Ghost Boot Wizard 283
Adding command-line parameters to a boot package
Table 11-3 Command parameters (continued)
Clone parameters Description
src=1 Specifies drive 1 as the source drive
dst=D:\Backups\Maindrv.gho Saves the image to the file D:\Backups\Maindrv.gho
See “About Symantec Ghost switches” on page 467.
Providing MS-DOS
The Ghost Boot Wizard includes PC-DOS on boot packages. However, a boot
package that includes PC-DOS might not start all computers. When you create a
boot package, you can include MS-DOS instead of PC-DOS.
If you use MS-DOS, then you must provide MS-DOS files on the computer on which
you are creating the boot package. Using an MS-DOS system disk that was
formatted on a Windows 95/98 computer, you can install the MS-DOS files during
the creation of the boot package.
For more information, see the Knowledgebase articles at the following URLs:
■ How to create a Microsoft Client boot disk
■ How to create an MS-DOS system disk for Ghost
■ Drive mapping to Windows 2003 Server
To create an MS-DOS system disk on a Windows 95/98 computer
1 Insert a blank floppy disk into drive A of a Windows 95/98 computer.
2 on the Windows taskbar, click Start > Program Files > Windows Explorer.
3 Right-click drive A.
Warning: Do not right-click drive C.
4 Click Format.
5 Check Copy System Files.
6 Click Start to format the disk.
You can install or uninstall MS-DOS while you are creating a boot disk.
Creating boot packages with the Ghost Boot Wizard
Providing MS-DOS
284
To copy MS-DOS to your computer
1 Insert the formatted floppy disk into drive A of the computer on which the
Ghost Boot Wizard is running.
2 In the DOS Version window, click Get MS-DOS.
3 In the Get MS-DOS dialog box, do one of the following steps:
To get MS-DOS from a floppy Click From Floppy Disk, and select a floppy drive.
disk.
To get MS-DOS from a folder. Click From Directory.
4 Click OK.
To remove MS-DOS from your computer
1 In the DOS Version window, click Remove MS-DOS.
2 Click OK.
Installing MS-DOS Client files
If you are using the mapped network drive functionality and MS-DOS, you must
include the Microsoft DOS Client files. You must install the files on the computer
before you can include them on the boot package.
For more information, see the Knowledgebase articles at the following URLs:
■ How to create a Microsoft Client boot disk
■ How to create an MS-DOS system disk for Ghost
■ Drive mapping to Windows 2003 Server
The following files are required:
■ EMSBFR.EXE
■ LMHOSTS
■ NEMM.DOS
■ NET.EXE
■ NET.MSG
■ NETBIND.COM
■ NETH.MSG
■ NETWORKS
Creating boot packages with the Ghost Boot Wizard 285
Installing MS-DOS Client files
■ NMTSR.EXE
■ PROTMAN.DOS
■ PROTMAN.EXE
■ PROTOCOL
■ TCPDRV.DOS
■ TCPTSR.EXE
■ TCPUTILS.INI
■ TINYRFC.EXE
■ UMB.COM
■ IFSHLP.SYS
■ EMM386.EXE
■ HIMEM.SYS
■ WFWSYS.CFG
To install the Microsoft DOS Client files
1 In the DOS version window, click Get MS Client.
2 In the Browse for Folder dialog box, select the MS-DOS LAN Client files.
3 Click OK to continue creating a boot package.
Symantec Ghost support for multiple network
interface cards
The UNDI drivers support multiple network interface cards (NIC) in a computer.
If you have more than one NIC in your computer, and you do not use the UNDI
driver, then it is possible that Ghost might not select the correct card. If you do
not want to use the UNDI driver, then you should edit the Protocol.ini file to select
the correct card.
If Ghost does not select the correct card, you can edit the Protocol.ini file to specify
the correct settings to bind the network driver to the correct network card. You
must specify the physical location of the network card in the computer. The
information that you must include in the Protocol.ini file is specific to the driver
and to the network.
Note: The network driver must be a PCI network card.
Creating boot packages with the Ghost Boot Wizard
Symantec Ghost support for multiple network interface cards
286
Before you edit the Protocol.ini file, you need the following information:
You can obtain this information from the
manufacturer of your NIC. The manufacturer
might also require you to include additional
information in the Protocol.ini file. For
example, the manufacturer might require
you to place the keyword information in a
specific section of the Protocol.ini file.
Some manufacturers use the term device
instead of the word slot.
PCI Location Bus, Slot, and Function
keywords
You can obtain this information by checking
the client computer properties in the Ghost
Console.
See “To view Symantec Ghost Console client
computer properties” on page 95.
Symantec Ghost displays the PCI
information in decimal format. A
manufacturer might require that you use
this hexadecimal format in the Protocol.ini
file.
PCI bus number, slot number, and function
number
When you have the PCI information, you can edit the Protocol.ini file.
For example, a manufacturer provides the following keywords:
■ SLOT
■ BUSNO
■ FUNCTNO
The Symantec Ghost client dialog properties lists the following properties:
B:0 S:17 F:0
In this case, you would edit the Protocol.ini file as follows:
■ SLOT=17
■ BUSNO=0
■ FUNCTNO=0
Creating boot packages with the Ghost Boot Wizard 287
Symantec Ghost support for multiple network interface cards
Creating a DOS boot disk manually
There may be times when you want to create boot disks manually. For example,
you may wish to create a NetWare boot disk, add custom programs, or add batch
files.
To create a DOS boot disk manually
1 If the operating system is DOS/Win 98, insert a blank, formatted floppy disk
into drive A.
2 Type the following:
C:\> sys c: a:
3 Set up the packet driver interface.
For example, type the following command to copy the network interface card
packet driver file:
C:\> copy 3c5x9pd.com a:\
See “Setting up packet drivers” on page 289.
4 To copy Ghost.exe and Wattcp.cfg to the floppy disk, type the following:
C:\> copy progra~1\Symantec\ghost\ghost.exe a:\
C:\> copy progra~1\Symantec\ghost\wattcp.cfg a:\
Creating boot packages with the Ghost Boot Wizard
Creating a DOS boot disk manually
288
5 Edit the Wattcp.cfg file.
For example:
IP = 192.168.100.44
NETMASK = 255.255.255.0
The Wattcp.cfg file stores the TCP/IP stack configuration details and specifies
the IP address and subnet mask of the computer.
See your system administrator for IP and netmask values.
6 Edit the Autoexec.bat startup file.
For example:
3c5x9pd.com 0x60
ghost.exe
Add the command line for the packet drive to the Autoexec.bat file.
For more information, see the packet driver documentation.
Ensure that the same changes are made to Autoexec.bat on both disks in the
floppy disk set.
You can add additional command-line switches to the Ghost.exe command
to automate the cloning process.
See “About Symantec Ghost switches” on page 467.
Setting up packet drivers
There are several packet driver interface options as follows:
■ Network interface card-dependent packet driver.
See “To set up a network interface card-dependent packet driver” on page 290.
■ NDIS version 2.01 driver with packet driver shim supplied by Symantec Ghost.
NDIS version 3 or later drivers do not work with the Ghost client.
See “To set up an NDIS 2.01 network adapter driver with supplied packet driver
shim” on page 290.
■ Third-party network adapter driver and packet driver shim. These have not
been tested or documented with the GhostCasting feature. This includes
ODI-based packet driver shims such as Odipkt.com.
Packet drivers are easy to set up and require minimal configuration.
The NDIS driver setup is more complex. The selection of NDIS 2.01 and shim, or
a network interface card-specific packet driver depends on factors such as
availability, reliability, ease of use, and speed. By running a system test, you can
Creating boot packages with the Ghost Boot Wizard 289
Creating a DOS boot disk manually
choose the best alternative for your network interface card (that is, the specific
packet driver or the NDIS 2.01 driver and shim).
Note: Do not use the Network Client Administrator from Windows NT 4 or the
Microsoft Network Client Installation program to create a GhostCast boot package
as they are not compatible.
To set up a network interface card-dependent packet driver
1 Locate the packet driver for your network interface card.
Packet drivers are usually supplied on the installation disk included with a
network interface card or may be available on the manufacturer’s Web site.
2 Load the packet driver onto the computer.
The command-line arguments vary slightly from driver to driver as follows:
■ 3COM590 PCI network interface card packet driver:
A:\> 3c59xpd.com
■ 3COM509 ISA network interface card packet driver:
A:\> 3c5x9pd.com 0x60
■ NE2000 compatible using software interrupt 0x60 at IRQ10 and IObase
0x280:
A:\> ne2000pd.com 0x60 10 0x280
The syntax for the NE2000pd command is a typical example of an ISA
driver command line. You can find the IRQ and IO base address values
using the setup program included with the network interface card. The
software interrupt can be between 0x60—0x7f.
To set up an NDIS 2.01 network adapter driver with supplied packet driver shim
1 Locate the NDIS 2.01 driver for the network interface card.
NDIS (version 2.01) drivers are usually supplied on the installation disk
included with a network interface card and have a .dos file extension.
Alternatively, NDIS (version 2.01) drivers may be available on the network
interface card manufacturer’s Web site.
2 Copy and modify Protocol.ini, Config.sys, and Autoexec.bat.
Base configuration files ready for editing are included in the GhostCasting
installation files. Extract these configuration files and edit as shown. If you
are creating a floppy disk set and you edit Autoexec.bat, you should ensure
that the same changes are made to Autoexec.bat on both disks in the floppy
disk set.
Creating boot packages with the Ghost Boot Wizard
Creating a DOS boot disk manually
290
3 In the Ghost directory, copy the following files from the \ndis directory:
■ Protman.dos
■ Protman.exe
■ Netbind.com
■ Dis_pkt.dos
4 Restart the computer.
The packet driver interface should now be ready for Symantec Ghost to use.
Table 11-4 lists the files that your directory or floppy package should contain.
Table 11-4 Required files
System files Configuration files NDIS files
Command.com Config.sys Dis_pkt.dos
Msdos.sys (hidden) Autoexec.bat Netbind.com
Io.sys (hidden) Protocol.ini Protman.dos
Protman.exe
*.dos
Note the following:
■ Protman.exe is used during the NETBIND and is not needed in Autoexec.bat.
■ *.dos is the network interface card specific driver (for example, ELNK3.DOS).
Following is a sample Protocol.ini file:
[PROTMAN]
drivername = PROTMAN$
[PKTDRV]
drivername = PKTDRV$
bindings = PC_CARD
intvec = 0x60
chainvec = 0x66
[PC_CARD]
drivername = PNPND$
Change the [PC_CARD] module driver name to correspond to the NDIS driver in
use for your network interface card. For example, if you use a 3COM509 card then
change the driver name to:
Creating boot packages with the Ghost Boot Wizard 291
Creating a DOS boot disk manually
drivername = ELNK3$
Type any additional required options for the network interface card configuration
in the [PC_CARD] module. Refer to the documentation or the sample Protocol.ini
for the network interface card in use, if required. For example, the 3COM509 card
lets you optionally specify the IO Base address:
[PC_CARD]
drivername = ELNK3$
IOADDRESS = 0x300
Following is a sample Config.sys file:
device=protman.dos /I:\
device=dis_pkt.dos
device=pnpnd.dos
The /I: in the first line indicates the location of the Protocol.ini file and must be
present. For example, /I:\ specifies the root directory and /I:A:\NET specifies
A:\NET.
The last line refers to the driver for the network interface card. For example, if
you use a 3COM509, the last line of Config.sys should be replaced with:
device=ELNK3.DOS
Following is a sample Autoexec.bat file:
prompt $p$g
netbind
NETBIND binds the NDIS drivers together and installs the packet driver interface.
Supporting regional keyboards and character sets
You can customize boot disks and packages to support regional keyboards and
character sets by editing the Local.cfg file. The Local.cfg file does not support
languages that use double-byte character sets.
The Local.cfg file is one of the files that is required to support the Ghost Boot
Wizard. It is stored in one of the following locations:
\Documents and Settings\All Users\Application
Data\Symantec\Ghost\Template\Common
Windows XP
\Documents and Settings\All Users\Application
Data\Symantec\Ghost\Template\Common
Windows 2000
Creating boot packages with the Ghost Boot Wizard
Supporting regional keyboards and character sets
292
Files included in a Ghost package
The following files are required to run Ghost.exe and are included in a boot
package:
The Ghost executable that is run from DOS.
Note: Mapped Network Drive packages might not include
Ghost.exe.
Ghost.exe
PC-DOS is supplied for the purpose of creating Ghost boot
packages. The DOS files are installed automatically when
you create the boot package using the Ghost Boot Wizard.
DOS system files
This includes CD-R/RW drivers, network protocol files, or
network interface card (NIC) drivers, or any other files for
external storage access.
Note: For best performance , you should use the latest
version of the NIC driver. You might need to download the
driver from the manufacturer.
Any files and drivers
required to access the
selected hardware
Note: In versions previous to 8.0 of Symantec Ghost, MSCDEX was required to
read an image from a CD. If you created a bootable CD using any version of
Symantec Ghost you do not need to include MSCDEX in the boot package. If you
created a bootable CD with another utility, MSCDEX must be included.
When to include a network card driver
If the boot package includes network support, the Universal Packet Driver (UNDI
driver) enables detection of network cards in most computers without a specific
network card driver. If the boot package does not work on a computer, then a new
boot package must be created that uses the correct network card driver.
The UNDI driver can replace a specific driver in most of the following situations:
■ If the computer has been manufactured within the last two or three years
■ If the computer supports network booting using PXE (version 2.1)
Note: Symantec Ghost supports any version of PXE when booting a computer
over a network from a PXE server.
The UNDI drivers support multiple network interface cards (NIC) in a computer.
If you have more than one NIC in your computer, and you do not use the UNDI
Creating boot packages with the Ghost Boot Wizard 255
Files included in a Ghost package
driver, then it is possible that Ghost might not select the correct card. If you do
not want to use the UNDI driver, then you should edit the Protocol.ini file to select
the correct card.
See “Symantec Ghost support for multiple network interface cards ” on page 286.
The UNDI driver installation loads a driver from the option ROM of a network
card. If any one of the following is disabled in the BIOS, you must enable the option
in the BIOS before using the UNDI driver:
■ Option ROM
■ PXE
■ UNDI
Symantec provides a Universal Packet Driver, but to create a mapped network
boot package, you must provide a Universal NDIS Driver. You can download this
from the 3Com Site at the following URL:
http://support.3com.com/infodeli/tools/nic/mba.htm
When creating the mapped network boot package you are prompted for the location
of the Universal NDIS Driver.
When to include MS-DOS in a boot package
By default, Symantec Ghost includes PC-DOS in a Ghost boot package. However,
some computer models may not start from a Ghost boot package that contains
PC-DOS. If your computer does not start from a Ghost boot package, you should
create a new Ghost boot package from the Ghost Boot Wizard and include Windows
95/98 MS-DOS.
Before you create an MS-DOS Ghost boot package, you must provide Windows
95/98 MS-DOS for the computer that is running the Ghost Boot Wizard.
See “Providing MS-DOS” on page 284.
Opening the Ghost Boot Wizard
After you start the Ghost Boot Wizard, you can create boot packages.
To open the Ghost Boot Wizard
■ on the Windows taskbar, click Start > Programs > Symantec Ghost > Ghost
Boot Wizard.
Creating boot packages with the Ghost Boot Wizard
Opening the Ghost Boot Wizard
256
Selecting which boot package to create
You can include any of the following features in a boot package:
■ Support for CD-R/RW, DVD, LPT, USB, and FireWire
■ Network support for TCP/IP peer-to-peer connections and GhostCasting
■ Support for reading and writing an image to and from CD/DVD
■ Support for mapping network drives
■ An image of the Console Boot Partition.
■ RIS boot packages that support Microsoft Remote Installation Service (RIS)
with Symantec Ghost
■ TCP/IP network boot images that use 3Com DynamicAccess Boot Services to
allow access to Symantec Ghost without a boot disk
Table 11-1 provides information about the types of boot packages that you can
make and how they can be used.
Table 11-1 Boot package types
Intended use Ghost Boot Wizard options
You can use either of the following
options:
■ Standard Ghost Boot Package
See “Standard boot packages”
on page 259.
■ Network Boot Package
See “Boot packages with network
support” on page 264.
Local use of Ghost.exe:
■ Disk-to-disk
■ Partition-to-partition
■ Disk or partition to and from local JAZ or ZIP
drive
Standard Ghost Boot Package
See “Standard boot packages”
on page 259.
■ Clone, back up, or restore over peer-to-peer
connection between two computers using LPT,
FireWire, or USB cable.
Creating boot packages with the Ghost Boot Wizard 257
Selecting which boot package to create
Table 11-1 Boot package types (continued)
Intended use Ghost Boot Wizard options
You can use either of the following
options:
■ Network Boot Package
See “Boot packages with network
support” on page 264.
■ Drive Mapping Boot Package
See “Creating a boot package that
supports mapped network drives”
on page 265.
Note: A Drive Mapping Boot Package
supports NDIS drivers but does not
support using packet drivers. To use
Ghost.exe with network support using
packet drivers, you should create a
Network Boot Package.
■ Clone, back up, or restore over TCP/IP
peer-to-peer connection with network support
between two computers.
Standard Ghost Boot Package
See “Standard boot packages”
on page 259.
■ Back up or restore a computer onto an image
file on a CD/DVD that is on a CD/DVD writer
supported by Symantec Ghost.
CD/DVD Startup Boot Package with
Ghost
See “Boot packages with CD and DVD
support” on page 268.
■ Restore a computer from a Ghost image file
on a CD that is on a CD-R/RW drive not
supported by Symantec Ghost. The image file
was not stored on the CD using Symantec
Ghost. Contains generic CD drivers.
■ Access files other than a Ghost image file on
a CD.
Drive Mapping Boot Package
See “Creating a boot package that
supports mapped network drives”
on page 265.
■ Map a drive on a workstation to a shared
resource on a server and use Symantec Ghost
to clone, back up, or restore.
Console Boot Partition
See “Creating a boot image containing
the Console boot partition” on page 269.
■ Install the Console boot partition on a client
computer.
TCP/IP Network Boot Image
See “Starting client computers in
Ghost.exe from the network” on page 273.
■ Start Ghost.exe on a client computer from the
network (without a boot disk).
Creating boot packages with the Ghost Boot Wizard
Selecting which boot package to create
258
Table 11-1 Boot package types (continued)
Intended use Ghost Boot Wizard options
TCP/IP Network Ghost Client Boot
Image
See “Starting client computers from the
network to connect with the Symantec
Ghost Console” on page 274.
■ Start a client computer from the network to
connect to the Symantec Ghost Console.
Microsoft RIS Boot Option
See “Boot packages that support
Remote Installation Service (RIS)”
on page 271.
■ Create an entry in the RIS menu on a client
computer to start the computer from the
network.
Creating boot packages
After you have decided which boot which boot package to create you can create
it.
Standard boot packages
The Ghost Boot Wizard creates a boot package that does the following:
■ Runs Ghost.exe for local operations.
■ Writes Ghost images directly to media on a CD/DVD writer supported by
Symantec Ghost. The media must be supported by the CD/DVD writer.
■ Runs Ghost.exe on two computers that are connected by either an LPT or USB
cable.
■ Runs Ghost.exe to back up to or restore from an external device that is
connected by USB or FireWire.
To create standard boot package
1 In the Ghost Boot Wizard window, click Standard Ghost Boot Package.
2 Click Next.
Creating boot packages with the Ghost Boot Wizard 259
Creating boot packages
3 Select one or more of the following:
USB support To add support for USB peer-to-peer to the boot package.
To set the USB peer-to-peer drivers.
See “Setting the USB peer-to-peer drivers” on page 261.
Advanced
To add support for LPT peer-to-peer to the boot package.
See “Setting the LPT port or mode” on page 261.
LPT support
Advanced To change the LPT mode or port.
To add Adaptec ASPI drivers to the boot package.
These drivers are required to write an image directly to a SCSI
CD-R that is supported by Symantec Ghost.
Include Adaptec
ASPI drivers
4 Select one of the following:
■ Use PC-DOS
■ Use MS-DOS
See “Providing MS-DOS” on page 284.
5 Click Next.
6 In the Ghost.exe field, type the correct path if the executable has been moved
or you want to use a different version of Symantec Ghost.
The default path to Ghost.exe appears in the Ghost.exe field.
7 In the Parameters field, type any required command-line parameters.
See “Adding command-line parameters to a boot package” on page 282.
8 Click Next.
9 If you want to move control of USB devices from the BIOS to Ghost, check
Override BIOS USB control.
This option is unavailable if you have previously included USB support in the
boot package.
Do not select this option if you are creating a bootable USB device.
10 If you want to move control of FireWire devices from the BIOS to Ghost, check
Override BIOS FireWire control.
11 Click Next.
Creating boot packages with the Ghost Boot Wizard
Creating boot packages
260
12 Select a destination for the boot package.
See “Selecting a destination drive” on page 262.
13 Review the boot package details and click Next to start creating the boot
package.
Follow the prompts to create a boot package.
Setting the USB peer-to-peer drivers
You can select USB peer-to-peer drivers to include in the boot package. In most
cases, you do not need to change the default driver setting. If you have problems
connecting using peer-to-peer, then select another option and try again.
To set USB peer-to-peer drivers
1 In the Load USB drivers dialog box, select one of the following:
Includes All drivers all USB peer-to-peer drivers in the boot package
UHCI driver Includes only UHCI drivers in the boot package
OHCI driver Includes only OHCI drivers in the boot package
2 Click OK.
Setting the LPT port or mode
The default mode for an LPT connection is ECP/EPP. If you are having problems
with your LPT connection, set the mode to Bidirectional 8bit or Bidirectional 4bit.
The next time that you create a boot package, the mode is reset to the default,
ECP/EPP High Speed.
If you have multiple parallel ports and want to connect using a port other than
the default LPT1, use the LPT port option to specify the port into which your cable
is plugged.
To set the LPT port or mode
1 In the LPT configuration dialog box, under Mode, select one of the following:
■ ECP/EPP High Speed
■ Bidirectional 8bit
■ Bidirectional 4bit
2 Under Port, select one of the following:
■ Default
Creating boot packages with the Ghost Boot Wizard 261
Creating boot packages
■ LPT1
■ LPT2
■ LPT3
3 Click OK.
Selecting a destination drive
You can select one of the following destinations for the boot package:
This option is unavailable if you are creating a Drive Mapping Boot
Package that includes Ghost.exe.
Floppy disk set
This option lets you create an ISO image that you can write to a CD
or DVD using third-party software.
This option is unavailable if you use a Multicard template.
ISO image
Symantec fully supports USB flash drives as a removable device;
however, other devices also work with this options. The client
computer must support starting from the device and be configured
correctly. For example, the BIOS must support the option to start from
the device.
For a list of supported devices, see the Knowledgebase article at the
following URL:
http://service1.symantec.com/SUPPORT/ghost.nsf/docid/2006081110304125
A 2 GB partition is created on the device, and any remaining space on
the device becomes unavailable. The device is reformatted, and any
existing data is overwritten.
Removable and
unremovable
devices
Warning: All information on the selected device is deleted. The device is
automatically formatted before use.
Creating boot packages with the Ghost Boot Wizard
Creating boot packages
262
To select a package type
1 In the Destination Drive window, select one of the following:
Format floppy disk Lets you create a floppy disk boot set
set
Create ISO image Lets you create an ISO image to write to a CD/DVD
Lets you create a boot package on a removable or unremovable
device
Format Disk
2 Select one of the following destination options for the selected package type:
Format floppy disk See “To set floppy disk options” on page 263.
set
Create ISO image See “To set ISO image options” on page 263.
Format Disk See “To set removable or unremovable disk options” on page 264.
To set floppy disk options
1 In the Destination Drive window, in the Floppy Disk Drive field, select the
appropriate drive letter.
2 In the Number of disk sets to create field, select the number that you want
to create.
3 Ensure that Format disk(s) First is checked to format the disks before disk
creation.
Ensure that this option is checked unless you are creating a custom boot disk
with custom system files. If this option is unchecked, the boot disk is not
bootable.
4 Ensure that Quick Format is checked to perform a quick format.
5 Click Next.
To set ISO image options
1 In the Destination Drive window, click Browse and select a location and file
name for the image file.
2 Click Next.
Creating boot packages with the Ghost Boot Wizard 263
Creating boot packages
To set removable or unremovable disk options
1 In the Destination Drive window, under Available Devices, click the down
arrow, and select one of the devices listed.
2 If you want to display unremovable devices, uncheck Show only removable
devices.
3 If you want to add support for creating a bootable CD/DVD, click Support for
creating bootable CD/DVDs.
This option adds an image of a bootable floppy disk to the boot package. If
you are using Ghost to write an image directly to a CD or DVD, this option
adds support for making the CD or DVD bootable.
4 Click Next.
Boot packages with network support
The Ghost Boot Wizard helps you create boot packages that provide network
support for GhostCasting and TCP/IP peer-to-peer connections.
To create a boot package with network support
1 In the Ghost Boot Wizard window, click Network Boot Package.
2 Click Next.
3 In the Network Interface Card window, do one of the following:
■ Select the Universal Packet Driver, and then click Next.
See “When to include a network card driver” on page 255.
■ Click Show all drivers, select or add a network driver, and then click Next.
See “Selecting and adding a network driver” on page 276.
4 Select one of the following:
■ Use PC-DOS
■ Use MS-DOS
See “Providing MS-DOS” on page 284.
5 Click Next.
6 Click Symantec Ghost to create a boot package for the client that loads
Symantec Ghost. You can connect to a running GhostCast Server to transfer
image files to and from the client.
The default path to Ghost.exe is entered in the Ghost.exe field. If the
executable has been moved, or you want to use a different version of Ghost.exe,
type the correct path.
Creating boot packages with the Ghost Boot Wizard
Creating boot packages
264
7 In the Parameters field, type any required command-line parameters.
See “Adding command-line parameters to a boot package” on page 282.
8 Click Next.
9 If you want to move control of USB devices from the BIOS to Ghost, check
Override BIOS USB control.
This option is unavailable if you have previously included USB support in the
boot package.
Do not select this option if you are creating a bootable USB device.
10 If you want to move control of FireWire devices from the BIOS to Ghost, check
Override BIOS FireWire control.
11 Click Next.
12 Do one of the following:
■ Click DHCP will assign the IP settings if your network contains a DHCP
server.
■ Click The IP settings will be statically defined and complete the fields
below this option if your network does not contain a DHCP server.
If you create more than one boot package, then the static IP address
incrementally increases as each boot package is created.
13 If you want to alter the number of router hops then select the correct number
in Router Hops.
This specifies how many routers the client searches across when attempting
to find the Multicast Server. The default value of 16 lets Ghost find the server
as long as it is not more than 16 router hops away. This is sufficient for most
networks.
14 Click Next.
15 Select a destination for the boot package.
See “Selecting a destination drive” on page 262.
16 Review the boot package details and click Next to start creating the boot
package.
Follow the prompts to create a boot package.
Creating a boot package that supports mapped network drives
You can use the Ghost Boot Wizard to create boot packages that map a drive letter
to a shared resource on a network server. This drive mapping lets you access a
network drive from Ghost.exe.
Creating boot packages with the Ghost Boot Wizard 265
Creating boot packages
You can choose to include Ghost.exe in the boot package. If you do not include
Ghost.exe, you must run Ghost from the network drive. If you include Ghost.exe
in the boot package, you cannot create a boot package on a floppy disk set. You
can save the package to a USB flash drive or an to an ISO image.
Note: A Drive Mapping Boot Package supports NDIS drivers but does not support
using packet drivers. If you want to run Ghost.exe with network support and you
want to use packet drivers, you should create a Network Boot Package.
Note: If you do not run Ghost.exe from the A drive, then you must reset the
environment variable WATTCP to provide the location of the Wattcp.cfg file.
See “To reset the environment variable to the correct location of Wattcp.cfg”
on page 326.
To create a boot package that supports mapped network drives
1 In the Ghost Boot Wizard window, click Drive Mapping Boot Package.
2 Click Next.
3 In the Network Interface Card window, do one of the following:
■ In the driver list, double-click the Universal NDIS Driver, browse to the
location of the Universal NDIS Driver files, and then click OK.
See “When to include a network card driver” on page 255.
■ In the driver list, select or add a network driver, and then click Next.
See “Selecting and adding a network driver” on page 276.
4 Select one of the following:
■ Use PC-DOS
■ Use MS-DOS
See “Providing MS-DOS” on page 284.
5 Click Get MS Client and browse to the MS-DOS Client files to include if you
are using MS-DOS.
If you are using MS-DOS, you must include the Microsoft DOS Client files.
You must install the files on the Ghost Boot Wizard computer before you can
include them in the boot package.
See “Installing MS-DOS Client files” on page 285.
6 Click Next.
Creating boot packages with the Ghost Boot Wizard
Creating boot packages
266
7 In the Client type dialog box, check Do not include any Ghost executables if
you do not want to include Ghost.exe in the boot package.
If you do not include Ghost.exe in the package, you must run Ghost from a
network drive. If you do not include Ghost.exe in the package, then the
remaining Client Type boxes are unavailable.
8 Click Symantec Ghost to create a boot package for the client that loads
Symantec Ghost. You can connect to a GhostCast Server to transfer image
files to and from the client.
The default path to Ghost.exe is entered in the Ghost.exe field. If the
executable has been moved, or you want to use a different version of Ghost.exe,
type the correct path.
9 In the Parameters field, type any required command-line parameters.
See “Adding command-line parameters to a boot package” on page 282.
10 Click Next.
11 If you want to move control of USB devices from the BIOS to Ghost, check
Override BIOS USB control.
This option is unavailable if you have previously included USB support in the
boot package or if you have selected not to include Ghost.exe in the boot
package.
Do not select this option if you are creating a bootable USB device.
12 If you want to move control of FireWire devices from the BIOS to Ghost, check
Override BIOS FireWire control.
This option is unavailable if you have selected not to include Ghost.exe in the
boot package.
13 Click Next.
14 In the Client Computer Name field, type the name of the client computer.
This specifies the name of the computer after it starts from the package and
does not have to be the same name given to the computer in Windows. If you
create more than one package, a number is added to the computer name so
that the names for subsequent packages are unique.
15 In the User Name field, type the user name that the boot package will use to
log on to the network.
This user must exist on the network and have sufficient access rights to the
mapped network drive, files, and directories that you want to use.
16 In the Domain field, type the domain to which the user belongs.
Creating boot packages with the Ghost Boot Wizard 267
Creating boot packages
17 In the Drive Letter field, select a drive letter to access a network share through
a mapped drive.
Select a drive letter greater than any existing drive letter.
18 If you want to prevent the boot package from mapping a drive when the
computer starts, click None.
In this case, map a drive from the DOS prompt after the computer has started.
19 In the Maps To field, type the complete UNC path to the network share.
For example, to access a shared folder named Ghost on a computer named
Boss, the UNC path is \\Boss\Ghost.
20 Click Next.
21 Do one of the following:
DHCP will assign the IP If your network contains a DHCP server
settings
Complete the fields below this option if your network
does not contain a DHCP server. Your network
administrator can provide the values for these fields.
The IP settings will be
statically defined
22 Click Next.
23 Select a destination for the boot package.
If you have selected to include Ghost.exe in the boot package then you cannot
create a floppy disk set.
See “Selecting a destination drive” on page 262.
24 Review the boot package details and click Next to start creating the boot
package.
Follow the prompts to create a boot package.
Boot packages with CD and DVD support
A boot package with CD/DVD support lets you access images and other files stored
on CD-R/RW and DVD drives that are not supported by Symantec Ghost.
This kind of package also contains the DOS system files and Ghost.exe.
To create a boot package with CD-ROM and DVD support
1 In the Ghost Boot Wizard window, click CD/DVD Startup Package with Ghost.
2 Click Next.
Creating boot packages with the Ghost Boot Wizard
Creating boot packages
268
3 Select one of the following:
■ Use PC-DOS
■ Use MS-DOS
See “Providing MS-DOS” on page 284.
4 Click Next.
5 In the Ghost.exe field, type the correct path if the executable has been moved
or you want to use a different version of Ghost.exe.
The default path to the Ghost.exe appears in the Ghost.exe field.
6 In the Parameters field, type any required command-line parameters.
See “Adding command-line parameters to a boot package” on page 282.
7 Click Next.
8 If you want to move control of USB devices from the BIOS to Ghost, check
Override BIOS USB control.
Do not select this option if you are creating a bootable USB device.
9 If you want to move control of FireWire devices from the BIOS to Ghost, check
Override BIOS FireWire control.
10 Click Next.
11 Select a destination for the boot package.
See “Selecting a destination drive” on page 262.
12 Review the boot package details and click Next to start creating the boot
package.
Follow the prompts to create a boot package.
Creating a boot image containing the Console boot partition
You can create an image that contains the Console boot partition. Install this
image on client computers to allow remote control by the Console.
See “Installing the Console client” on page 58.
To create a boot image that contains a Console boot partition
1 In the Ghost Boot Wizard window, click Console Boot Partition.
2 Click Next.
3 In the Network Interface Card window, do one of the following:
■ Select the Universal Packet Driver and click Next.
See “When to include a network card driver” on page 255.
Creating boot packages with the Ghost Boot Wizard 269
Creating boot packages
■ Click Show all drivers, select or add a network driver and then click Next.
See “Selecting and adding a network driver” on page 276.
4 Select one of the following:
■ Use PC-DOS
■ Use MS-DOS
See “Providing MS-DOS” on page 284.
5 Click Next.
6 Type the correct path in the Ghost.exe field if the executable has been moved,
or you want to use a different version of Ghost.exe.
The default path to Ghost.exe appears in the Ghost.exe field.
7 Type the correct path in the Ngctdos.exe field if the executable has been
moved, or you want to use a different version.
The default path to the Ghost DOS client executable appears in the Ngctdos.exe
field.
8 Type the correct path in the Ghstwalk.exe field if the executable has been
moved, or you want to use a different version.
The default path to the Ghost Walker executable is entered in the Ghstwalk.exe
field.
9 In the Machine Group field, type the computer group folder, if required.
When a Console Client is first discovered on the network, the Console creates
an icon for it in the Machine Group section of the Default folder. When DOS
Console Client computers are discovered, they are identified by Adapter
Address only. Specifying a group folder makes identification of the computer
easier.
10 Click Next.
11 Do one of the following:
DHCP will assign the IP If your network contains a DHCP server
settings
Complete the fields below this option if your network
does not contain a DHCP server. Your network
administrator can provide the values for these fields.
The IP settings will be
statically defined
Creating boot packages with the Ghost Boot Wizard
Creating boot packages
270
12 If you want to alter the number of router hops then select the correct number
in Router Hops.
This specifies how many routers the client searches across when attempting
to find the Multicast Server. The default value of 16 lets Ghost find the server
as long as it is not more than 16 router hops away. This is sufficient for most
networks.
13 Click Next.
14 In the Image File field, type a name for the image file.
15 In the Description field, type a description for the image file.
16 To execute creation of the image file, click Next.
Boot packages that support Remote Installation Service (RIS)
Ghost Boot Wizard Remote Installation Service (RIS) leverages the Preboot
Execution Environment (PXE) feature of PC-98 specified computers to provide a
remote installation service for Windows 2000. Symantec Ghost provides a cloning
solution suitable for deployment or migration of any computer operating system
with specific support for Microsoft Windows. Symantec Ghost also works with
Windows systems prepared with the Microsoft SysPrep tool.
You can create a RIS boot package in the Symantec Ghost Boot Wizard only when
running on a Windows 2000/2003/XP server with RIS installed. An entry for the
boot package appears in the RIS menu.
Note: This option only appears if Microsoft Remote Installation Service is installed
on your computer.
To create a boot package that supports RIS
1 In the Ghost Boot Wizard window, click Microsoft RIS Boot Option.
2 Select the generic PXE packet driver template.
3 Click Next.
4 Select one of the following:
■ Use PC-DOS
■ Use MS-DOS
See “Providing MS-DOS” on page 284.
5 Click Next.
Creating boot packages with the Ghost Boot Wizard 271
Creating boot packages
6 Click Symantec Ghost to create a boot package that loads Symantec Ghost.
You can connect to a running GhostCast Server to transfer image files to and
from the client.
The default path to Ghost.exe is entered in the Ghost.exe field. If the
executable has been moved, or you want to use a different version of Ghost.exe,
type the correct path.
7 In the Parameters field, type any required command-line parameters.
See “Adding command-line parameters to a boot package” on page 282.
8 Click Next.
9 If you want to move control of USB devices from the BIOS to Ghost, check
Override BIOS USB control.
Do not select this option if you are creating a bootable USB device.
10 If you want to move control of FireWire devices from the BIOS to Ghost, check
Override BIOS FireWire control.
11 Click Next.
12 Do one of the following:
DHCP will assign the IP If your network contains a DHCP server
settings
Complete the fields below this option if your network
does not contain a DHCP server. Your network
administrator can provide the values for these fields.
The IP settings will be
statically defined
13 If you want to alter the number of router hops then select the correct number
in Router Hops.
This specifies how many routers the client searches across when attempting
to find the Multicast Server. The default value of 16 lets Ghost find the server
as long as it is not more than 16 router hops away. This is sufficient for most
networks.
14 Click Next.
15 In the RIS Boot Menu Name field, type the name that will appear on the RIS
Boot menu.
When you select this menu item, the client computer starts from the network
card.
Creating boot packages with the Ghost Boot Wizard
Creating boot packages
272
16 In the RIS Boot Description field, type a description for the boot package.
This text appears as a help message when the menu option is selected.
In the RIS Boot directory field, the name of the directory under the main RIS
tree in which the boot package is installed is displayed.
The contents of this field are generated from the text you type for the RIS
menu name. You should not change the text in this field from the default.
17 Click Next.
18 Select a language if there is more than one.
19 Click Next.
20 Review the boot package details and click Next to start creating the image
file.
Starting client computers in Ghost.exe from the network
You can create an image file that lets you start client computers in Ghost.exe,
from the network, using 3Com DynamicAccess Boot Services software.
To create an image file to start client computers from the network
1 In the Ghost Boot Wizard window, click TCP/IP Network Boot Image.
2 Click Next.
3 In the Network Interface Card window, do one of the following:
■ Select the Universal Packet Driver, and click Next.
See “When to include a network card driver” on page 255.
■ Click Show all drivers, select or add a network driver, and then click Next.
See “Selecting and adding a network driver” on page 276.
4 Select one of the following:
■ Use PC-DOS
■ Use MS-DOS
See “Providing MS-DOS” on page 284.
5 Click Next.
6 Click Symantec Ghost to include the Ghost client in the boot package.
The default path to Ghost.exe is entered in the Ghost.exe field. If the
executable has been moved, or you want to use a different version of Ghost.exe,
type the correct path.
Creating boot packages with the Ghost Boot Wizard 273
Creating boot packages
7 In the Parameters field, type any required command-line parameters.
See “Adding command-line parameters to a boot package” on page 282.
8 Click Next.
9 If you want to move control of USB devices from the BIOS to Ghost, check
Override BIOS USB control.
Do not select this option if you are creating a bootable USB device.
10 If you want to move control of FireWire devices from the BIOS to Ghost, check
Override BIOS FireWire control.
11 Click Next.
12 Do one of the following:
DHCP will assign the IP If your network contains a DHCP server
settings
Complete the fields below this option if your network
does not contain a DHCP server. Your network
administrator can provide the values for these fields.
The IP settings will be
statically defined
13 If you want to alter the number of router hops then select the correct number
in Router Hops.
This specifies how many routers the client searches across when attempting
to find the Multicast Server. The default value of 16 lets Ghost find the server
as long as it is not more than 16 router hops away. This is sufficient for most
networks.
14 Click Next.
15 In the Image File field, type a file name for the image file.
This image can be used with any BOOTP/TFTP server.
16 Click Next.
17 Review the boot package details and click Next to start creating the image
file.
Starting client computers from the network to connect with the
Symantec Ghost Console
You can create an image file that lets you start client computers from the network
and connect to the Symantec Ghost Console, using 3Com DynamicAccess Boot
Services software.
Creating boot packages with the Ghost Boot Wizard
Creating boot packages
274
To create an image file to start client computers from the network
1 In the Ghost Boot Wizard window, click TCP/IP Network Ghost Client Boot
Image.
2 Click Next.
3 In the Network Interface Card window, do one of the following:
■ Select the Universal Packet Driver, and click Next.
See “When to include a network card driver” on page 255.
■ Click Show all drivers, select or add a network driver, and then click Next.
See “Selecting and adding a network driver” on page 276.
4 Select one of the following:
■ Use PC-DOS
■ Use MS-DOS
See “Providing MS-DOS” on page 284.
5 Click Next.
6 Type the correct path in the Ghost.exe field if the executable has been moved,
or you want to use a different version of Ghost.exe.
The default path to Ghost.exe appears in the Ghost.exe field.
7 Type the correct path in the Ngctdos.exe field if the executable has been
moved, or you want to use a different version.
The default path to the Ghost DOS client executable appears in the Ngctdos.exe
field.
8 Type the correct path in the Ghstwalk.exe field if the executable has been
moved, or you want to use a different version.
The default path to the Ghost Walker executable is entered in the Ghstwalk.exe
field.
9 In the Machine Group field, type the computer group folder, if required.
When a Console Client is first discovered on the network, the Console creates
an icon for it in the Machine Group section of the Default folder. When DOS
Console Client computers are discovered, they are identified by Adapter
Address only. Specifying a group folder makes identification of the computer
easier.
10 Click Next.
Creating boot packages with the Ghost Boot Wizard 275
Creating boot packages
11 Do one of the following:
DHCP will assign the IP If your network contains a DHCP server
settings
Complete the fields below this option if your network
does not contain a DHCP server. Your network
administrator can provide the values for these fields.
The IP settings will be
statically defined
12 If you want to alter the number of router hops then select the correct number
in Router Hops.
This specifies how many routers the client searches across when attempting
to find the Multicast Server. The default value of 16 lets Ghost find the server
as long as it is not more than 16 router hops away. This is sufficient for most
networks.
13 Click Next.
14 In the Image File field, type a file name for the image file.
This image can be used with any BOOTP/TFTP server.
15 Click Next.
16 Review the boot package details and click Next to start creating the image
file.
Selecting and adding a network driver
If the Universal Network Driver cannot access the network interface card installed
in the target computer then you must either select or add a driver.
Unless you use the multicard template, you must create a boot package for each
network card.
To select or add a network driver
■ In the Network Interface Card window, do one of the following:
■ Select the network driver for the make and model of the network card
installed on the client computer.
See “Selecting a template” on page 277.
■ If the correct driver is not in the list, add the driver.
See “Adding network drivers to the Ghost Boot Wizard” on page 279.
You can add more than one driver to the boot package.
See “Creating a multicard template” on page 278.
Creating boot packages with the Ghost Boot Wizard
Selecting and adding a network driver
276
Selecting a template
For the boot package to work correctly, it is important that you select the correct
template. When you create a boot package for client computers, the template that
you select must be suitable for the network cards installed in the computers that
are to start from the package. You can use the Ghost Console to check the client
computer's network interface card in the Ghost Console.
See “Viewing Symantec Ghost Console resource properties” on page 84.
If the client computer is not installed with the Console client, then you can find
the name of the driver from Network Properties within Windows. This must be
done on the client computer for which you are preparing the boot package. The
name of the network interface card as shown in Windows may not exactly match
the name of the correct template in the Ghost Boot Wizard. For example, Windows
might list the card as 3Com Fast EtherLink XL 10/100Mb TX Ethernet NIC
(3C905B-TX). In this case, 3C905B-TX is the model number of the card. Therefore,
you can use the Ghost Boot Wizard template that is named 3COM 3C90X. This
template works for all 3C90- cards.
In some cases, you might have a choice between an NDIS2 driver and a packet
driver version of the same template. Both templates should work, but you might
find that one gives better performance. You can experiment to determine which
one works better.
It is possible that there is no existing template in the Ghost Boot Wizard that is
suitable for the network interface card installed in your computer. In this case,
obtain the DOS drivers for the network interface card either from the disk supplied
with the card or from the manufacturer’s Web site, and add a new template to the
Ghost Boot Wizard.
See “Adding network drivers to the Ghost Boot Wizard” on page 279.
If you have different network interface cards installed in client computers, then
you may be able to use the multicard template to create a single boot package that
works on each of your computers without modification.
To determine which network interface card is installed on a Windows 98 computer
1 on the Windows taskbar, click Start > Settings > Control Panel.
2 Double-click System.
3 Click Device Manager.
4 Expand Network Adapter.
The make and model of the installed network interface card are listed.
Creating boot packages with the Ghost Boot Wizard 277
Selecting a template
To determine which network interface card is installed on a Windows NT 4 computer
1 on the Windows taskbar, click Start > Settings > Control Panel.
2 Double-click Network.
The make and model of the installed network interface card are listed on the
Adapters tab.
To determine which network interface card is installed on a Windows 2000 computer
1 on the Windows taskbar, click Start > Settings > Control Panel.
2 Double-click System.
3 on the Hardware tab, click Device Manager.
4 Expand Network adapters.
The make and model of the installed network interface card are listed.
To determine which network interface card is installed on a Windows XP computer
1 on the Windows taskbar, click Start > Control Panel > System.
2 on the Hardware tab, click Device Manager.
3 Expand Network adapters.
The make and model of the installed network interface card are listed.
Creating a multicard template
You can use multicard templates to create a boot package containing several
NDIS2 drivers. When the computer starts from the boot package, a special
multicard driver checks the computer’s hardware to see if any of the NDIS2 drivers
can be used to access the installed network card.
Multicard templates are useful because several makes and models of network
cards are often used in a single LAN. You can create a single boot package for use
with all of your computers without modification.
Note: Multicard templates are not supported for ISO images.
Refer to the Software License Agreement for use restrictions.
Creating boot packages with the Ghost Boot Wizard
Creating a multicard template
278
To create a multicard template
1 In the Network Interface Card window, ensure that Show All Drivers is
checked.
The Network Interface Card window appears when you create a boot package
that requires a NIC. It is the second window in the Ghost Boot Wizard.
2 Click Multicard Template.
3 Click Next.
4 In the list of NDIS2 drivers, select the required drivers.
If you create a floppy disk set you should select no more than four or five
drivers. The space is limited on a floppy disk.
5 Click Next, and then follow the on-screen prompts to create the boot package.
Adding network drivers to the Ghost Boot Wizard
The Ghost Boot Wizard includes drivers for over 130 network interface cards. If
your driver is not in the list, you can add it to the wizard so that it is set up the
next time that you need it.
To begin adding a network driver to the Ghost Boot Wizard
1 In the Network Interface window, click Add.
2 In the Template Type dialog box, select one of the following:
■ Packet Driver
■ NDIS2 Driver
Many manufacturers ship both drivers with their network cards so you have
a choice of which one to use.
3 Click OK.
You can then complete the details to add a packet driver or NDIS2 driver.
See “Adding packet drivers to the Ghost Boot Wizard” on page 279.
See “Adding NDIS2 drivers to the Ghost Boot Wizard” on page 280.
Adding packet drivers to the Ghost Boot Wizard
Packet drivers are usually DOS executables (with .com or .exe file extensions) that
load from the Autoexec.bat file before Symantec Ghost loads. Symantec Ghost
communicates directly with the packet driver to use the services provided by the
network card.
Creating boot packages with the Ghost Boot Wizard 279
Adding network drivers to the Ghost Boot Wizard
To add a packet driver to the Ghost Boot Wizard
1 In the Template Properties window, on the Packet Driver tab, in the Driver
Executable field, click Browse to locate the packet driver so that the Ghost
Boot Wizard can copy the file to the current template.
Packet drivers are usually included on the driver disk supplied with the
network card. If you are installing the packet driver from the original disks
that came with your network interface card, the packet driver should be in a
directory called Packet or Pktdrv. The driver date lets you check whether you
have the latest driver.
2 In the Parameters field, type the command-line parameters if the network
card requires them.
These parameters vary from driver to driver and are usually optional with
plug-and-play network cards. Consult the documentation that came with the
network card. This is often in the form of a Readme.txt file in the same
directory as the driver itself.
3 In the Mode drop-down list, click Select Automatically to let Ghost determine
the best multicasting mode based on the information in the packet driver.
If the Select Automatically mode does not work, try Receive Mode 5. If that
does not work, try Receive Mode 6.
4 Click OK to continue creating the boot package.
You can also add additional drivers or programs or customize the Autoexec.bat
and Config.sys files of the resulting boot package. If you are creating a floppy disk
set and you edit Autoexec.bat you should ensure that the same changes are made
to Autoexec.bat on both disks in the floppy disk set.
See “Customizing the template” on page 281.
Adding NDIS2 drivers to the Ghost Boot Wizard
NDIS2 drivers work with the Microsoft Network Client. Symantec Ghost also uses
them for GhostCasting. NDIS2 drivers are DOS drivers that load from the DOS
Config.sys file.
You can also to add additional drivers or programs or customize the Autoexec.bat
and Config.sys files of the resulting boot package. If you are creating a floppy disk
set and you edit Autoexec.bat, you should ensure that the same changes are made
to Autoexec.bat on both disks in the floppy disk set.
See “Customizing the template” on page 281.
Creating boot packages with the Ghost Boot Wizard
Adding network drivers to the Ghost Boot Wizard
280
To add an NDIS2 driver to the Ghost Boot Wizard
1 In the Template Properties window, on the NDIS Driver tab, click Setup.
2 Locate the NDIS2 driver.
In many cases Ghost can automatically determine the other parameters for
your network. When locating the directory that contains the driver, look for
a folder named Ndis or Ndis2. If you have a choice between DOS and OS2
folders, select DOS. The driver date lets you check whether you have the latest
driver.
3 Click OK.
If the setup fails to complete the driver properties, then complete the following
fields manually:
Filename Type the DOS file name for the NDIS2 driver.
Type the internal name of the driver.
The internal name of the driver is used when generating the
Protocol.ini configuration file and must always end with a $
character. Read the sample Protocol.ini file in the same directory
as the driver itself to find the internal driver name.
The internal name of the driver is often the DOS file name with
the file name extension replaced with a $. For example, the
internal name of Mydriver.dos is Mydriver$.
Driver Name
Type the parameters for the Protocol.ini configuration file.
If you use Setup to automatically fill in this page, you will see
the parameters that you need to adjust. For the majority of
plug-and-play cards, all of the parameters are optional, so you
can either accept the defaults or leave this field empty.
Parameters
4 In the Mode drop-down list, click Select Automatically to let Ghost determine
the best multicasting mode based on the information in the NDIS driver.
If the Select Automatically mode does not work, try Receive Mode 5. If that
does not work, try Receive Mode 6.
5 Click OK to continue creating the boot package.
Customizing the template
You may require additional drivers and programs in order to use the network
device attached to your computer. For example, many USB network devices must
load an extra driver for the USB port before the driver for the network device.
Creating boot packages with the Ghost Boot Wizard 281
Adding network drivers to the Ghost Boot Wizard
You can add files to the template and customize the Autoexec.bat and Config.sys
files of the resulting boot package. Usually these are either DOS drivers or
executable programs, but you can add any type of file. Files added to the template
appear in the list to the right of the button.
Note: If you are creating a floppy disk set and you edit Autoexec.bat, you should
ensure that the same changes are made to Autoexec.bat on both disks in the floppy
disk set.
If this template is used as a multicard template, then any additional files or
modifications are overridden by its settings.
To modify a template
1 In the Template Properties window, on the Advanced tab, do any of the
following:
■ Click New and select a file to add to the template.
■ Click Delete to delete the selected file from the list.
■ In the Autoexec.bat field, type any additional Autoexec.bat entries for the
driver.
The entries appear before any network-related commands, such as
Netbind.com or the packet driver executable.
■ In the Config.sys field, type any additional Config.sys entries for the driver.
The entries appear before any driver-related devices to ensure that the
enabling drivers load before the main network device drivers specified on
the network driver page.
2 Click OK to continue creating the boot package.
Adding command-line parameters to a boot package
You can add command-line parameters to a boot package to instruct Symantec
Ghost to perform certain actions.
Command-line parameters can be added while creating a Standard Boot Package,
Network Boot Package, CD/DVD Startup Package with Ghost, TCP/IP Network
Boot Image, or boot package in the Client Type window.
In the following example, the parameters instruct Symantec Ghost to connect to
the GhostCast session called test and restore the disk image to the first drive:
Creating boot packages with the Ghost Boot Wizard
Adding command-line parameters to a boot package
282
Table 11-2 Command parameters
Switch Description
-sure Removes the need to confirm the specified details.
Causes a restart immediately after the cloning
operation.
-rb
Used with the parameter src=@mctest and dst=1.
@mc indicates the GhostCast session name. In this
case, the session name is test.
The session name must match on the client and
server.
dst=1 refers to the destination being fixed disk 1.
-clone
In the following example, the parameters instruct Symantec Ghost to back up
your main disk to an image on another drive:
-clone,mode=create,src=1,dst=D:\backups\maindrv.gho
Table 11-3 Command parameters
Clone parameters Description
mode=create Creates an image file
Creating boot packages with the Ghost Boot Wizard 283
Adding command-line parameters to a boot package
Table 11-3 Command parameters (continued)
Clone parameters Description
src=1 Specifies drive 1 as the source drive
dst=D:\Backups\Maindrv.gho Saves the image to the file D:\Backups\Maindrv.gho
See “About Symantec Ghost switches” on page 467.
Providing MS-DOS
The Ghost Boot Wizard includes PC-DOS on boot packages. However, a boot
package that includes PC-DOS might not start all computers. When you create a
boot package, you can include MS-DOS instead of PC-DOS.
If you use MS-DOS, then you must provide MS-DOS files on the computer on which
you are creating the boot package. Using an MS-DOS system disk that was
formatted on a Windows 95/98 computer, you can install the MS-DOS files during
the creation of the boot package.
For more information, see the Knowledgebase articles at the following URLs:
■ How to create a Microsoft Client boot disk
■ How to create an MS-DOS system disk for Ghost
■ Drive mapping to Windows 2003 Server
To create an MS-DOS system disk on a Windows 95/98 computer
1 Insert a blank floppy disk into drive A of a Windows 95/98 computer.
2 on the Windows taskbar, click Start > Program Files > Windows Explorer.
3 Right-click drive A.
Warning: Do not right-click drive C.
4 Click Format.
5 Check Copy System Files.
6 Click Start to format the disk.
You can install or uninstall MS-DOS while you are creating a boot disk.
Creating boot packages with the Ghost Boot Wizard
Providing MS-DOS
284
To copy MS-DOS to your computer
1 Insert the formatted floppy disk into drive A of the computer on which the
Ghost Boot Wizard is running.
2 In the DOS Version window, click Get MS-DOS.
3 In the Get MS-DOS dialog box, do one of the following steps:
To get MS-DOS from a floppy Click From Floppy Disk, and select a floppy drive.
disk.
To get MS-DOS from a folder. Click From Directory.
4 Click OK.
To remove MS-DOS from your computer
1 In the DOS Version window, click Remove MS-DOS.
2 Click OK.
Installing MS-DOS Client files
If you are using the mapped network drive functionality and MS-DOS, you must
include the Microsoft DOS Client files. You must install the files on the computer
before you can include them on the boot package.
For more information, see the Knowledgebase articles at the following URLs:
■ How to create a Microsoft Client boot disk
■ How to create an MS-DOS system disk for Ghost
■ Drive mapping to Windows 2003 Server
The following files are required:
■ EMSBFR.EXE
■ LMHOSTS
■ NEMM.DOS
■ NET.EXE
■ NET.MSG
■ NETBIND.COM
■ NETH.MSG
■ NETWORKS
Creating boot packages with the Ghost Boot Wizard 285
Installing MS-DOS Client files
■ NMTSR.EXE
■ PROTMAN.DOS
■ PROTMAN.EXE
■ PROTOCOL
■ TCPDRV.DOS
■ TCPTSR.EXE
■ TCPUTILS.INI
■ TINYRFC.EXE
■ UMB.COM
■ IFSHLP.SYS
■ EMM386.EXE
■ HIMEM.SYS
■ WFWSYS.CFG
To install the Microsoft DOS Client files
1 In the DOS version window, click Get MS Client.
2 In the Browse for Folder dialog box, select the MS-DOS LAN Client files.
3 Click OK to continue creating a boot package.
Symantec Ghost support for multiple network
interface cards
The UNDI drivers support multiple network interface cards (NIC) in a computer.
If you have more than one NIC in your computer, and you do not use the UNDI
driver, then it is possible that Ghost might not select the correct card. If you do
not want to use the UNDI driver, then you should edit the Protocol.ini file to select
the correct card.
If Ghost does not select the correct card, you can edit the Protocol.ini file to specify
the correct settings to bind the network driver to the correct network card. You
must specify the physical location of the network card in the computer. The
information that you must include in the Protocol.ini file is specific to the driver
and to the network.
Note: The network driver must be a PCI network card.
Creating boot packages with the Ghost Boot Wizard
Symantec Ghost support for multiple network interface cards
286
Before you edit the Protocol.ini file, you need the following information:
You can obtain this information from the
manufacturer of your NIC. The manufacturer
might also require you to include additional
information in the Protocol.ini file. For
example, the manufacturer might require
you to place the keyword information in a
specific section of the Protocol.ini file.
Some manufacturers use the term device
instead of the word slot.
PCI Location Bus, Slot, and Function
keywords
You can obtain this information by checking
the client computer properties in the Ghost
Console.
See “To view Symantec Ghost Console client
computer properties” on page 95.
Symantec Ghost displays the PCI
information in decimal format. A
manufacturer might require that you use
this hexadecimal format in the Protocol.ini
file.
PCI bus number, slot number, and function
number
When you have the PCI information, you can edit the Protocol.ini file.
For example, a manufacturer provides the following keywords:
■ SLOT
■ BUSNO
■ FUNCTNO
The Symantec Ghost client dialog properties lists the following properties:
B:0 S:17 F:0
In this case, you would edit the Protocol.ini file as follows:
■ SLOT=17
■ BUSNO=0
■ FUNCTNO=0
Creating boot packages with the Ghost Boot Wizard 287
Symantec Ghost support for multiple network interface cards
Creating a DOS boot disk manually
There may be times when you want to create boot disks manually. For example,
you may wish to create a NetWare boot disk, add custom programs, or add batch
files.
To create a DOS boot disk manually
1 If the operating system is DOS/Win 98, insert a blank, formatted floppy disk
into drive A.
2 Type the following:
C:\> sys c: a:
3 Set up the packet driver interface.
For example, type the following command to copy the network interface card
packet driver file:
C:\> copy 3c5x9pd.com a:\
See “Setting up packet drivers” on page 289.
4 To copy Ghost.exe and Wattcp.cfg to the floppy disk, type the following:
C:\> copy progra~1\Symantec\ghost\ghost.exe a:\
C:\> copy progra~1\Symantec\ghost\wattcp.cfg a:\
Creating boot packages with the Ghost Boot Wizard
Creating a DOS boot disk manually
288
5 Edit the Wattcp.cfg file.
For example:
IP = 192.168.100.44
NETMASK = 255.255.255.0
The Wattcp.cfg file stores the TCP/IP stack configuration details and specifies
the IP address and subnet mask of the computer.
See your system administrator for IP and netmask values.
6 Edit the Autoexec.bat startup file.
For example:
3c5x9pd.com 0x60
ghost.exe
Add the command line for the packet drive to the Autoexec.bat file.
For more information, see the packet driver documentation.
Ensure that the same changes are made to Autoexec.bat on both disks in the
floppy disk set.
You can add additional command-line switches to the Ghost.exe command
to automate the cloning process.
See “About Symantec Ghost switches” on page 467.
Setting up packet drivers
There are several packet driver interface options as follows:
■ Network interface card-dependent packet driver.
See “To set up a network interface card-dependent packet driver” on page 290.
■ NDIS version 2.01 driver with packet driver shim supplied by Symantec Ghost.
NDIS version 3 or later drivers do not work with the Ghost client.
See “To set up an NDIS 2.01 network adapter driver with supplied packet driver
shim” on page 290.
■ Third-party network adapter driver and packet driver shim. These have not
been tested or documented with the GhostCasting feature. This includes
ODI-based packet driver shims such as Odipkt.com.
Packet drivers are easy to set up and require minimal configuration.
The NDIS driver setup is more complex. The selection of NDIS 2.01 and shim, or
a network interface card-specific packet driver depends on factors such as
availability, reliability, ease of use, and speed. By running a system test, you can
Creating boot packages with the Ghost Boot Wizard 289
Creating a DOS boot disk manually
choose the best alternative for your network interface card (that is, the specific
packet driver or the NDIS 2.01 driver and shim).
Note: Do not use the Network Client Administrator from Windows NT 4 or the
Microsoft Network Client Installation program to create a GhostCast boot package
as they are not compatible.
To set up a network interface card-dependent packet driver
1 Locate the packet driver for your network interface card.
Packet drivers are usually supplied on the installation disk included with a
network interface card or may be available on the manufacturer’s Web site.
2 Load the packet driver onto the computer.
The command-line arguments vary slightly from driver to driver as follows:
■ 3COM590 PCI network interface card packet driver:
A:\> 3c59xpd.com
■ 3COM509 ISA network interface card packet driver:
A:\> 3c5x9pd.com 0x60
■ NE2000 compatible using software interrupt 0x60 at IRQ10 and IObase
0x280:
A:\> ne2000pd.com 0x60 10 0x280
The syntax for the NE2000pd command is a typical example of an ISA
driver command line. You can find the IRQ and IO base address values
using the setup program included with the network interface card. The
software interrupt can be between 0x60—0x7f.
To set up an NDIS 2.01 network adapter driver with supplied packet driver shim
1 Locate the NDIS 2.01 driver for the network interface card.
NDIS (version 2.01) drivers are usually supplied on the installation disk
included with a network interface card and have a .dos file extension.
Alternatively, NDIS (version 2.01) drivers may be available on the network
interface card manufacturer’s Web site.
2 Copy and modify Protocol.ini, Config.sys, and Autoexec.bat.
Base configuration files ready for editing are included in the GhostCasting
installation files. Extract these configuration files and edit as shown. If you
are creating a floppy disk set and you edit Autoexec.bat, you should ensure
that the same changes are made to Autoexec.bat on both disks in the floppy
disk set.
Creating boot packages with the Ghost Boot Wizard
Creating a DOS boot disk manually
290
3 In the Ghost directory, copy the following files from the \ndis directory:
■ Protman.dos
■ Protman.exe
■ Netbind.com
■ Dis_pkt.dos
4 Restart the computer.
The packet driver interface should now be ready for Symantec Ghost to use.
Table 11-4 lists the files that your directory or floppy package should contain.
Table 11-4 Required files
System files Configuration files NDIS files
Command.com Config.sys Dis_pkt.dos
Msdos.sys (hidden) Autoexec.bat Netbind.com
Io.sys (hidden) Protocol.ini Protman.dos
Protman.exe
*.dos
Note the following:
■ Protman.exe is used during the NETBIND and is not needed in Autoexec.bat.
■ *.dos is the network interface card specific driver (for example, ELNK3.DOS).
Following is a sample Protocol.ini file:
[PROTMAN]
drivername = PROTMAN$
[PKTDRV]
drivername = PKTDRV$
bindings = PC_CARD
intvec = 0x60
chainvec = 0x66
[PC_CARD]
drivername = PNPND$
Change the [PC_CARD] module driver name to correspond to the NDIS driver in
use for your network interface card. For example, if you use a 3COM509 card then
change the driver name to:
Creating boot packages with the Ghost Boot Wizard 291
Creating a DOS boot disk manually
drivername = ELNK3$
Type any additional required options for the network interface card configuration
in the [PC_CARD] module. Refer to the documentation or the sample Protocol.ini
for the network interface card in use, if required. For example, the 3COM509 card
lets you optionally specify the IO Base address:
[PC_CARD]
drivername = ELNK3$
IOADDRESS = 0x300
Following is a sample Config.sys file:
device=protman.dos /I:\
device=dis_pkt.dos
device=pnpnd.dos
The /I: in the first line indicates the location of the Protocol.ini file and must be
present. For example, /I:\ specifies the root directory and /I:A:\NET specifies
A:\NET.
The last line refers to the driver for the network interface card. For example, if
you use a 3COM509, the last line of Config.sys should be replaced with:
device=ELNK3.DOS
Following is a sample Autoexec.bat file:
prompt $p$g
netbind
NETBIND binds the NDIS drivers together and installs the packet driver interface.
Supporting regional keyboards and character sets
You can customize boot disks and packages to support regional keyboards and
character sets by editing the Local.cfg file. The Local.cfg file does not support
languages that use double-byte character sets.
The Local.cfg file is one of the files that is required to support the Ghost Boot
Wizard. It is stored in one of the following locations:
\Documents and Settings\All Users\Application
Data\Symantec\Ghost\Template\Common
Windows XP
\Documents and Settings\All Users\Application
Data\Symantec\Ghost\Template\Common
Windows 2000
Creating boot packages with the Ghost Boot Wizard
Supporting regional keyboards and character sets
292
'컴퓨터관련' 카테고리의 다른 글
| [스크랩] 노트북 LCD 고장증상에 따른 해결방법 (0) | 2007.03.07 |
|---|---|
| windows vista 이야기... 펌. (0) | 2007.02.17 |
| windows vista sysprep... 펌. (0) | 2007.02.16 |
| [펌] Windows XP SP2 에서, 공유기의 NAT 를 통해서 접속하는 환경 (0) | 2007.02.15 |
| 윈도 비스타 종류... 펌. (0) | 2007.02.14 |