pushnt4.txt Driver File Contents (815elan.zip)

Windows NT 4.x Push Install Instructions
========================================

Contents:
I.	Introduction
II.   	Setting up an install directory on the file server
III.    Prepare the Microsoft Client Installation diskette 
IV.     Sample Templates

I. Introduction

    The push installation of Windows* NT 4.x is achieved by setting the 
    options in the Unattend.txt file.

    The main steps of the process are:

    1. Create a Network Installation Startup disk from the Windows NT
       Server and modify it for your adapter.

    2. Create a shared directory for the Windows NT Workstation
       Installation files on the Windows NT Server.

    3. Modify the UNATTEND.TXT installation script to automate the
       procedure and add the proper adapter installation and
       configuration information.

       The sample UNATTEND.TXT file provided shows how to override
       default registry parameters for the adapter in the [E100BParameters]
       section. Override parameters should not be used unless the default
       parameters will not work properly for a specific installation.  The
       sample parameters are commented out.

    4. Integrate the adapter driver files into the Windows NT installation
       source files.

    5. Perform the Unattended Setup booting with the prepared setup disk
       from the client system.


II. Setting up an install directory on the file server

    1. Create a folder on the server's hard disk for the
       installation files (e.g., "NT40.INS").  Make this folder
       shared (e.g., with shared name "NT40.INS").

    2. Create a user (e.g., "USERID" with a password "password")
       and grant read and view rights for the NT40.INS folder.

    3. Use a CD-ROM drive at the Windows NT server and copy the i386
       folder with Windows NT 4.0 installation files to the shared
       folder NT40.INS on this server (e.g., using the NT Explorer).

    4. Create / Modify the installation answer file UNATTEND.TXT as
       required by your specific system and desired Windows NT
       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.

      The best place to put this file is in the root of your install
      disk, but the real requirement is just to specify the full
      path to this file in the AUTOEXEC.BAT for the WINNT command
      (see 6b) and 6m) below).

    5. Create the \E100B directory:    NT40.INS\i386\$OEM$\Net\E100B.

    6. Copy driver installation files:
       Xcopy the Intel Configuration and Drivers Disk
       to the proper place under Adapter Device Driver folder
       (NT40.INS\i386\$OEM$\Net\E100B folder on the Windows NT
       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.

       Alternatively, you can use the pushcopy.bat file located in the
       \PushInstall directory on the Drivers CD.
       Example: "d:\pushinstall\pushcopy z:\NT40.INS\i386 NT"
       This command will create the $OEM$\Net\E100B directory structure.
      
III. Prepare the Microsoft Client Installation diskette 

    1. Using the Windows NT Network Client Administrator:

        a)  Prepare a system diskette (e.g., DOS 6.22: format a: /s).  Do
            not use the Windows NT system disk.

        b)  Copy UNATTEND.TXT from \NT40.INS\i386 to the diskette as
            specified in 3) above (preferably to the root (a:\)).

        c)  Use the Windows NT Administrative Tools (Common), start
            Network Client Administrator and choose "Make Network
            Installation Startup Disk".

        d)  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).

        e)  Choose "Network Client v3.0 for MS-DOS and Windows".
 
        f)  Choose any of the Network Adapters from the list
            (e.g., NE2000 compatible).

        g)  Set Computer name, User name, Domain and Network protocol
            when prompted.

        h)  Select OK and wait while files are copied to the disk.

        i)  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 Configuration and Driver Disk.

        j)  Modify A:\NET\SYSTEM.INI :  netcard = E100B.DOS

        k)  Modify A:\NET\PROTOCOL.INI :  drivername = E100B$

        l)  Add a line: CACHEFLUSH = 1
            just after the "drivername = E100B$" line.

        m)  Verify or modify A:\AUTOEXEC.BAT to have the following
            commands:

            NET USE W: \\PST\NT40.INS
            W:\i386\WINNT /s:W:\i386 /u:a:\unattend.txt
 
            Note that W is an example for the logical drive mapped to
            the share on the Windows NT server.

        n)  Remove the invocation of setup.exe from A:\AUTOEXEC.BAT.

    2. Boot up your DOS client with the disk prepared above.
       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


IV. 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

;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: \\133\nt40.ins
W:
cd i386
winnt /s:W:\i386 /u:a:\unattend.txt

4) UNATTEND.TXT

[Unattended]
OemPreinstall = yes
NoWaitAfterTextMode = 1
NoWaitAfterGUIMode = 1
FileSystem = LeaveAlone
ExtendOEMPartition = 0
ConfirmHardware = no
NtUpgrade = no
Win31Upgrade = no
TargetPath = winnt
OverwriteOemFilesOnUpgrade = no
OemSkipEULA = yes

[GuiUnattended]
OemSkipWelcome = 1
OEMBlankAdminPassword = 1
TimeZone = "(GMT-08:00) Pacific Time (US & Canada)"

[UserData]
FullName = "Userid"
OrgName = "Organization"
ComputerName = COMPUTER
ProductId = "xxx-xxxxxxx"
;or Product key if you are using OEM versions

[Display]
ConfigureAtLogon = 0
BitsPerPel = 8
XResolution = 640
YResolution = 480
VRefresh = 60
AutoConfirm = 1

[Network]
InstallAdapters = SelectedAdaptersSection
InstallProtocols = ProtocolsSection
InstallServices = ServicesSection
JoinWorkgroup = workgroup

[SelectedAdaptersSection]
E100B = E100BParameters, ..\$OEM$\Net\E100B\

[E100BParameters]
; For Cardbus configuration
;MemoryAddress = 0x0C000000		; sample parameter only
;InterruptNumber = 11   		; sample parameter only
;IOBaseAddress = 0x0F00    		; sample parameter only
;MemoryMappedBaseAddress = 0x00000000	; sample parameter only

; Other configuration parameters
;BusNumber = 4				; sample parameter only
;SlotNumber = 10			; sample parameter only
;SpeedDuplex = 0			; 0 = Auto Detect
;			       		  1 = 10Mbps/Half Duplex
;					  2 = 10Mbps/Full Duplex
;					  3 = 100Mbps/Half Duplex
;					  4 = 100Mbps/Full Duplex

[ProtocolsSection]
TC = TCParamSection

[TCParamSection]
DHCP = yes

[ServicesSection]


REFERENCES:

1. Microsoft Windows NT Resource Kit - Microsoft Press 19NT
2. Microsoft TechNet CD-ROM, April 1997
3. Microsoft support web page at http://support.microsoft.com/support
   Article ID : Q155197, Q156795
Download Driver Pack

How To Update Drivers Manually

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.

server: ftp, load: 2.22