Dave Addey wrote:
>but on
>Win it is reported as 5316944 (that's an integer, not hex) which I don't
>recognise.
That doesn't look like a correct encoding to me.
>I've been finding out more about this string, and it seems as though
>FileLocation->Length() returns 0. The length of the cstring is 19, and then
>there's that weird encoding.
this all sounds as if memory got overwritten. Do you check these
values right at the time when you try to build the CFstring, or
later?
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
|