Modify an old Device Driver for MISSIL 4302HD Mp4 Player?

Hi!

I recently purchased a MISSIL 4302HD MP4 player that is really cool, but
Windows 7 does not revognize it. When I tried to install the .inf files
manually, it also errored.

I have posted the entire contents of my supplied cd here:

http://www.top10google.com/MISSILE-4302HD-CD.zip

There are two .inf files, here is the FIRST:

;; Jz4740_usb.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 Windows DDK documentation contains an excellent INF reference.

;--------- Version Section ---------------------------------------------------

[Version]
Signature="$Windows 95$"

; 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}
Provider=%ProviderName%


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

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

[Manufacturer]
%MfgName%=Mfg0

[Mfg0]
%DeviceDesc%=Jz4740_usb_DDI, USB\VID_2008&PID_0808

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

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

[Jz4740_usb_DDI]
CopyFiles=Jz4740_usb_Files_Driver
AddReg=Jz4740_usb_9X_AddReg

[Jz4740_usb_9X_AddReg]
HKR,,DevLoader,,*ntkern
HKR,,NTMPDriver,,jz4740_usb.sys
HKR, "Parameters", "BreakOnEntry", 0x00010001, 0
; --------- Windows NT -----------------

[Jz4740_usb_DDI.NT]
CopyFiles=Jz4740_usb_Files_Driver
AddReg=Jz4740_usb_NT_AddReg

[Jz4740_usb_DDI.NT.Services]
Addservice = Jz4740_usb, 0x00000002, Jz4740_usb_AddService

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

[Jz4740_usb_NT_AddReg]
HKLM, "System\CurrentControlSet\Services\Jz4740_usb\Para meters",\
"BreakOnEntry", 0x00010001, 0



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

[Jz4740_usb_Files_Driver]
jz4740_usb.sys

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

[Strings]
ProviderName="Chinachip Tech"
MfgName="Chinachip Tech"
DeviceDesc="Chinachip USB Loader"
DeviceClassName="Chinachip USB Loader class"
SvcDesc="Chinachip USB Loader NT service"


>>>>>>>>>>>>>> HERE IS THE SECOND .INF FILE <<<<<<<<<<<<<<<

;; Jz4740_usb.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 Windows DDK documentation contains an excellent INF reference.

;--------- Version Section ---------------------------------------------------

[Version]
Signature="$Windows 95$"

; 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}
Provider=%ProviderName%


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

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

[Manufacturer]
%MfgName%=Mfg0

[Mfg0]
%DeviceDesc%=Jz4740_usb_DDI, USB\VID_2008&PID_0808

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

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

[Jz4740_usb_DDI]
CopyFiles=Jz4740_usb_Files_Driver
AddReg=Jz4740_usb_9X_AddReg

[Jz4740_usb_9X_AddReg]
HKR,,DevLoader,,*ntkern
HKR,,NTMPDriver,,jz4740_usb.sys
HKR, "Parameters", "BreakOnEntry", 0x00010001, 0
; --------- Windows NT -----------------

[Jz4740_usb_DDI.NT]
CopyFiles=Jz4740_usb_Files_Driver
AddReg=Jz4740_usb_NT_AddReg

[Jz4740_usb_DDI.NT.Services]
Addservice = Jz4740_usb, 0x00000002, Jz4740_usb_AddService

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

[Jz4740_usb_NT_AddReg]
HKLM, "System\CurrentControlSet\Services\Jz4740_usb\Para meters",\
"BreakOnEntry", 0x00010001, 0



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

[Jz4740_usb_Files_Driver]
jz4740_usb.sys

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

[Strings]
ProviderName="Chinachip Tech"
MfgName="Chinachip Tech"
DeviceDesc="Chinachip USB Loader"
DeviceClassName="Chinachip USB Loader class"
SvcDesc="Chinachip USB Loader NT service"

What is the exact error message?
If you were not logged in as administrator, do so.
--pa

