[argyllcms] Re: Wanted: Spyder 3 and ColorMunki Beta Testers
- From: Graeme Gill <graeme@xxxxxxxxxxxxx>
- To: argyllcms@xxxxxxxxxxxxx
- Date: Wed, 04 Mar 2009 10:53:11 +1100
howdy555@xxxxxxxxx wrote:
Spyder 3 does not work :(...
1) There is no spyd3.inf file so the driver cannot be installed
(corrected by guessing my own version :) )
Yes, there was a typo in the file list. See .inf file attached.
2) Here are the compilation errors that seem to be important:
spectro\hidio.c: In function `icoms_hid_read_th':
spectro\hidio.c:559: warning: passing arg 4 of `ReadFile' from incompatible poin
ter type
spectro\hidio.c: In function `icoms_hid_write_th':
spectro\hidio.c:683: warning: passing arg 4 of `WriteFile' from incompatible poi
nter type
Thanks. (I haven't looked in detail at MingW output recently).
Cc_ tiff\port\strtoul.obj
tiff\port\strtoul.c: In function `strtoul':
tiff\port\strtoul.c:105: warning: assignment discards qualifiers from pointer ta
rget type
I'm not going to try and fix all the compiler warnings in the tiff library,
since I didn't write it :-) [There are many more using VC++6 ]
I also got a huge load of:
e:\temp/ccRw9D3g.s:502029: Warning: .stabn: description field '[5 hex
numbers]' too big, try a different debug format
but http://www.winehq.org/pipermail/wine-devel/2004-January/023964.html
tells that it does not matter. Doesn't it?
It's irritating, but shouldn't affect functionality (it seems the MingW
assembler needs updating).
3) Does the Spyder3 need the original firmware to work? If yes, is there a
version of spyd2en for Spyder3?
No it doesn't, that's why the documentation doesn't refer to it.
[They have used different hardware for the 3 that doesn't need
firmware uploaded, so it's much more convenient than the 2.]
4) [compilation issue] - can the USB driver be compiled using DDK
pathes set to win2k? It does not want to compile if I set them to
"xp". I used:
set DDK_INC_PATH=E:\WINDDK\3790.1830\inc\w2k
set DDK_LIB_PATH=E:\WINDDK\3790.1830\lib\w2k\i386
set MINGW=C:\MinGW
I'm not sure what you mean. In what way does it fail ?
Certain header files are needed during compilation, and the
associated library files to access HID devices. As long
as the DDK_INC_PATH and DDK_LIB_PATH environment variables
point to places where those files exist, it should work.
It doesn't matter for the Spyder anyway, this will just affect
access to the Huey, so at worst you could remove the
DDK_INC_PATH and DDK_LIB_PATH environment variables.
5) dispcal -D5 xx crashes.... Here is the screen output:
Sorry, there's nothing interesting there. What makes you say it
crashed ? (ie. you haven't shown anything that indicates or
show the details of this).
Graeme Gill.
[Version]
Signature = "$Chicago$"
provider = ArgyllCMS
DriverVer = 11/21/2007,0.1.12.1
CatalogFile = spyd3.cat
CatalogFile.NT = spyd3.cat
CatalogFile.NTAMD64 = spyd3_x64.cat
Class = LibUsbDevices
ClassGUID = {EB781AAF-9C70-4523-A5DF-642A87ECA567}
[ClassInstall]
AddReg=libusb_class_install_add_reg
[ClassInstall32]
AddReg=libusb_class_install_add_reg
[libusb_class_install_add_reg]
HKR,,,,"LibUSB-Win32 Devices"
HKR,,Icon,,"-20"
[Manufacturer]
%manufacturer%=Devices,NT,NTAMD64
;--------------------------------------------------------------------------
; Files
;--------------------------------------------------------------------------
[SourceDisksNames]
1 = "Libusb-Win32 Driver Installation Disk",,
[SourceDisksFiles]
libusb0.sys = 1,,
libusb0.dll = 1,,
libusb0_x64.sys = 1,,
libusb0_x64.dll = 1,,
[DestinationDirs]
libusb_files_sys = 10,system32\drivers
libusb_files_sys_x64 = 10,system32\drivers
libusb_files_dll = 10,system32
libusb_files_dll_wow64 = 10,syswow64
libusb_files_dll_x64 = 10,system32
[libusb_files_sys]
libusb0.sys
[libusb_files_sys_x64]
libusb0.sys,libusb0_x64.sys
[libusb_files_dll]
libusb0.dll
[libusb_files_dll_wow64]
libusb0.dll
[libusb_files_dll_x64]
libusb0.dll,libusb0_x64.dll
;--------------------------------------------------------------------------
; Device driver
;--------------------------------------------------------------------------
[LIBUSB_DEV]
CopyFiles = libusb_files_sys, libusb_files_dll
AddReg = libusb_add_reg
[LIBUSB_DEV.NT]
CopyFiles = libusb_files_sys, libusb_files_dll
[LIBUSB_DEV.NTAMD64]
CopyFiles = libusb_files_sys_x64, libusb_files_dll_wow64, libusb_files_dll_x64
[LIBUSB_DEV.HW]
DelReg = libusb_del_reg_hw
AddReg = libusb_add_reg_hw
[LIBUSB_DEV.NT.HW]
DelReg = libusb_del_reg_hw
AddReg = libusb_add_reg_hw
[LIBUSB_DEV.NTAMD64.HW]
DelReg = libusb_del_reg_hw
AddReg = libusb_add_reg_hw
[LIBUSB_DEV.NT.Services]
AddService = libusb0, 0x00000002, libusb_add_service
[LIBUSB_DEV.NTAMD64.Services]
AddService = libusb0, 0x00000002, libusb_add_service
[libusb_add_reg]
HKR,,DevLoader,,*ntkern
HKR,,NTMPDriver,,libusb0.sys
; Older versions of this .inf file installed filter drivers. They are not
; needed any more and must be removed
[libusb_del_reg_hw]
HKR,,LowerFilters
HKR,,UpperFilters
; Device properties
[libusb_add_reg_hw]
HKR,,SurpriseRemovalOK, 0x00010001, 1
;--------------------------------------------------------------------------
; Services
;--------------------------------------------------------------------------
[libusb_add_service]
DisplayName = "LibUsb-Win32 - Kernel Driver 11/21/2007, 0.1.12.1"
ServiceType = 1
StartType = 3
ErrorControl = 0
ServiceBinary = %12%\libusb0.sys
;--------------------------------------------------------------------------
; Devices
;--------------------------------------------------------------------------
[Devices]
"Spyder3 (Argyll)"=LIBUSB_DEV, USB\VID_085C&PID_0300
[Devices.NT]
"Spyder3 (Argyll)"=LIBUSB_DEV, USB\VID_085C&PID_0300
[Devices.NTAMD64]
"Spyder3 (Argyll)"=LIBUSB_DEV, USB\VID_085C&PID_0300
;--------------------------------------------------------------------------
; Strings
;--------------------------------------------------------------------------
[Strings]
DESCRIPTION="Spyder3 (Argyll)"
FriendlyName="Spyder3 (Argyll)"
manufacturer="Datacolor"
Other related posts:
