Wouldn’t this depend on the wrapper you’re using? But from a pure twain point of view, i would check if ICAP_SUPPORTEDSIZES was supported (if it shows up in cap_supportedcaps), get the supported msg_get with ICAP_SUPPORTEDSIZES should return a tw_oneValue or tw_enumeration (I usually see a tw_enumeration). From there I check if the current icap_supportedsize if already set to what I want and if needed set icap_supportedSizes with a tw_OneValue to the enumeration value that I want to use. But in the back of my head I seem to remember a couple of post about icap_supportedsizes being a bit unstable depending on the device you’re acquireing from and I think it was spike that had a routine for setting the layout then the papersize…. search the forum (and that other place that archives the forum) for supportedSizes. If you’re still having trouble, post back and I’ll give it more than 45 seconds of thought.
.