"kcarring" <> wrote in message
news:19E4428A-48B0-4A3E-BC0F-...
> Hi!
>
> I recently purchased a MISSIL 4302HD MP4 player that is really cool, but
> Windows 7 does not revognize it. When I tried to install the .inf files
> manually, it also errored.
>
> I have posted the entire contents of my supplied cd here:
>
> http://www.top10google.com/MISSILE-4302HD-CD.zip
>
> There are two .inf files, here is the FIRST:
>
> ;; Jz4740_usb.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 Windows DDK documentation contains an excellent INF reference.
>
> ;--------- Version
> Section ---------------------------------------------------
>
> [Version]
> Signature="$Windows 95$"
>
> ; 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}
> Provider=%ProviderName%
>
>
> ;--------- 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]
> ;jz4740_usb.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]
> Jz4740_usb_Files_Driver = 10,System32\Drivers
>
> ;--------- Manufacturer and Models
> Sections ----------------------------------
>
> [Manufacturer]
> %MfgName%=Mfg0
>
> [Mfg0]
> %DeviceDesc%=Jz4740_usb_DDI, USB\VID_2008&PID_0808
>
> ;---------- DDInstall
> Sections -----------------------------------------------
> ; --------- Windows 9X -----------------
>
> ; Experimentation has shown that DDInstall root names greater than 19
> characters
> ; cause problems in Windows 98
>
> [Jz4740_usb_DDI]
> CopyFiles=Jz4740_usb_Files_Driver
> AddReg=Jz4740_usb_9X_AddReg
>
> [Jz4740_usb_9X_AddReg]
> HKR,,DevLoader,,*ntkern
> HKR,,NTMPDriver,,jz4740_usb.sys
> HKR, "Parameters", "BreakOnEntry", 0x00010001, 0
> ; --------- Windows NT -----------------
>
> [Jz4740_usb_DDI.NT]
> CopyFiles=Jz4740_usb_Files_Driver
> AddReg=Jz4740_usb_NT_AddReg
>
> [Jz4740_usb_DDI.NT.Services]
> Addservice = Jz4740_usb, 0x00000002, Jz4740_usb_AddService
>
> [Jz4740_usb_AddService]
> DisplayName = %SvcDesc%
> ServiceType = 1 ; SERVICE_KERNEL_DRIVER
> StartType = 3 ; SERVICE_DEMAND_START
> ErrorControl = 1 ; SERVICE_ERROR_NORMAL
> ServiceBinary = %10%\System32\Drivers\jz4740_usb.sys
>
> [Jz4740_usb_NT_AddReg]
> HKLM, "System\CurrentControlSet\Services\Jz4740_usb\Para meters",\
> "BreakOnEntry", 0x00010001, 0
>
>
>
> ; --------- Files (common) -------------
>
> [Jz4740_usb_Files_Driver]
> jz4740_usb.sys
>
> ;--------- Strings
> Section ---------------------------------------------------
>
> [Strings]
> ProviderName="Chinachip Tech"
> MfgName="Chinachip Tech"
> DeviceDesc="Chinachip USB Loader"
> DeviceClassName="Chinachip USB Loader class"
> SvcDesc="Chinachip USB Loader NT service"
>
>
>>>>>>>>>>>>>>> HERE IS THE SECOND .INF FILE <<<<<<<<<<<<<<<
>
> ;; Jz4740_usb.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 Windows DDK documentation contains an excellent INF reference.
>
> ;--------- Version
> Section ---------------------------------------------------
>
> [Version]
> Signature="$Windows 95$"
>
> ; 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}
> Provider=%ProviderName%
>
>
> ;--------- 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]
> ;jz4740_usb.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]
> Jz4740_usb_Files_Driver = 10,System32\Drivers
>
> ;--------- Manufacturer and Models
> Sections ----------------------------------
>
> [Manufacturer]
> %MfgName%=Mfg0
>
> [Mfg0]
> %DeviceDesc%=Jz4740_usb_DDI, USB\VID_2008&PID_0808
>
> ;---------- DDInstall
> Sections -----------------------------------------------
> ; --------- Windows 9X -----------------
>
> ; Experimentation has shown that DDInstall root names greater than 19
> characters
> ; cause problems in Windows 98
>
> [Jz4740_usb_DDI]
> CopyFiles=Jz4740_usb_Files_Driver
> AddReg=Jz4740_usb_9X_AddReg
>
> [Jz4740_usb_9X_AddReg]
> HKR,,DevLoader,,*ntkern
> HKR,,NTMPDriver,,jz4740_usb.sys
> HKR, "Parameters", "BreakOnEntry", 0x00010001, 0
> ; --------- Windows NT -----------------
>
> [Jz4740_usb_DDI.NT]
> CopyFiles=Jz4740_usb_Files_Driver
> AddReg=Jz4740_usb_NT_AddReg
>
> [Jz4740_usb_DDI.NT.Services]
> Addservice = Jz4740_usb, 0x00000002, Jz4740_usb_AddService
>
> [Jz4740_usb_AddService]
> DisplayName = %SvcDesc%
> ServiceType = 1 ; SERVICE_KERNEL_DRIVER
> StartType = 3 ; SERVICE_DEMAND_START
> ErrorControl = 1 ; SERVICE_ERROR_NORMAL
> ServiceBinary = %10%\System32\Drivers\jz4740_usb.sys
>
> [Jz4740_usb_NT_AddReg]
> HKLM, "System\CurrentControlSet\Services\Jz4740_usb\Para meters",\
> "BreakOnEntry", 0x00010001, 0
>
>
>
> ; --------- Files (common) -------------
>
> [Jz4740_usb_Files_Driver]
> jz4740_usb.sys
>
> ;--------- Strings
> Section ---------------------------------------------------
>
> [Strings]
> ProviderName="Chinachip Tech"
> MfgName="Chinachip Tech"
> DeviceDesc="Chinachip USB Loader"
> DeviceClassName="Chinachip USB Loader class"
> SvcDesc="Chinachip USB Loader NT service"
>

