Re: Component of EyeOne driver files on Windows
Re: Component of EyeOne driver files on Windows
- Subject: Re: Component of EyeOne driver files on Windows
- From: Graeme Gill <email@hidden>
- Date: Mon, 31 Jan 2011 15:38:21 +1100
Roger Breton wrote:
Somehow, based on my humble understanding of Windows's architecture, I sense
that the "i1.sys" is the actual 32-bit (or 64-bit) device driver, that
"talks" to the instrument directly (in Kernel mode?). Its job is to allocate
ports for applications to communicate with the instrument, writing commands
and reading measurements of those ports and use it to retrieve status
information.
Yes.
But I am not sure what role the "EyeOne.dll" plays here?
I gather that the "EyeOne.dll" provides some APIs that most likely allow
communicating with the instrument/driver from an application?
The .dll acts as an intermediary between the kernel driver and
the application. It opens the port to the kernel driver, and will
(typically) add extra convenience facilities over the top.
[In the specific case of the EyeOne, the kernel driver doesn't
do much - it just transfers USB packets to/from the .dll. The guts
of the instrument driver is in the .dll, together with all the
libraries for massaging color values etc.]
Graeme Gill.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Colorsync-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden