Hi all,
I'm actually use Ghost 11.5 version in my company, unfortunaly I lost my usb key for take a ghost by network. Since i tryed to recreate this usb key but I have a problems with my Network card ( Intel) and your Ghost USB key.
I have created this USB with your application : Ghost boot Wizard with this readme.txt >>
Using Intel Adapters with Symantec Ghost*
=========================================
1) General Information
2) Creating a diskette for Symantec Ghost* Enterprise 7.5
3) Editing the PROTOCOL.INI
General Information
-------------------
After creating a boot disk for Ghost, you should replace the driver files supplied
with Ghost for Intel adapters in the \NET directory of the boot diskette with the
updated version contained in this archive. Use E100B.DOS for Intel PRO/100 adapters,
and E1000.DOS for Intel PRO/1000 adapters.
Use GHOST.EXE with the -FNI switch when using LAN on Motherboard implementations
of Intel Network Interfaces, or if you are experiencing system hangs when the driver
loads. This can be added as a parameter through the Ghost Boot Wizard, or by a manual
edit of the AUTOEXEC.BAT file after the diskette is created.
If you are using motherboards with Intel 865 or 875 chip sets, check the Symantec
web site for updates.
If you want to force speed and duplex, or modify any other parameters for the Intel
adapter, see "Editing the PROTOCOL.INI" at the end of this document.
Creating a diskette for Symantec Ghost* Enterprise 7.5
------------------------------------------------------
These instructions will step you through creating a network boot diskette for
Symantec Ghost Enterprise 7.5 and customizing it for Intel LAN interfaces.
1) Start the Symantec Ghost Boot Wizard
2) Select Network Boot Disk
3) Select either the Intel PRO 100 (for Intel 10/100 adapters) or Intel PRO 1000
(for Intel gigabit adapters)
4) Select the version of DOS you will be using
5) Select Symantec Ghost, then add any startup parameters
NOTE: If you experience system hangs when the adapter driver loads, or other
apparent adapter driver related issues, use the startup parameter -fni
6) Select DHCP or enter a static IP address
7) Specify your diskette parameters, and then confirm the details
8) Select "next" to finish, and continue until you complete the diskette creation
process.
9) Replace the adapter driver that Ghost copied to the \NET directory on the
diskette with the updated driver supplied in this archive. For 10/100 adapters,
use E100B.DOS. For Gigabit adapters, use E1000.DOS. If additional parameters,
such as speed and duplex, are needed, see the next section on how to edit the
PROTOCOL.INI file.
Editing the PROTOCOL.INI
------------------------
If additional adapter parameters are needed, such as forcing speed and
duplex, use any text editor to edit the file net\protocol.ini.
For a complete list of available parameters, use any browser to open the file
\DOCS\DOS-DODI\driv_dos.htm.
The sample PROTOCOL.INI supplied in the \GHOST directory of this archive shows
usage examples. Any text in the sample file following a semicolon (;) will be
ignored by the software, and are included to add usage comments for the user.
To enable an option in the sample, remove the semicolon from the left-most column.
Here are instructions for the most commonly used parameters.
drivername = E1000$
Use E1000$ for PRO/1000 adapters or E100B$ for PRO/100 adapters. Drivername is the
only required parameter for the driver. All others are optional.
NODE = "00D00C123456"
The NODE parameter overrides the burned in MAC address. Use this parameter if you
are using Locally Administered Addresses
SPEEDDUPLEX = # (E1000.DOS driver for PRO/1000 adapters only)
Where # = the number specifying the desired speed and duplex. 0 equals 10Mbps half
duplex, 1 equals 10Mbps full duplex, 2 equals 100Mbps half duplex and 3 equals
100Mbps full duplex. There is no parameter for 1000 Mbps, as this is always
autonegotiated. Leave this parameter out if you want to run at 1000 MBPS.
SPEED = # (E100B.DOS driver for PRO/100 adapters only)
Where # equals 10 or 100. Sets the adapter speed to 10Mbps or 100Mbps.
FORCEDUPLEX = # (E100B.DOS driver for PRO/100 adapters only)
Where # equals 0 (autonegotiate), 1 (half duplex) or 2 (full duplex)
SLOT = #
Where # equals the slot number. This parameter is not needed if there is only one
adapter in the system. If the driver finds more than one adapter in the system and
this parameter is not used or is not valid, the driver will load on the
first adapter it finds. If more than one NIC is present in the computer, set this
for the NIC you wish to use. Should you need this parameter, download PROADMIN.EXE
and see the documentation for the IDAdapt.exe utility, which explains the slot
parameter usage in detail and how to use the utility to determine each adapters
current slot number.
------------------------------------------------------------------------------------
This document, README.TXT, as well as the software described in it is furnished
under license and may only be used or copied in accordance with the terms of the
license. The information in this manual is furnished for informational use only,
is subject to change without notice, and should not be construed as a commitment
by Intel Corporation. Intel Corporation assumes no responsibility or liability for
any errors or inaccuracies that may appear in this document or any software that
may be provided in association with this document. Except as permitted by such
license, no part of this document may be reproduced, stored in a retrieval system,
or transmitted in any form or by any means without the express written consent of
Intel Corporation.
* Other product and corporate names may be trademarks of other companies and are
used only for explanation and to the owner's benefit, without intent to infringe.
When i'm launch a usb key, i have this result:
Error: unable to locate the PCI Lan Adapter.
1.The system may not support the PCI bus
2.The PCI adapter may not be properly installed in a slot
3. Some of the PCI adapter resources in configuration space may be invalid
Check for possible errors listed above and run adapter diagnostics
Failure: Driver did not load, NDIS environment invalid
Erreur: 33 Unable to bind
my Autoexec.bat content :
@echo off
prompt $p$g
\net\netbind.com
MOUSE.COM
cd \ghost
echo Loading...
GHOST.EXE -fni
my Config.sys content :
DEVICE=\net\protman.dos /I:\net
DEVICE=\net\dis_pkt.dos
DEVICE=\net\e1000.dos
my protocol.ini content :
[protman]
drivername=PROTMAN$
[pktdrv]
drivername=PKTDRV$
bindings=nic
intvec=0x60
chainvec=0x66
[nic]
drivername = e1000$
[nic]
drivername = E1000$
; NODE = "00D00C123456" ; override the burned in MAC address
; SPEEDDUPLEX = 0 ; 10Mbps half duplex
; = 1 ; 10Mbps full duplex
; = 2 ; 100Mbps half duplex
; = 3 ; 100Mbps full duplex
; SLOT = 7 ; set this for each NIC if using more than one. See readme.txt for details
; CACHEFLUSH = 1 ; set this if doing an unattended installation of
; Windows NT 4.0 using this driver to make the initial
; connection
I have changed e1000.dos file like read on readme.txt.
I followed the documentation but it doesn't work. I don't know exactly what is a proble with this configuration...?
Thanks for your help.