Home › Forums › TWAIN Classic › Connecting to TWAIN failed in a streamed (isolated) env.
- This topic has 1 reply, 2 voices, and was last updated 15 years, 8 months ago by gabe.
- AuthorPosts
Hello!Fine to be here 😉
I have an abstract problem with a special environment:
Server:
W2K3SP1 std. GER
Citrix Presentation Server (XenApp) 4.5 R02
HP Precisionscan 3.13Client:
XPSP2 GER
hp scanjet 5470cApplication presentation:
It is a “streamed” Application to the Server. This means you snapshot the installation of a program into a sandbox.
• This is stored into an image file.
• This File contains File- and Registryinformation.Now, there are two ways to deliver this streamed app to the user:
1. Stream it to the client directly
2. Stream it to the Server and tunnel it into the ica-protocollWe try to find a solution for #2!
Additional Information:
• In our Lab we have tested the Citrix-functionality “TWAIN-Redirection” without a streamed App. This works! A few guys answered in this forum to these questions.
• While putting the streamed app into the sandbox, we can choose to bypass NAMED-OBJECTS to the system-os directly. If we do so, it works!!!Goal:
• I want to narrow down these named objects to determine which object is causing the problem.
• If I get the missing objects I can write a better, smaller filter for my appQuestion:
How can I identify these named objects?TIA (really)
Bernd
PS: I am not a programmer, so talk “easy” 😉
I thought named objects were primarily for interprocess communication. There is no documentation for interprocess communication in the twain specification. I don’t think you’re going to find an answer to this here, sorry
.
- AuthorPosts