I just tried logging in as Administrator, and I get the same error:

"The INF file you have chosen does not support this type of installation".

When you read the book, it sounds as if when you first plug the player into
USB(it says, do it "hot" - but ive tried both hot and cold) - it will
autoplay the driver setup.

There is no "setup.exe" or the likes on the CD, and Windows 7 does not "see"
that I have attached a USB device like it would, say, my camcorder, digicam,
etc.



"Pavel A." wrote:

> What is the exact error message?
> If you were not logged in as administrator, do so.
> --pa

So when you plug the player in, a "new device found" dialog does not show
up?
Do you see this device somewhere in the device manager, maybe with yellow
bang sign?
If yes, click on update driver, select "from location" and browse to the
directory
on the CD where the INF files are located.

If you are sure that you follow the manufactirer installation instruction
correctly,
probably the player is broken. It happens.

--pa


"kcarring" <> wrote in message
news:4CE1D830-5951-43C2-AFCA-...
> I just tried logging in as Administrator, and I get the same error:
>
> "The INF file you have chosen does not support this type of installation".
>
> When you read the book, it sounds as if when you first plug the player
> into
> USB(it says, do it "hot" - but ive tried both hot and cold) - it will
> autoplay the driver setup.
>
> There is no "setup.exe" or the likes on the CD, and Windows 7 does not
> "see"
> that I have attached a USB device like it would, say, my camcorder,
> digicam,
> etc.
>
> "Pavel A." wrote:
>> What is the exact error message?
>> If you were not logged in as administrator, do so.
>> --pa
>

Windows 7 requires that the INF files are in UNICODE format.

SourceDiskNames and SourceDiskFiles may also be mandatory now. dpinst, for
example, will fail without them.

