There are several packet driver interface
options:
- Network interface card-dependent packet driver.
- 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.
- 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 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 disk as they are not
compatible.
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.
- 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.
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 edit
Autoexec.bat ensure that the same changes are made to Autoexec.bat
on both disks in the floppy disk set.
3.
|
|
In the Ghost directory, copy the following
files from the \ndis directory:
|
4.
|
|
Restart the computer.
|
The packet driver interface should
now be ready for Symantec Ghost to use.
Table 2-4 lists the files that your
directory or floppy disk should contain.
Table 2-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).