Based on the log it looks like we are making a call into the driver and the driver never responds.  There isn't much that can be done about that, but here are a couple things to try:Change the value of Device.ModalAcquire.  Sometimes having ModalAcquire set to true will help, but if the same driver works on other systems it probably ...

There is no way to pause the undo manager.  I'll add this to our feature request list.

If the scanner is not skipping blank pages, you can go by the order.  The first image should be the front and the second the back. If the scanner is setup to skip blank pages, it would have to be a driver that supports the CAP_CAMERASIDE capability.  You can use the Device.QuerySupport method to see if the driver supports this.

I've never seen this before, but it would have to be a driver bug.  There's really nothing you can do about it other than make sure you have the latest drivers.

Setting ModalAcquire to false does not provide the threading I'm talking about.  You would need to create a separate Thread object and run all DotTwain code, including the Form that acts as its parent, in that thread.  Then if your application has not received an event within a certain amount of time you can allow the user to kill the ...

It sounds like you're trying to install the license files onto another machine.  Instead you should be embedding the licenses into your EXE.  This KB should help:  http://www.atalasoft.com/KB/article.aspx?id=10128

You can either attach it to this forum thread or open a support case.

Can you provide a simple project showing this issue?

Visual Studio 2005 did not work correctly on 64-bit systems when trying to build 32-bit applications.  Try adding the build events from this KB:  http://www.atalasoft.com/KB/article.aspx?id=10149

This is strange.  There is no difference in the DotTwain code between .NET 1.1 and 2.0 builds, so perhaps something in the framework itself could be causing this. 1.  Have you created a DotTwain trace log?  This is the only way for us to see what is happening inside DotTwain. 2.  Does this happen when running our Acquisition ...