BorlandTalk.com

Scott · Guest

Hello,

I have an OWL application that I need to get working under BCB5
(preferably BCB6 and OwlNext, but let's start with BCB5 and Owl for
now).

I've used BCB5 for years, but never with OWL. So today, I dug out my
trusty BCB5 companion tools disc and attempted to install the OWL
support. Of course, there appears to be aboslutely no documentation
whatsoever, just a bunch of ZIP files. So I created a directory called
'owl', made include bin and lib directories off of it, and unzipped the
files to what appeared to be the appropriate place.

Next, I created a new console application. I unchecked the 'vcl'
checkbox in the console wizard, but left the multithread box.

I told console wizard to use the main file from my OWL project as it's
source (this is the file containing OwlMain).

Next, I added all of my source files back into the project.

I added two libraries: owlwt.lib and bidst.lib as these appeared to be
the libraries the original app was using. I used the copies that came
out of the OWL distribution from the companion CD.

Eventually after fixing numerous things that went wrong, I managed to
get the thing to compile.

Problem is, when I hit run, it fails with an EAccessViolation in
CC3250MT.DLL. This is before any dialog boxes have been opened. In
fact, it happens before OwlMain() gets called, which leads me to
believe it's somewhere in the Owl intialization code.

Any idea what I've done wrong? I've left all other compile options to
the BCB5 defaults.

Thanks,
Scott

Scott · Guest

Silly me, I was building the project with dynamic RTL. Changed it to
static and got past that problem. Now, to extricate BWCC from the three
dozen forms in the project.

A curious thing has happened; the width of all the dialog boxes is a
little bit narrower. Perhaps by about 10-20%. This happened when moving
from OWL under BC 5.01 to OWL under BCB5. Does anyone know why this
happened, or how to correct it?