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

Null pointer returned by DAT_IMAGENATIVEXFER

Forums › TWAIN Classic › Null pointer returned by DAT_IMAGENATIVEXFER

  • This topic has 1 reply, 2 voices, and was last updated 14 years, 2 months ago by dpenney.
Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • November 14, 2006 at 11:05 pm #22037 Reply
    cardbox
    Participant
    • Topics - 1
    • Replies - 0
    • Total Posts - 1

    One of my users is having the following problem with a DS Dual3 1.0 data source under Windows:

    DAT_IMAGENATIVEXFER / MSG_GET

    returns TWRC_XFERDONE, but the pointer returned by the call is NULL instead of being a global memory handle.

    I can’t see any mention in the TWAIN specification of this being a legitimate result of the call. If the return code is not an error code, then surely a valid handle should be passed back to the calling program?

    Am I right that this is invalid behaviour by the data source?
    Has anyone else come across this behaviour, with this data source or others?
    Any ideas as to what might be causing the error?
    Any suggestions for working round it?

    (I should add that this is production code and has worked well for many people with many different data sources, so if the bug is ours then it must be a pretty specialised one)

    November 20, 2006 at 5:09 pm #23532 Reply
    dpenney
    Participant
    • Topics - 3
    • Replies - 66
    • Total Posts - 69

    You say your code works with many different DS’s but fails with a particular one. That’s a strong indication (but not a guarantee) that the problem is in that DS. You can switch to a memory or file transfer or contact the vendor to try to get the bug fixed.

    The TWAIN specification says DS’s are required to support native transfers but very few applications use this transfer method. Vendors usually have a suite of apps they use for Quality Assurance testing. This bug would slip right through QA if the DS is not tested with an app that uses native transfers.

  • Author
    Posts
Viewing 2 posts - 1 through 2 (of 2 total)
Reply To: Null pointer returned by DAT_IMAGENATIVEXFER
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

  • EPSON V600 TWAIN and WIA on Windows 10
  • When and how to use WaitForEvents command ?
  • Problem enumerating list of installed scanners in windows server 2012
  • Failed to create TWAIN progress! Error code is 1260.
  • To get the list of scanners from javascript client side (browser)
  • 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.