GameFace130/Data1.cab/Video3D.inf Driver File Contents (GameFace130.zip)

Driver Package File Name: GameFace130.zip
File Size: 6.8 MB

;; Video3D.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="$Windows 95$"
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=AsusOtherDevices
ClassGUID={5458011F-08D4-4605-93A2-F03E61BEDBA3}
;Class=NewDeviceClass
;ClassGUID={ff646f80-8def-11d2-9449-00105a075f6b}
;Class=Media
;ClassGUID={4D36E96C-E325-11CE-BFC1-08002BE10318}

DriverVer = 02/25/2003, 1.0.0.0
catalogfile = video3d.cat
;--------- 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]
;Video3D.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,,"-18"

;--------- DestinationDirs Section -------------------------------------------

[DestinationDirs]
Video3D_Files_Driver = 10,System32\Drivers

;--------- Manufacturer and Models Sections ----------------------------------

[Manufacturer]
%MfgName%=Mfg0

[Mfg0]
%DeviceDesc%=Video3D_DDI, *Video3D

;---------- DDInstall Sections -----------------------------------------------
; --------- Windows 9X -----------------

; Experimentation has shown that DDInstall root names greater than 19 characters
; cause problems in Windows 98

[Video3D_DDI]
CopyFiles=Video3D_Files_Driver
AddReg=Video3D_9X_AddReg

[Video3D_9X_AddReg]
HKR,,DevLoader,,*ntkern
HKR,,NTMPDriver,,Video3D.sys
HKR, "Parameters", "BreakOnEntry", 0x00010001, 0

; --------- Windows NT -----------------

[Video3D_DDI.NT]
CopyFiles=Video3D_Files_Driver
AddReg=Video3D_NT_AddReg

[Video3D_DDI.NT.Services]
Addservice = Video3D, 0x00000002, Video3D_AddService

[Video3D_AddService]
DisplayName    = %SvcDesc%
ServiceType    = 1                  ; SERVICE_KERNEL_DRIVER
StartType      = 3                  ; SERVICE_DEMAND_START
ErrorControl   = 1                  ; SERVICE_ERROR_NORMAL
ServiceBinary  = %10%\System32\Drivers\Video3D.sys

[Video3D_NT_AddReg]
HKLM, "System\CurrentControlSet\Services\Video3D\Parameters",\
	"BreakOnEntry", 0x00010001, 0


; --------- Files (common) -------------

[Video3D_Files_Driver]
;Video3D.sys

;--------- Strings Section ---------------------------------------------------

[Strings]
ProviderName="ASUSTeK"
MfgName="ASUSTeK"
DeviceDesc="Asus Video3D Device"
DeviceClassName="ASUS Other Devices"
SvcDesc="ASUS Video3D Service"
server: web4, load: 0.63