1. Re: An old C function problem revisited - Rob??
- Posted by Jonas Temple <jtemple at yhti.net>
Feb 27, 2006
-
Last edited Feb 28, 2006
Al Getz wrote:
>
> I noticed a difference in params between the def of
> cwbUN_DisplayCommandPrompter
> and the example they quote in the 'docs'.
> What's up with that?
Yeah, I asked myself the same question. I even removed the last parm from my
call to see if that corrected the problem. :) Someone told me that "@20" in the
function name problably means 5 parms for 4 bytes each. Makes sense.
> Also, they null the two pointers out before they pass them (i guess)
> so you could try that.
Yep, did that too...
> Also, did you try allocating more bytes then needed for the string?
The docs specifically say to allocate 32768 bytes at least so if you look at my
earlier post that's exactly what I did.
> Are you sure the systemhandle you are passing is valid?
Yep. It properly makes a connection to the system defined by the system handle.
> Did you try leaving off the "@20" at the end of the function name?
> and possibly leave off the "_" in front of the function name?
But that's how the function is exported from the dll.
> Ask Rob if "poke" works correctly for memory allocated with the
> shells allocator...perhaps try writing then reading with 'peek'.
>
Okay, Rob. Do you think there's some incompatability issue here?
> Just some possibilities, which i cant say for sure if they will help
> or not. When this kind of thing happens to me and i dont have a solid
> answer i usually try a bunch of different things...whatever i can think
> of...to see if i can stumble on the correct answer. Usually sooner or
> later something comes up that solves it. Is there anyone associated
> with the dll you are using you can ask?
IBM? Getting an answer from them is quite difficult, just ask Rob.
> Is there a web site for this
> 'library' ?
Yes but the web site lists nothing more than the documentation from the include
file. A google of the function name doesn't even turn anything up.
Whenever i had a problem like this in the past it was
> one of the things you already covered:
> *incorrect numb of params
> *param wrong type
> *param not passed properly as required by Eu
> *not enough string space allocated
>
I've tried countless variations on the call but to no avail. I guess I'm close
to just giving up again. :(
Jonas Temple
http://www.yhti.net/~jktemple
