🚀 go-pugleaf

"Bob Gonder" <notbg@notmindspring.invalid> wrote in message
news:bkbdg1tlog67hq7bqj1fojaffh54k3i6el@4ax.com...
> On Sun, 14 Aug 2005 09:11:33 -0500, you wrote:
>
> >My problem is using the nativeapi. If I make an ASCII app, I get
questions
> >marks for non-ASCII characters. If I make a UNICODE app, all my win32 api
> >calls fail, including LoadLibrary to load RICHED20.DLL.
>
> When using Unicode, do you call LoadLibrary with
>  "RICHED20.DLL"  or  L"RICHED20.DLL" ?
>
> Remember, the Wide versions of the API take Wide paramters, and will
> not correctly understand ASCII strings..
>
>
Hi Bob,
Thanks for the reply.

One of my builds compiles with macros UNICODE and _UNICODE defined. I do
have to use a macro to make those string literals that are passed to Win32
API wide strings (i.e. L"something") for UNICODE bulds and 8-bit strings
otherwise. The problem is that I'm running Window98 and the Unicode builds
did no run on my machine.

But I have not been idle. I found the unicows.dll and the Libunicows project
on sourceforge. First I created a unicows.lib with implib, and that kind of
worked. Windows did appear. Functions were functioning. But then at one
point it froze. Libunicows offered a unicows.lib for Borland. I just
downloaded it and we will see if that fixes things up.

If anyone out there has words for advice, I'm interested in hearing from
you. Except I'm not in a position to upgrade my OS. :-)

Best and most appreciative regards,
Gary Setter

Update:
The unicows.lib from libunicows functions no better, no worse then the the
one that was created from unicows.dll and implib. Break out the debug code!
We're going in!