Component of EyeOne driver files on Windows
Component of EyeOne driver files on Windows
- Subject: Component of EyeOne driver files on Windows
- From: Roger Breton <email@hidden>
- Date: Sun, 30 Jan 2011 18:06:51 -0500
Hello group,
I am looking for some help to clear out what is what, on Windows, as far as
support files are concerned to drive the EyeOne family of devices.
To me, there are two obvious components, "i1.sys" and "EyeOne.dll".
But is there more than those two essential components?
As far as I can see, "i1.sys" is at v1.5 and "EyeOne.dll" is at v3.4.0.131.
If you know about other required components, please let me know.
Also, does it make sense to say that some applications will use the system
driver ("i1.sys") directly while others will go through "EyeOne.dll"
*without* going through "i1.sys"?
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.
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?
If there are any X-Rite documentation that you know could help clear up that
smoke, I'd be interested to study it.
Maybe I need the SDK?
Best / Roger
_______________________________________________
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