"kcarring" <> wrote in message
news:19E4428A-48B0-4A3E-BC0F-...
> Hi!
>
> I recently purchased a MISSIL 4302HD MP4 player that is really cool, but
> Windows 7 does not revognize it. When I tried to install the .inf files
> manually, it also errored.
>
> I have posted the entire contents of my supplied cd here:
>
> http://www.top10google.com/MISSILE-4302HD-CD.zip
>
> There are two .inf files, here is the FIRST:
>
> ;; Jz4740_usb.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 Windows DDK documentation contains an excellent INF reference.
>
> ;--------- Version
> Section ---------------------------------------------------
>
> [Version]
> Signature="$Windows 95$"
>
> ; 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}
> Provider=%ProviderName%
>
>
> ;--------- 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]
> ;jz4740_usb.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]
> Jz4740_usb_Files_Driver = 10,System32\Drivers
>
> ;--------- Manufacturer and Models
> Sections ----------------------------------
>
> [Manufacturer]
> %MfgName%=Mfg0
>
> [Mfg0]
> %DeviceDesc%=Jz4740_usb_DDI, USB\VID_2008&PID_0808
>
> ;---------- DDInstall
> Sections -----------------------------------------------
> ; --------- Windows 9X -----------------
>
> ; Experimentation has shown that DDInstall root names greater than 19
> characters
> ; cause problems in Windows 98
>
> [Jz4740_usb_DDI]
> CopyFiles=Jz4740_usb_Files_Driver
> AddReg=Jz4740_usb_9X_AddReg
>
> [Jz4740_usb_9X_AddReg]
> HKR,,DevLoader,,*ntkern
> HKR,,NTMPDriver,,jz4740_usb.sys
> HKR, "Parameters", "BreakOnEntry", 0x00010001, 0
> ; --------- Windows NT -----------------
>
> [Jz4740_usb_DDI.NT]
> CopyFiles=Jz4740_usb_Files_Driver
> AddReg=Jz4740_usb_NT_AddReg
>
> [Jz4740_usb_DDI.NT.Services]
> Addservice = Jz4740_usb, 0x00000002, Jz4740_usb_AddService
>
> [Jz4740_usb_AddService]
> DisplayName = %SvcDesc%
> ServiceType = 1 ; SERVICE_KERNEL_DRIVER
> StartType = 3 ; SERVICE_DEMAND_START
> ErrorControl = 1 ; SERVICE_ERROR_NORMAL
> ServiceBinary = %10%\System32\Drivers\jz4740_usb.sys
>
> [Jz4740_usb_NT_AddReg]
> HKLM, "System\CurrentControlSet\Services\Jz4740_usb\Para meters",\
> "BreakOnEntry", 0x00010001, 0
>
>
>
> ; --------- Files (common) -------------
>
> [Jz4740_usb_Files_Driver]
> jz4740_usb.sys
>
> ;--------- Strings
> Section ---------------------------------------------------
>
> [Strings]
> ProviderName="Chinachip Tech"
> MfgName="Chinachip Tech"
> DeviceDesc="Chinachip USB Loader"
> DeviceClassName="Chinachip USB Loader class"
> SvcDesc="Chinachip USB Loader NT service"
>
>
>>>>>>>>>>>>>>> HERE IS THE SECOND .INF FILE <<<<<<<<<<<<<<<
>
> ;; Jz4740_usb.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 Windows DDK documentation contains an excellent INF reference.
>
> ;--------- Version
> Section ---------------------------------------------------
>
> [Version]
> Signature="$Windows 95$"
>
> ; 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}
> Provider=%ProviderName%
>
>
> ;--------- 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]
> ;jz4740_usb.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]
> Jz4740_usb_Files_Driver = 10,System32\Drivers
>
> ;--------- Manufacturer and Models
> Sections ----------------------------------
>
> [Manufacturer]
> %MfgName%=Mfg0
>
> [Mfg0]
> %DeviceDesc%=Jz4740_usb_DDI, USB\VID_2008&PID_0808
>
> ;---------- DDInstall
> Sections -----------------------------------------------
> ; --------- Windows 9X -----------------
>
> ; Experimentation has shown that DDInstall root names greater than 19
> characters
> ; cause problems in Windows 98
>
> [Jz4740_usb_DDI]
> CopyFiles=Jz4740_usb_Files_Driver
> AddReg=Jz4740_usb_9X_AddReg
>
> [Jz4740_usb_9X_AddReg]
> HKR,,DevLoader,,*ntkern
> HKR,,NTMPDriver,,jz4740_usb.sys
> HKR, "Parameters", "BreakOnEntry", 0x00010001, 0
> ; --------- Windows NT -----------------
>
> [Jz4740_usb_DDI.NT]
> CopyFiles=Jz4740_usb_Files_Driver
> AddReg=Jz4740_usb_NT_AddReg
>
> [Jz4740_usb_DDI.NT.Services]
> Addservice = Jz4740_usb, 0x00000002, Jz4740_usb_AddService
>
> [Jz4740_usb_AddService]
> DisplayName = %SvcDesc%
> ServiceType = 1 ; SERVICE_KERNEL_DRIVER
> StartType = 3 ; SERVICE_DEMAND_START
> ErrorControl = 1 ; SERVICE_ERROR_NORMAL
> ServiceBinary = %10%\System32\Drivers\jz4740_usb.sys
>
> [Jz4740_usb_NT_AddReg]
> HKLM, "System\CurrentControlSet\Services\Jz4740_usb\Para meters",\
> "BreakOnEntry", 0x00010001, 0
>
>
>
> ; --------- Files (common) -------------
>
> [Jz4740_usb_Files_Driver]
> jz4740_usb.sys
>
> ;--------- Strings
> Section ---------------------------------------------------
>
> [Strings]
> ProviderName="Chinachip Tech"
> MfgName="Chinachip Tech"
> DeviceDesc="Chinachip USB Loader"
> DeviceClassName="Chinachip USB Loader class"
> SvcDesc="Chinachip USB Loader NT service"
>

