>>What do I think of this…
I think that the first time a user tries to use ms word to acquire an image that you’re going to get a call if they can find your number. If you don’t want the user to change a setting don’t tie that setting to your Ui – you’re writing the Ui, you can put whatever you want in there or not.
Also, think about what version of twain you’re writing you driver for. If you’re targetting twain 1.5 compability you (per the spec – chapter 3-64) must support:
CAP_SUPPORTEDCAPS MSG_GET required
CAP_XFERCOUNT All MSG_* operations required
ICAP_COMPRESSION All MSG_GET* operations required
ICAP_BITDEPTH All MSG_* operations required
ICAP_BITORDER All MSG_* operations required
ICAP_PLANARCHUNKY All MSG_GET* operations required
ICAP_PHYSICALHEIGHT All MSG_GET* operations required
ICAP_PHYSICALWIDTH All MSG_GET* operations required
ICAP_PIXELFLAVOR All MSG_GET* operations required
ICAP_PIXELTYPE All MSG_* operations required
ICAP_UNITS All MSG_* operations required
ICAP_XFERMECH All MSG_* operations required
ICAP_XRESOLUTION All MSG_* operations required
ICAP_YRESOLUTION All MSG_* operations required
and if you’re aiming for a more current spec you’ll have to add more.
…And yeah, none of that was really in answer to your question, but I do have something that may be useful for you: have you taken a look at the shell provided by dosadi? Take a look at ‘GenDS Toolkit’ over here: http://www.dosadi.com/beta_products.htm
Oh and take my comments lightly, I’ve never written a driver – but I have definate feelings for drivers that don’t follow the spec and the devs responsible.. 😉
.