How and when to modify the Wattcp.cfg file

Article:TECH108109  |  Created: 2002-01-16  |  Updated: 2008-01-04  |  Article URL http://www.symantec.com/docs/TECH108109
Article Type
Technical Solution

Product(s)

Environment

Issue



This document discusses the use and modification of the Wattcp.cfg file.


Solution



The Wattcp.cfg file is a Ghost configuration file that is used to specify networking parameters for the client computer such as a static IP address. Ghost requires this file only in specific situations that occur when you run Ghost on a TCP/IP network.

In most situations, Ghost automatically creates and uses the file as necessary and no user intervention is required.

In some situations, however, you may want to change the contents of Wattcp.cfg or create a Wattcp.cfg file to resolve a problem. Because Wattcp.cfg is a text file, you can create or edit the file with any text editor.

You do not need to include a line in Config.sys or Autoexec.bat to load Wattcp.cfg. When you run Ghost.exe or Ghostpe.exe and Ghost needs TCP/IP network configuration information, Ghost automatically looks for Wattcp.cfg to obtain the information.
  • If there is no Wattcp.cfg file, Ghost uses default settings.
  • If there is a Wattcp.cfg file, the settings in that file override the Ghost default settings.


When to modify Wattcp.cfg
Typical situations that require editing or creating Wattcp.cfg include the following:
    Static IP address on the bootable floppy disk
    In some situations, you may be using a Ghost bootable floppy disk that is configured for DHCP or Bootp, rather than for a static IP address. DHCP and Bootp are programs that assign IP addresses as needed to computers on a client-server network.

    Typically, you may want to change to a static IP address when:
    • Using a TCP/IP peer-to-peer network rather than a client-server network.
    • Troubleshooting connection problems that you suspect are due to a problem with the DHCP server or Bootp server.
    • Using a client-server network that does not have a DHCP server or Bootp server.

    To change to a static IP address when using a bootable floppy disk, either create a new bootable floppy disk that includes the static IP address, or edit Wattcp.cfg to specify the static IP address.

    Network connectivity problems
    Some problems in communicating over a network are due to the receive mode setting for the client computer. In this situation, a client computer that uses a particular network interface card (NIC) and packet driver appears to have problems communicating on the network but computers with a different NIC or packet driver do not.

    When running Ghost.exe or Ghostpe.exe from a bootable floppy disk, specifying a receive mode of 5 or 6 for the client computer may resolve the problem. To specify the receive mode, edit the Wattcp.cfg file that is on the floppy disk that you start the client computer with.

    DOS version of GhostCast Server
    When you use the DOS version of GhostCast Server, GhostCast Server obtains its TCP/IP networking configuration information from Wattcp.cfg. Create a Wattcp.cfg file when you want to specific any of the parameters that are listed for Wattcp.cfg.

    Note that if you do not specify a static IP address in Wattcp.cfg when using Ghost.exe with the DOS GhostCast Server, Ghost cannot connect to the other computers on the network unless that network is using DHCP or Bootp to automatically assign IP addresses.

    Bootpto
    When the network uses DHCP or Bootp to assign IP addresses, and the client computer appears to time-out before receiving its IP address, you can use Wattcp.cfg to specify a longer wait period by using the BOOTPTO parameter. To specify the wait period, edit the Wattcp.cfg file that is on the floppy disk that you start the client computer with.


How to edit Wattcp.cfg
Because Wattcp.cfg is a text file, you can create or edit the file with any text editor.
  • When using a Ghost bootable floppy disk that you created with Ghost Boot Wizard, the file is located in the A:\Ghost directory.
  • When using a Ghost Boot Partition, the file is located on the Ghost Boot Partition, and is accessible by starting the computer with a bootable floppy disk.
  • When using a Ghost Virtual Boot Partition, the Wattcp.cfg file is created as needed at the time a Ghost Console Task is run. For information on how to modify the Wattcp.cfg file, read the document How to change files or settings in the Ghost Virtual Boot Partition.

Options are set using the format option = value. Comments in the file start with a semicolon (;).

Here is an example of a typical Wattcp.cfg file:

IP=192.168.100.3
NETMASK=255.255.255.0
GATEWAY=192.168.100.1
receive_mode=5; default receive mode is 4

For more examples of Wattcp.cfg files, consult the Ghost user guide or implementation guide that was included when you purchased Ghost.


Where to save Wattcp.cfg
Ghost looks for Wattcp.cfg in the current directory.

For this reason, Wattcp.cfg should normally be located in the same directory as Ghost.exe or Ghostpe.exe on the client. Ghost Boot Wizard, the Ghost Boot Partition, and the Ghost Virtual Boot Partition automatically use this location for saving Wattcp.cfg.