I tried a different USB port, and this time, it did come up. It shows it as
Drive Q. I was able to move some files to it this time. I'm now guessing
there is no actual "control" software (though the book says there is,
although it is rough translation from chinese). It allows one to move files,
in it's "update mode" - but then if you hit a Mode button, you lose that
ability.. and the device says "update is finished". so... I guess I was a bit
fooled. Odd thing is, it doesn't seem to be charging, so I'll just leave it
for a day hooked to this usb port, and then attempt to play a song etc. I
think it may be working. When it "is" being recognized, I will also check out
Device Manager and see if updating the driver is possible... when I looked,
it had "disappeared" as explained above. Thanks for your help!

"Alexander Grigoriev" <> writes:

> Windows 7 requires that the INF files are in UNICODE format.

Is that so even if the file contains ASCII characters only?
Does UNICODE here mean only little-endian UTF-16 with BOM,
or also UTF-8 with BOM?

"Alexander Grigoriev" <> wrote:
>
>Windows 7 requires that the INF files are in UNICODE format.

I'm not sure where you read this, but it's nonsense. Nothing has changed
in this regard.

>SourceDiskNames and SourceDiskFiles may also be mandatory now. dpinst, for
>example, will fail without them.

I'm not sure what to say about this. SourceDiskNames and SourceDiskFiles
have always been mandatory, as infchk tells you. DPinst uses them to
decide which files to copy to the driver store. I don't think anything has
changed in this regard for the latest WDK.
--
Tim Roberts,
Providenza & Boekelheide, Inc.

I have noticed in the latest WDK that the samples provided do seem to have
UNICODE source files. It is a real pain in some ways, but if you have
language sensitive text, then it makes sense.

"Tim Roberts" <> wrote in message
news:...
> "Alexander Grigoriev" <> wrote:
>>
>>Windows 7 requires that the INF files are in UNICODE format.
>
> I'm not sure where you read this, but it's nonsense. Nothing has changed
> in this regard.
>
>>SourceDiskNames and SourceDiskFiles may also be mandatory now. dpinst, for
>>example, will fail without them.
>
> I'm not sure what to say about this. SourceDiskNames and SourceDiskFiles
> have always been mandatory, as infchk tells you. DPinst uses them to
> decide which files to copy to the driver store. I don't think anything
> has
> changed in this regard for the latest WDK.
> --
> Tim Roberts,
> Providenza & Boekelheide, Inc.

Typing too fast. UNICODE inx files. Most source is still ASCII, I think.

"David Craig" <> wrote in message
news:...
>I have noticed in the latest WDK that the samples provided do seem to have
>UNICODE source files. It is a real pain in some ways, but if you have
>language sensitive text, then it makes sense.
>
> "Tim Roberts" <> wrote in message
> news:...
>> "Alexander Grigoriev" <> wrote:
>>>
>>>Windows 7 requires that the INF files are in UNICODE format.
>>
>> I'm not sure where you read this, but it's nonsense. Nothing has changed
>> in this regard.
>>
>>>SourceDiskNames and SourceDiskFiles may also be mandatory now. dpinst,
>>>for
>>>example, will fail without them.
>>
>> I'm not sure what to say about this. SourceDiskNames and SourceDiskFiles
>> have always been mandatory, as infchk tells you. DPinst uses them to
>> decide which files to copy to the driver store. I don't think anything
>> has
>> changed in this regard for the latest WDK.
>> --
>> Tim Roberts,
>> Providenza & Boekelheide, Inc.
>
>