TWAIN driver work on Windows 2003 server or Citrix…

[MassayParticipant Topics - 9Replies - 2Total Posts - 11]

Dear all TWAIN friends,

Now we plan to develop an application which works with Citrix system. but there is an issue which is from our customer, Can you help to check the issue? Thanks So much….

//

---

Basically what is happening is the software is not reading the twain_32.dll file that is in the C:windows directory. It’s actually looking for it in the c:documents and settings%username%windows directory. Since all the users have roaming profiles it’ll look for it there. In Windows2003 the windows directory has been moved from the profile to the home directory. So in our case it would be located on \swizznetfs01users%username%windows.

Hopefully I didn’t lose you. If you run across a user who can’t scan through page manager, just log into Swizznetfs01 and go to the D: drive, open up a user folder that you know scanning works and click on windows and copy the twain_32.dll file and past into the same directory on the user that isn’t able to scan. Have the user completely log off and you’re done.

//

---

As we know, TWAIN_32.dll is put in windows system directory, not in user path, Can you help to provide some useful information for the issue?

Thanks again.

best wishes

massay 🙂

[gabeParticipant Topics - 9Replies - 583Total Posts - 592]

the problem you’re describling is often just an issue of what path you use when you call loadlibrary.
On a terminal server the GetWindowsDirectory/GetWinDir doesn’t return C:WINNT but instead a windows directory under the users account, use GetSystemWindowsDirectory instead, or load both (one after another) and track the selected source with respect to which twain_32.dll it lives in.

see: http://msdn2.microsoft.com/en-us/library/ms724403(VS.85).aspx

[MassayParticipant Topics - 9Replies - 2Total Posts - 11]

Dear gabe,

Thanks for your help.

I will modify the function in my side.

Thanks & best wishes

Massay

[Author]

Posts