If you change the location of Wattcp.cfg, save it in the same directory as Ghost.exe or Ghostpe.exe. For example, if Ghost.exe or Ghostpe.exe is located at C:\Ghost\ and you are running Ghost from the C drive instead of from the floppy drive, the Wattcp.cfg file should be located in C:\Ghost\.

The exception is when you run Ghost.exe from any directory other than the directory in which Ghost.exe or Ghostpe.exe is located (such as when you run Ghost from the Autoexec.bat file without first changing directories). In this situation, make sure that Wattcp.cfg is located in the current directory. When you run Ghost from the Autoexec.bat file without first changing directories, the current directory is usually the root directory.


Parameters for Wattcp.cfg
The following information is from the Symantec Ghost Implementation Guide for Symantec Ghost 7.5.
    IP
    Specifies the IP address of the local computer. Each computer must have a unique IP address. Symantec Ghost supports the use of DHCP and BOOTP servers and defaults to using them when the IP address is left blank or is invalid. DHCP and BOOTP provide automatic assignment of IP addresses to computers. This lets identical boot disks be used on computers with similar network cards.

    Example: IP=192.168.100.10

    Netmask
    Specifies the network IP subnet mask.

    Example: NETMASK=255.255.255.0

    Gateway (optional)
    Specifies the IP address of the gateway. This option is required when routers are present on the network and when participating computers are located on different subnets.

    Example: GATEWAY=192.168.100.1

    Bootpto (optional)
    Overrides the time-out value (in seconds) for BOOTP/DHCP.

    Example: BOOTPTO=60

    Receive_Mode (Ethernet only)
    Overrides the automatically configured packet driver mode used by Symantec Ghost. The modes in order of preference are 4, 5, and 6. The default mode is 4.

    Some packet drivers misrepresent their ability to receive multicast information from the network and allow the use of packet receive modes that they do not support. The packet driver should be set to mode 4 so that it only accepts the multicast packets required. If the packet driver does not support this mode, mode 5 can be used to collect all multicast packets. The final option, mode 6, configures the packet driver to receive all packets that are being sent on the network, regardless of their destination address.

    Example: RECEIVE_MODE=6


More information
    Situations in which no user intervention is required
    In the following situations, Ghost automatically creates and uses Wattcp.cfg as necessary and no user intervention is required.
    • When you use Ghost Boot Wizard to create a bootable floppy disk, Ghost uses the information you specified while creating the disk to determine whether Wattcp.cfg is necessary. If it is, Ghost automatically creates the file and saves it to the bootable floppy disk in the A:\Ghost folder.
    • When you place a Ghost Boot Partition on a client computer, Ghost uses the information you specified while creating the image of the Ghost Boot Partition to determine whether Wattcp.cfg is necessary. If it is, Ghost automatically creates the file and saves it in the image of the Ghost Boot Partition. When you write the image to the client computer, the new partition includes Wattcp.cfg.
    • When you use a Ghost Virtual Boot Partition for a client computer, Ghost uses the information you specified while configuring parameters for the partition to determine whether Wattcp.cfg is necessary. If it is, Ghost automatically creates the file and saves it in the Ghost Virtual Boot Partition each time you run a Task that uses the Ghost Virtual Boot Partition.

    Which Ghost versions and features use Wattcp.cfg
    Because Ghost requires Wattcp.cfg only to obtain TCP/IP network configuration information (when you do not use the default settings), Wattcp.cfg is used only in TCP/IP networks. These networks include TCP/IP peer-to-peer networks and client-server networks. Ghost does not use Wattcp.cfg when cloning locally or over a peer-to-peer network that is not TCP/IP, such as over an LPT connection.

    Here is a general description of which Ghost versions and features may use Wattcp.cfg:
    • The consumer Ghost versions use Wattcp.cfg only when cloning over a TCP/IP peer-to-peer connection.
    • The corporate Ghost versions use Wattcp.cfg in the same circumstances as the consumer versions.
    • The corporate Ghost versions use Wattcp.cfg in some instances when using Ghost Multicast Server or GhostCast Server.
    • The corporate Ghost versions use Wattcp.cfg in some instances when using Ghost Console. If using a Ghost Boot Partition, Wattcp.cfg may be included in that partition. When using a Ghost Virtual Boot Partition, Wattcp.cfg may be created as needed each time you run a Task.






Legacy ID



2002051609295125


Article URL http://www.symantec.com/docs/TECH108109


Terms of use for this information are found in Legal Notices