Update for the Intel(R) PRO/100 S, PRO/100 Intelligent, and
PRO/1000 Adapters in Microsoft Windows 2000*
What's New in this Release
==========================
The drivers included in this Web release provide the ability
to install and team PRO/100 S, PRO/100 Intelligent, and
PRO/1000 adapters in Windows 2000.
Included here are instructions for:
- Installing the Drivers in Windows 2000
- Removing an Existing Adapter in Windows 2000
- Update Note for Windows NT* 4 Users
- Adding a VLAN in Windows 2000
- Performing a Windows 2000 Unattended Install (Push)
- Installing the Drivers in Windows 2000
======================================
NOTE: Windows 2000 does not offload fragmented IP traffic to
the adapter.
NOTE: If Windows 2000 is enabled for IPSec encryption, the
PRO/100 S adapter automatically offloads the intensive
encryption and authentication functions onto the IPSec
co-processor on the adapter. (The PRO/100 S adapter driver
registers with the operating system to automatically enable
this function.) The result is an increase in throughput
and a decrease in CPU utilization.
1. From the Control Panel, double-click the System icon, select
the Hardware tab, and click the Device Manager button.
2. Select "Network Adapters" and right-click on the appropriate
adapter listing to display its menu. Then click the Properties
menu option.
3. From the Properties dialog box, click the Driver tab and
click the Update Driver button. The Upgrade Device Driver
Wizard appears. Click Next.
4. At the prompt "What do you want the wizard to do?", select
the "Search for a suitable driver for my device" radio button
and click Next.
6. If you downloaded the update files to a temporary directory,
select the "Specify a location" check box and click Next. Then,
specify the path for the temporary directory.
If you downloaded to a floppy, select the "Floppy disk drives"
check box and click Next.
7. Select the "Install one of the other drivers" check box and
click Next.
8. Select the driver located in the temporary directory or floppy
(depending on the case) and click Next.
9. Restart your computer when finished.
*** *** *** *** *** ***
- Removing an Existing Adapter in Windows 2000
============================================
If you are replacing an existing adapter, follow these steps
before physically removing the old adapter card:
1. Double-click My Computer.
2. Double-click Control Panel.
3. Double-click System.
4. Click the Hardware tab.
5. Click the Device Manager button.
6. Double-click Network Adapters.
7. Right-click on the listing for the adapter you want to remove
and click Uninstall.
8. Click OK.
9. Shut down Windows, unplug the computer, and remove the adapter.
*** *** *** *** *** ***
- Update Note for Windows NT 4 Users
==================================
If you upgrade your operating system from Windows NT 4.0 to
Windows 2000, you may need to re-specify your settings for
Speed and Duplex in PROSet.
*** *** *** *** *** ***
- Adding a VLAN in Windows 2000
=============================
NOTE: 802.1p/802.1q is required for VLANs to function. You can
enable this feature through the Advanced tab in PROSet.
However, when 802.1p/802.1q is enabled on an adapter,
that adapter cannot be teamed.
IMPORTANT: You must use PROSet to add or remove a VLAN in Windows
2000. Do not use the Network and Dial-up Connections
dialog box to enable or disable VLANs. Otherwise,
the VLAN driver may not be correctly enabled or
disabled.
1. Create a VLAN on the switch.
Use the parameters you assign there to join the VLAN from the
server. See your switch documentation for more information.
2. In PROSet, click the Virtual LAN tab.
Note that VLANs cannot be assigned to adapters that are already
in an Adapter Team.
3. Under the Virtual LAN tab, click the ADD button.
If this is the first VLAN you're creating, you may see the
following message: "In order for VLANs to function, you must
be connected to a switch which supports IEEE VLANs (802.1Q).
Also, 802.1p/802.1Q Tagging must be enabled on this adapter.
Would you like to enable 802.1p/802.1Q Tagging on this
adapter?"
If this message appears, click Yes to continue. PROSet will
automatically enable the 802.1p/802.1Q feature on the Advanced
tab.
4. Enter the VLAN ID and VLAN Name and click OK.
The VLAN ID must match the VLAN ID on the switch. Valid ID range
is from 1-4094. The VLAN Name is for informational purposes only
and doesn't have to match the name on the switch.
5. Repeat steps 3 and 5 for each VLAN you want the server to join.
802.1p/802.1q is enabled for all VLANs after it is enabled for the
first VLAN. The VLANs you add are listed on the Adapters tab.
6. At the Virtual LAN tab, click OK and restart the computer if
prompted.
*** *** *** *** *** ***
- Performing a Windows 2000 Unattended Install (Push)
===================================================
The main objective of the Push Installation is to get the client
properly connected to the distribution server before the installation
begins using the NDIS2 driver, and to keep the same client connected
using the NDIS5 driver after the Windows 2000 system is installed
without any end user action. A distribution server is any system
capable of being accessed from the network that contains the
Windows 2000 distribution folder (the I386 directory and supporting
files).
The main difficulty is that the list of supported adapters on the
Windows 2000 CD-ROM is restricted and thus special steps must be
performed to update the installation source files and modify the
scripts to automate the process (for the adapters not on the list).
The main steps of the process are:
1. Create a Network Installation Startup disk from a Windows NT 4.0
Server and modify it for your adapter.
2. Create a shared directory for the Windows 2000 Workstation
Installation files on a distribution Server.
3. Modify the UNATTEND.TXT installation script to automate the
procedure and add the proper adapter installation and
configuration information.
4. Integrate the adapter driver files into the Windows 2000 installation
source files.
5. Perform the Unattended Setup booting with the prepared setup disk
from the client system.
The Procedure:
1. Prepare a distribution server:
a) Create a folder on the server's hard disk for the
installation files (e.g., "PUSHW2K"). Make this folder
shared (e.g., with shared name "PUSHW2K").
b) Create a user (e.g., "USERID" with a password "password")
and granted read and view rights for the PUSHW2K folder.
2. Use a CD-ROM drive at the distribution server and copy the files
from the i386 folder with Windows 2000 installation files to the
shared folder PUSHW2K on this server (e.g., using Explorer).
3. Create / Modify the installation answer file UNATTEND.TXT as
required by your specific system and desired Windows 2000
configurations. Note that UNATTEND.TXT may be read-only and
may need to be made write-able before editing (e.g.,
attrib -r unattend.txt). A sample UNATTEND.TXT file with
comments is included at the end of this document. Microsoft
also includes a sample UNATTEND.TXT in the I386 directory.
Specify the full path to the UNATTEND.TXT file in the batch file
for the WINNT command (see Step 6(L) below).
4. Create the \E100B directory: PUSHW2K\$OEM$\Drivers\Net\E100B.
5. Copy driver installation files:
Xcopy the Intel Configuration and Drivers Disk
to the proper place under Adapter Device Driver folder
(PUSHW2K\$OEM$\Drivers\Net\E100B folder on the distribution
server). This enables the installation program to find
the same file structure as on the Drivers disk. Be sure
to use the /s /e switches on xcopy.
6. Prepare a Microsoft Client Installation disk using the Windows NT
Network Client Administrator from a Windows NT 4.0 Server:
a) Prepare a bootable diskette (e.g., DOS 6.22: format a: /s).
b) Use the Windows NT Administrative Tools (Common), start
Network Client Administrator and choose "Make Network
Installation Startup Disk".
c) Set "Existing Path" to use the previously installed software
for MS Client or, if it is the first time, create the shared
directory on the server's hard drive, using the Windows NT 4.0
Server CD-ROM as a source (e.g., by copying from \client on
the CD-ROM to c:\client).
d) Choose "Network Client v3.0 for MS-DOS and Windows".
e) Choose any of the Network Adapters from the list
(e.g., NE2000 compatible).
f) Set Computer name, User name, Domain and Network protocol
when prompted.
g) Select OK and wait while files are copied to the disk.
h) Copy the proper ndis2 dos driver (E100B.DOS) to this disk
in the \NET directory. E100B.DOS can be found in
\DOS on the Intel CD.
i) Modify A:\NET\SYSTEM.INI : netcard = E100B.DOS
j) Modify A:\NET\PROTOCOL.INI : drivername = E100B$
k) Add a line: CACHEFLUSH = 1
just after the "drivername = E100B$" line.
l) Verify or modify A:\AUTOEXEC.BAT to have the following
commands:
NET USE W: \\PST\PUSHW2K
W:\WINNT /s:W:\ /u:W:\unattend.txt
Note that W is an example for the logical drive mapped to
the share on the Windows NT server with computer name PST
in this example.
m) Remove the invocation of setup.exe from A:\AUTOEXEC.BAT.
7. Boot up your DOS client with the disk prepared above installed.
After connecting to the network:
a) Input "USERID" as a User name when prompted.
b) Input "password" as a password when prompted.
OR
c) Modify the NET START line in the AUTOEXEC.BAT to
NET LOGON USERID PASSWORD /YES
Sample Templates:
1) PROTOCOL.INI
[network.setup]
version=0x3110
netcard=ms$ne2clone,1,MS$NE2CLONE,1
transport=ms$ndishlp,MS$NDISHLP
transport=ms$netbeui,MS$NETBEUI
lana0=ms$ne2clone,1,ms$netbeui
lana1=ms$ne2clone,1,ms$ndishlp
[ms$ne2clone]
drivername = E100B$
CACHEFLUSH = 1
; CACHEFLUSH line is required ONLY IF NDIS2 does not shut down
; properly
;INTERRUPT=3
;IOBASE=0x300
;SlotNumber=1
[protman]
drivername=PROTMAN$
PRIORITY=MS$NDISHLP
[MS$NDISHLP]
drivername=ndishlp$
BINDINGS=ms$ne2clone
[ms$netbeui]
drivername=netbeui$
SESSIONS=10
NCBS=12
BINDINGS=ms$ne2clone
LANABASE=0
2. SYSTEM.INI
[network]
filesharing=no
printsharing=no
autologon=yes
computername=COMPUTERNAME
lanroot=A:\NET
username=Administrator
workgroup=DOMAIN
reconnect=no
directhost=no
dospophotkey=N
lmlogon=0
logondomain=DOMAIN
preferredredir=full
autostart=full
maxconnections=8
[network drivers]
netcard=E100B.DOS
transport=ndishlp.sys,*netbeui
devdir=A:\NET
LoadRMDrivers=yes
[Password Lists]
*Shares=a:\net\Share000.PWL
USERID=A:\NET\USERID.PWL
3. AUTOEXEC.BAT
path=a:\net
a:\net\net start
rem a:\net\net logon userid password /yes
net use W: \\PST\PUSHW2K
W:
winnt /s:W:\ /u:W:\unattend.txt
4. UNATTEND.TXT
[Unattended]
Unattendmode = FullUnattended
;Values: GuiAttended | ProvideDefault | DefaultHide | ReadOnly | FullUnattended
;GuiAttended specifies that the GUI-mode section of Setup is attended
;ProvideDefault specifies that answers in the answer file are defaults
;DefaultHide specifies that answers in the answer file are defaults
;ReadOnly specifies that answers in the answer file are read-only
;FullUnattended specifies that GUI mode is fully unattended
OemPreinstall = YES
;Values: Yes | No
;Yes means any other existing subfolders are copied
TargetPath = WINNT
;Values: * | <path name>
;Path is the installation folder in which Windows 2000 should be installed.
Filesystem = LeaveAlone
;Value: ConvertNTFS | LeaveAlone
OemSkipEula = Yes
;Values: Yes | No
;Yes specifies that the user should not be prompted to accept
;the End User License Agreement (EULA) included with Windows 2000.
OemPnpDriversPath="drivers\net\e100b"
;Value: <folder 1 on system drive>;<folder 2 on system drive>;
;Specifies paths to folders that contain Plug and Play (PnP)
;drivers that do not ship on the Windows 2000 CD. Example:
;OemPnPDriversPath = "drivers\audio;drivers\net"
[UserData]
ProductID=xxxx-xxxx-xxxx-xxxx-xxxx
;Value: <string>
;Microsoft Product Identification (Product ID) number
FullName = "Administrator"
;Value: <string>
;The user's full name. If empty or missing, the user is prompted
OrgName = "Intel"
;Value: <string>
;An organization's name. If empty or missing, the user is prompted
ComputerName = "COMPUTER1"
;Value: <string>
;The computer name. If empty, missing or duplicate,
;the user is prompted
[GuiUnattended]
TimeZone = "004"
;Value: <index>
;Index Zone Index Zone
;000 Int'l Dateline 140 S. Africa:
;001 Samoa 145 Russian
;002 Hawaii 150 Arab
;003 Alaskan 155 E. Africa
;004 Pacific 160 Iran
;010 Mountain 165 Arabian
;015 U.S. Mountain: Arizona 170 Caucasus Pacific
;020 Central 175 Afghanistan
;025 Canada Central 180 Russia Yekaterinburg
;030 Mexico 185 W. Asia
;035 Eastern 190 India
;040 U.S. Eastern: Indiana 195 Central Asia
;045 S.A. Pacific 200 Sri Lanka
;050 Atlantic 205 S.E. Asia
;055 S.A. Western 210 China
;060 Newfoundland 215 Singapore
;065 E. South America 220 Taipei
;070 S.A. Eastern 225 W. Australia
;075 Mid-Atlantic 230 Korea: Seoul
;080 Azores 235 Tokyo
;085 GMT (GMT) 240 SakhaYakutsk
;090 GMT Greenwich 245 A.U.S. Central: Darwin
;095 Central Europe 250 Central Australia
;100 Central European 255 A.U.S. Eastern
;105 Romance 260 E. Australia
;110 W. Europe 265 Tasmania
;115 E. Europe 270 Vladivostok
;120 Egypt 275 W. Pacific
;125 FLE 280 Central Pacific
;130 EET 285 Fiji
;135 Israel: Jerusalem 290 New Zealand
AdminPassword = *
;Value: <password> | *
;* sets the Administrator password to NULL.
OEMSkipWelcome = 1
;Value: 1 | 0
;A value of 1 causes the Welcome page to be skipped.
;Only valid on Windows 2000 Professional
OEMSkipRegional = 1
;Values: 0 | 1
;If OemPreinstall = Yes, set OemSkipRegional = 1 to ensure
;setup completes without prompting for regional settings
[LicenseFilePrintData]
AutoMode = PerSeat
;Values: PerSeat | PerServer
;Servers only
;If AutoMode = PerServer, the AutoUsers key must also be specified
;If empty or missing, the user is prompted
[Display]
BitsPerPel = 16
;Value: <valid bits per pixel>
;Valid bits per pixel. A value of 8 (28) implies 256 colors,
:16 implies 65,536 colors.
XResolution = 800
;Value: <valid x resolution>
YResolution = 600
;Value: <valid y resolution>
VRefresh = 60
;Value: <valid refresh rate>
[Identification]
JoinDomain=MyDomain
;Value: <domain name>
;The name of the domain in which the computer participates.
;Either this key or the JoinWorkgroup key can be specified
DomainAdmin=Administrator
;Value: <domain admin name>
;name of a user account in the domain that has permission
;to create a computer account
DomainAdminPassword=AdminPass
;Value: <password of user specified in domainadmin>
[Networking]
InstallDefaultComponents=Yes
;Value: Yes | No
;Default: No
;Yes installs default networking components.
;The default components to be installed are:
;Component What is Installed
;Adapters All network adapters
;Protocols Internet Protocol (TCP/IP)
;Services File and Printer Sharing for Microsoft Networks
;Clients Client for Microsoft Networks
REFERENCES:
1. Microsoft Windows 2000 Unattended Setup Mode Parameters Guide
2. Microsoft Windows NT Resource Kit - Microsoft Press 19NT
3. Microsoft TechNet CD-ROM, April 1997
4. Microsoft support web page at http://support.microsoft.com/support
Article ID : Q155197, Q156795
* Third-party trademarks are the property of their respective owners.
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.