TWAIN Working Group

Newsletter Signup
Donate
Help keep TWAIN free
  • About TWAIN
    • What’s New?
    • News
    • Events
    • Membership
    • Consider a Donation
    • Contact Us
  • Why TWAIN?
  • Developers
    • Driver Developer
    • Application Developer
    • TWAIN Features
    • Specification & Tools
    • Self Certification Process
  • Support Forums
  • Scanner End-User
  • Find Certified Drivers
    • Facebook
    • LinkedIn
    • Vimeo

Windows Server 2003 Terminal Services

Forums › TWAIN Classic › Windows Server 2003 Terminal Services

  • This topic has 3 replies, 3 voices, and was last updated 13 years, 4 months ago by gabe.
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • May 31, 2007 at 2:05 pm #22152 Reply
    thomh
    Participant
    • Topics - 1
    • Replies - 0
    • Total Posts - 1

    We have installed a Xerox WorkCentre 7132 network printer/scanner in a Windows Server 2003 Terminal Services environment. It was installed correctly using the Add/Remove programs in Control Panel. Have also checked that the WIA service is running.

    When using Twack_32 application -> File -> Select Source, it does appear in the list. In fact no Twain scanner drivers that are installed appear in the list.

    If we install on a regular workstation it appears in the Select Source list and works fine.

    Is there a problem with Twain running in a Windows Server 2003 Terminal Services environment?

    Thanks.
    Thom

    June 1, 2007 at 7:22 am #23835 Reply
    gabe
    Participant
    • Topics - 9
    • Replies - 583
    • Total Posts - 592

    plugging the twain device into the ts… I would suggest against it there are usually better solutions. I know this doesn’t answer your question, and I’m not sure why you sources don’t show up in twackers – I would check that the .ds files exist in the %windir%twain_32 dir on the ts and that the users have access to the directory. From there I would probably either step thru the twacker code or even better run filemon to see what files are getting accessed on the ts.

    On the side, ts is odd enough on its own andfor that matter twain isn’t really something I would can clean but mixing in WIA which tends to muck with twain and twain solutions is my my experience just asking for trouble.

    For our ts users we have all the twain stuff on the workstations where the users will be working and then an app on the ts that talks to each of the workstations to acquire stuff – it works pretty well.

    November 29, 2007 at 4:47 pm #23836 Reply
    mcm
    Participant
    • Topics - 0
    • Replies - 2
    • Total Posts - 2

    On a terminal server the GetWindowsDirectory/GetWinDir doesn’t return C:WINNT but instead a windows directory under the users account.
    To get around this problem you can either copy the TWAIN files (twain.dll, twain_32.dll, twunk_16.exe and twunk_32.exe) to the above mentioned user “windows” directory and create a TWAIN_32 folder in the same for the data sources, or you can set a registry compatibility flag for you application to get GetWindowsDirectory to return the true Windows directory.
    Refer to http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B186499

    In the registry folder:

    HKEY_LOCAL_MACHINESoftwareMicrosoftWindows NTCurrentVersionTerminal ServerCompatibilityApplicationsAppname

    set Flags (a reg_dword) to 408h if you application is 32 bit. The value 40Ch may be more appropriate, as this seems to be quite common for all the pre-existing keys. This last flag mean Win-32, Win-16 and return literal windows dir.
    “Appname” above is your applications file name minus the “.exe” part.

    A last note – this will most likely only work if the scanner is physically attached to the Terminal server’s (COM, LPT, SCSI or USB) port.

    November 29, 2007 at 9:39 pm #23837 Reply
    gabe
    Participant
    • Topics - 9
    • Replies - 583
    • Total Posts - 592

    @mcm wrote:

    On a terminal server the GetWindowsDirectory/GetWinDir doesn’t return C:WINNT but instead a windows directory under the users account.
    To get around this problem you can either copy the TWAIN files…

    or if you can get the developers to use GetSystemWindowsDirectory instead of GetWindowsDirectory|GetWinDir.

    but good call on the wrong function being used to feed the load library call, that didn’t occur to me even though I’ve had that problem..

    .

  • Author
    Posts
Viewing 4 posts - 1 through 4 (of 4 total)
Reply To: Windows Server 2003 Terminal Services
Your information:




Quick Links

Service Providers
TWAIN Support Forums
Membership
Contact Us
Privacy Policy

Newsletter Signup

TWAIN Working Group Family

TWAIN Working Group
TWAIN Direct®
TWAIN Resources
TWAIN Certified Drivers
PDF/raster

  • Facebook
  • GitHub
  • LinkedIn
  • Vimeo

Recent Topics

  • TWAIN for dental imaging integration
  • PDF/R For who and where?
  • Making searchable PDF with PDF/R
  • Backward compatibility with PDF/A and traditional PDF
  • could not open the twain source. Make sure there is a valid source for your sca
  • Quarterly Newsletter
  • TWAIN Working Group Membership
  • Logo Usage
  • TWAIN License
  • Contact Us
Privacy Policy • Privacy Tools • Copyright © 2021 TWAIN Working Group • by iHwy, LLC • Log in

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.