I work in a clinical environment, and one of the applications we are ThinApp'ing will be utilized by persons performing registration, and will require for documents to be scanned into the application from ADF scanners.
Initial attempts to have the ThinApp'd app scan have proven unfruitful. The application seems to be able to see the scanner. When I click on the menu that lets me choose a scanner, it is listed in the dropdown list correctly. However, when I actually attempt to scan, the application gives an error message stating that it cannot communicate with the scanner. My suspicions are that the scanner isn't able to communicate back with the process from the app that is initializing the scan, since the app is in the virtual environment, and the scanner is not. The message generated also includes references to the scanner model.
Here are some methods I've attempted in order to get this going. I'll admit, I'm definitely not a guru when it comes to reading out logmon reports, so I may be going the wrong direction with this.
- ChildProcessEnvironementDefault=External to force Child processes to load in the physical environment
- AllowExternalProcessModifications=1
- ExternalDLLs= listing all of the dll's it seems the application uses to scan
Does anyone have any insight on what would be needed to get this application to scan? I do realize that virtualizing the twain drivers is not possible, but I didn't know if that meant that working with twain scanners from within a ThinApp was impossible as well.
Any feedback or direction would be appreciated.