Home › Forums › TWAIN Classic › Device List – Error messages with MSG_GETFIRST
- This topic has 4 replies, 3 voices, and was last updated 15 years, 8 months ago by gabe.
- AuthorPosts
I am writing a custom dialog to list the currently available Twain devices. I am getting the list by calling the MSG_GETFIRST and MSG_GETNEXT for all the devices. Everything is working as expected except I am getting
“This application has failed to start because xxxxxx.dll was not found…”
errors. This occurs for any .ds file that can’t load its dll.
Is there a way to disable these messages or work around them? I don’t have control over what the twain devices the user has installed (or uninstalled). I’d also rather not use the standard Twain device selection UI since we have a custom look and feel.
The errors occurs while calling the the GD_CONTROL/DAT_IDENTITY/MSG_GET_FIRST triplet.
Curiously, the error messages don’t show up when I’m in Debug mode (C# VS2005).
Any ideas?
> “This application has failed to start because xxxxxx.dll was not found…”
What is the filename of xxxxxx.dll?
Is this a trick question? If that is the error message it seems that the filename is xxxxxx.dll.
no I’ve never seen this error and it is only related to twain in the sense that you are posting it to this forum and perhaps the application is attempting (poorly) to communicate with a scanner/camera.
.
My apologies for any confusion…
xxxxxx.dll is not the literal filename. The actual filename would be the name of the twain driver for a specific device.
The error message shows up where a .ds file in the twain_32 directory references a dll that does not exist or load properly. This could occur for any Twain component that has a botched install or was improperly uninstalled.
It looks like the error messages are coming from the Source Manager, but the default Twain source selection UI does not show them. They only occur when I get the list of twain devices by the GETFIRST/GETNEXT method. This is why I’m wondering if they can be disabled.
Fixing the error messages by forcing the end user to fix their device install is not ideal. I do not have any control over what devices end users of my application have installed.
My application is working as expected, I’m just trying to work around error messages that I don’t have any control over. Thanks for any help.
just trying to work around error messages that I don’t have any control over
lovely phrase.
So ( if I understand you) the generic select source dialog doesn’t display the drivers gone wild but they turn up when you getfirst/next thru. interesting.
If GetDefault/GetFirst/GetNext isn’t the last triplet you call before the big kaboom what is?
Who is the vendor & driver in use?
.
- AuthorPosts