为什么DS生成的INF文件经过必要的修改后总是不能用？？？？？？

大家帮我看看这段INF文件有什么错？
ezDriverInstall老是报错，始终装不上去。

;; Test3.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=Unknown
ClassGUID={ff646f80-8def-11d2-9449-00105a075f6b}

;--------- 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]
;Test3.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]
Test3_Files_Driver = 10,System32\\Drivers

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

[Manufacturer]
%MfgName%=Mfg0

[Mfg0]
%DeviceDesc%=Test3_DDI, !test!

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

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

[Test3_DDI]
CopyFiles=Test3_Files_Driver
AddReg=Test3_9X_AddReg
LogConfig=Test3_Config

[Test3_9X_AddReg]
HKR,,DevLoader,,*ntkern
HKR,,NTMPDriver,,Test3.sys
HKR, \"Parameters\", \"BreakOnEntry\", 0x00010001, 0

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

[Test3_DDI.NT]
CopyFiles=Test3_Files_Driver
AddReg=Test3_NT_AddReg
LogConfig=Test3_Config

[Test3_DDI.NT.Services]
Addservice = Test3, 0x00000002, Test3_AddService

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

[Test3_NT_AddReg]
HKLM, \"System\\CurrentControlSet\\Services\\Test3\\Parameters\",\\
\"BreakOnEntry\", 0x00010001, 0

; ------ Logical Config (common) -------

[Test3_Config]
; This is the logical configuration for the device. If the device has no
; hardware resources, you can remove this section, and remove the reference
; to it in section [Test3_Device]
;
ConfigPriority=NORMAL
; The allowed values for ConfigPriority are:
; HARDWIRED Cannot be reset in any way
; DESIRED Soft Configurable most optimal
; NORMAL Soft Configured medium optimal
; SUBOPTIMAL Soft Configured least optimal
; DISABLED Hardware disabled
; RESTART Requires Windows restart to affect
; REBOOT Requires system reboot to affect
; POWEROFF Requires power cycle to affect
; HARDRECONFIG Requires Jumper setting
;
IRQConfig=4,5,9,10,11
;; TODO: You must replace IRQNUM in the line above with the correct IRQ for your device

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

[Test3_Files_Driver]
Test3.sys

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

[Strings]
ProviderName=\"Your Company Name here\"
MfgName=\"Name of HW Manufacturer here\"
DeviceDesc=\"Description of Device here\"
DeviceClassName=\"Description of Device class here\"
SvcDesc=\"Description of NT service here\"