|
Creating a boot image containing the Console boot partition |
|
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.
|
To create a boot image that contains a Console boot partition |
|
3.
|
|
Select the network driver for the make and
model of the network card installed on the client computer.
|
If the correct driver isn't in the list, add the driver.
You can add more than one driver to the boot package.
|
7.
|
|
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.
|
8.
|
|
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.
|
9.
|
|
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.
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.
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.
