home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.networkinstruments.com
/
2015-02-04.ftp.networkinstruments.com.tar
/
ftp.networkinstruments.com
/
pub
/
demos
/
ObserverSetup.exe
/
Win32
/
Drivers
/
NiFr1S.inf
< prev
next >
Wrap
Windows Setup INFormation
|
2013-01-17
|
3KB
|
118 lines
;; NiFr1S.inf
;; ********* PLEASE READ ***********
;; The wizard cannot create exact INF files for all buses and device types.
;; You may have to make changes to this file in order to get your device to
;; install. In particular, hardware IDs and logical configurations require
;; intervention.
;;
;; The Win2K DDK documentation contains an excellent INF reference.
;--------- Version Section ---------------------------------------------------
[Version]
Signature="$Chicago$"
Provider=%ProviderName%
; If device fits one of the standard classes, use the name and GUID here,
; otherwise create your own device class and GUID as this example shows.
Class=NewDeviceClass
ClassGUID={ff646f80-8def-11d2-9449-00105a075f6b}
DriverVer=12/05/2012,16.0.0000
;--------- SourceDiskNames and SourceDiskFiles Section -----------------------
; These sections identify source disks and files for installation. They are
; shown here as an example, but commented out.
;[SourceDisksNames]
;1 = "Install Disk",Disk1,,
;[SourceDisksFiles]
;NiFr1S.sys = 1,,
;--------- ClassInstall/ClassInstall32 Section -------------------------------
; Not necessary if using a standard class
; 9X Style
[ClassInstall]
Addreg=Class_AddReg
; NT Style
[ClassInstall32]
Addreg=Class_AddReg
[Class_AddReg]
HKR,,,,%DeviceClassName%
HKR,,Icon,,"-5"
;--------- DestinationDirs Section -------------------------------------------
[DestinationDirs]
NiFr1S_Files_Driver = 10,System32\Drivers
;--------- Manufacturer and Models Sections ----------------------------------
[Manufacturer]
%MfgName%=Mfg0
[Mfg0]
; PCI hardware IDs use the form
; PCI\VEN_aaaa&DEV_bbbb&SUBSYS_cccccccc&REV_dd
;
%DeviceDesc%=NiFr1S_DDI, PCI\VEN_12aa&DEV_5568
;&SUBSYS_00000000&REV_00
;---------- DDInstall Sections -----------------------------------------------
; --------- Windows 9X -----------------
; Experimentation has shown that DDInstall root names greater than 19 characters
; cause problems in Windows 98
[NiFr1S_DDI]
CopyFiles=NiFr1S_Files_Driver
AddReg=NiFr1S_9X_AddReg
[NiFr1S_9X_AddReg]
HKR,,DevLoader,,*ntkern
HKR,,NTMPDriver,,NiFr1S.sys
HKR, "Parameters", "BreakOnEntry", 0x00010001, 0
; --------- Windows NT -----------------
[NiFr1S_DDI.NT]
CopyFiles=NiFr1S_Files_Driver
AddReg=NiFr1S_NT_AddReg
[NiFr1S_DDI.NT.Services]
Addservice = NiFr1S, 0x00000002, NiFr1S_AddService
[NiFr1S_AddService]
DisplayName = %SvcDesc%
ServiceType = 1 ; SERVICE_KERNEL_DRIVER
StartType = 3 ; SERVICE_DEMAND_START
ErrorControl = 1 ; SERVICE_ERROR_NORMAL
ServiceBinary = %10%\System32\Drivers\NiFr1S.sys
[NiFr1S_NT_AddReg]
HKLM, "System\CurrentControlSet\Services\NiFr1S\Parameters",\
"BreakOnEntry", 0x00010001, 0
; --------- Files (common) -------------
[NiFr1S_Files_Driver]
NiFr1S.sys
;--------- Strings Section ---------------------------------------------------
[Strings]
ProviderName="Network Instruments, LLC"
MfgName="Network Instruments, LLC"
DeviceDesc="T1/E1 WAN Analyzer (Serial)"
DeviceClassName="NI Protocol Analyzers"
SvcDesc="T1/E1 WAN Analyzer (Serial)"