1. gnic_nt_082897.zip Driver
2. PEI100X.INF File Contents

PEI100X.INF Driver File Contents (gnic_nt_082897.zip)

;*           Name:  PEI100X.INF
;*          Title:  PEI100X.SYS setup file for Windows 95 OEM SR2
;*  Creation Date:  March 27, 1997
;*
;*  Version History
;*  ---------------
;*
;*    Date    Who?  Description
;*  --------  ----  -------------------------------------------------------
;*  05/20/97  CFJ   Updated to install Packet Engines drivers.
;#BeginRevision
;*  04/16/97  RAJ   Updated to install NDIS 3 or NDIS 4 adapter
;*  04/07/97  RAJ   Updated to only work with rev B silicon.
;#EndRevision
;*  03/27/97  RAJ   Created.
;#EndRevision
;*
;#BeginDescription
;*
;*  This file contains the PEI100X.SYS Windows 95 OEM SR2 setup initialization
;*  scripts.
;*
;#EndDescription
;*
;*-------------------------------------------------------------------------

[Version]
LayoutFile=layout.inf
signature="$CHICAGO$"
Class=Net
provider=%V_PROVIDER%

[Manufacturer]
%V_PACKET%=Packet

[Packet]
;Because Windows 95 will load the first driver listed by default and sometimes
;doesn't provide the user a choice of which driver to load, we must list the
;most compatible driver first.  Since the NDIS 3 driver works on all versions of
;Windows 95 and the NDIS 4 driver only works on the OEMSR2 release, we must list
;the NDIS 3 driver first.
%PEI100X_NDIS3.DeviceDesc%=PEI100Xndis3.ndi,PCI\VEN_1000&DEV_0702
%PEI100X.DeviceDesc%=PEI100X.ndi,PCI\VEN_1000&DEV_0702

;****************************************************************************
; Packet Engines PEI100X Ethernet Adapter
;****************************************************************************

[PEI100X.ndi]
;'Execute' the following sections:
;   PEI100X.ndi.reg - Setup the device specific information
;   ENET_1000.ndi.reg - Setup the information for all 1000 cards
;   ENET_1000 - Setup user changeable data for all 1000 cards
AddReg=PEI100X.ndi.reg, ENET_1000.ndi.reg, ENET_1000.params

[PEI100Xndis3.ndi]
;Change the ethernet setup to use the NDIS 3 version data
AddReg=PEI100X.ndi.reg, ENET_1000_NDIS3.ndi.reg, ENET_1000.params

[PEI100X.ndi.reg]
; key,subkey,value-name,type,value
HKR,Ndi,DeviceID,,"PCI\VEN_1000&DEV_0702"
HKR,Ndi,CardType,,"PCI"

;****************************************************************************
; Ethernet 1000 megabit adapters
;****************************************************************************
[ENET_1000.ndi.reg]

; Setup NDI general driver information
; DevLoader indicates that we are loaded by NDIS
; DeviceVxDs indicates which files and in what order to load
; EnumPropPages ???
HKR,,DevLoader,,*ndis
HKR,,DeviceVxDs,,PEI100X.sys
HKR,,EnumPropPages,,"netdi.dll,EnumPropPages"

; NDIS Info
; This data indicates that we are an NDIS 4.0 driver
HKR,NDIS,LogDriverName,,"PEI100X"
HKR,NDIS,MajorNdisVersion,1,04
HKR,NDIS,MinorNdisVersion,1,00

; Interfaces
; DefUpper and UpperRange define what our upper driver interface is like for
;   binding information.  DefLower and LowerRange indicate what we provide at
;   our lower edge.
HKR,Ndi\Interfaces,DefUpper,,"ndis3"
HKR,Ndi\Interfaces,DefLower,,"ethernet"
HKR,Ndi\Interfaces,UpperRange,,"ndis3"
HKR,Ndi\Interfaces,LowerRange,,"ethernet"

; Install sections
; The value-name of ndis3 matches our DefUpper value.  We need one of these
; subkey's for every value in DefUpper.  The value parameter indicates which
; section in this file to 'execute' in order to install our driver.
HKR,Ndi\Install,ndis3,,"PEI100X.ndis4"

[ENET_1000_NDIS3.ndi.reg]
;This is pretty much the same as above but the driver file name and the NDIS
;version supported are different.
HKR,,DevLoader,,*ndis
HKR,,DeviceVxDs,,PEI100X3.sys
HKR,,EnumPropPages,,"netdi.dll,EnumPropPages"
HKR,NDIS,LogDriverName,,"PEI100X"
HKR,NDIS,MajorNdisVersion,1,03
HKR,NDIS,MinorNdisVersion,1,0A
HKR,Ndi\Interfaces,DefUpper,,"ndis3"
HKR,Ndi\Interfaces,DefLower,,"ethernet"
HKR,Ndi\Interfaces,UpperRange,,"ndis3"
HKR,Ndi\Interfaces,LowerRange,,"ethernet"
HKR,Ndi\Install,ndis3,,"PEI100X.ndis3"

;****************************************************************************
; Ethernet 1000 megabit adapter parameters
;****************************************************************************
[ENET_1000.params]

; The following parameters are required by our driver.  These values must not
; change or we will call NDIS with invalid data.  NDIS has its own mechanism of
; finding our cards so we don't have to worry about the BusNumber, DeviceNumber
; or FunctionId being the actual PCI values.
;
; BusType of 5 is PCI
HKR,,BusType,,5
HKR,,BusNumber,,0
HKR,,DeviceNumber,,0
HKR,,FunctionId,,0

;****************************************************************************
; File copy sections
;****************************************************************************
[PEI100X.ndis4]
CopyFiles=PEI100X.ndis4.CopyFiles, PEI100X.inf.CopyFiles

[PEI100X.ndis4.CopyFiles]
PEI100X.SYS, PEI100X.i

[PEI100X.ndis3]
CopyFiles=PEI100X.ndis3.CopyFiles, PEI100X.inf.CopyFiles

[PEI100X.ndis3.CopyFiles]
PEI100X3.SYS, PEI100X3.i

[PEI100X.inf.CopyFiles]
PEI100X.inf

[SourceDisksNames]
1="Packet Engines Installation Disk", "",

[SourceDisksFiles]
PEI100X.i=1
PEI100X3.i=1

[DestinationDirs]
DefaultDestDir              =11 ; LDID_SYS
PEI100X.ndis4.CopyFiles     =11 ; LDID_SYS
PEI100X.ndis3.CopyFiles     =11 ; LDID_SYS
PEI100X.inf.CopyFiles       =17 ; INF_DIR

;****************************************************************************
; Localizable Strings
;****************************************************************************
[strings]
; Provider
V_PROVIDER="Packet Engines, Inc"
; Manufacturers
V_PACKET="Packet Engines, Inc"

; PCI Devices
PEI100X.DeviceDesc="NDIS 4 Packet Engines PEI100X Ethernet Adapter"
PEI100X_NDIS3.DeviceDesc="NDIS 3 Packet Engines PEI100X Ethernet Adapter"